miniblog.

← Back to all posts
Feb 5, 2022 at 06:22
Measuring Go program (GoAWK) performance from 1.2 to 1.18: https://benhoyt.com/writings/go-version-performance/ The Go 1.3 runtime led to a 2x speedup in GoAWK, and performance wins have continued since. It's easy to see popular PLs as largely finished, but the wins here show there's still opportunities.
Go performance from version 1.2 to 1.18
Shows how much the performance of Go has improved from version 1.2 through to 1.18 -- in its compiler, runtime, and libraries.

Related Posts

Jan 25, 2026 at 16:22
2
An AI benchmark website that tries to run comparable benchmarks regularly to discover when LLM performance is degrading:
AI Benchmark Tool - Best AI Models 2025 | Compare Claude vs GPT vs Gemini
AI Benchmark Tool - Best AI Models 2025 | Compare Claude vs GPT vs Gemini
Ultimate AI benchmarking tool for 2025. Test AI performance, compare AI models, and find the best AI for coding. Real-time AI benchmark results and LLM performance tests.
Apr 3, 2025 at 15:56
2
When writing long-lived programs (daemons etc) in Rust, I find myself asking *where* I should put data. In a GC'd language it's just "I have a string" but Rust forces me to find somewhere to put it. You do get a performance benefit for this work though.
Feb 4, 2025 at 16:32
I've just squeezed another 5% of performance out of difftastic by finding a few HashSet values that weren't FxHashSet. I do wonder whether hash DoS resistance is a good default. Sure, Rust programs are often pretty fast anyway, but it feels like a different threat model to the rest of Rust.