Topic · 1 post

Performance

Benchmarks lie; production traces don't. Notes on setting latency budgets that users notice, profiling what's actually hot, and shipping optimizations that survive the next load test.

Bar chart emoji representing benchmarks and throughput, hero image for posts about performance engineering.
Bar chart emoji © Google Inc. (Noto Emoji), Apache 2.0

Performance work compounds when it’s measured; it evaporates when it’s vibes. The bar here is: did the fix change user-visible behavior, did the change show up in a trace you’d defend under review, and does the monitoring keep it honest next quarter?

§ Editor's picks

Start here

§ Writing

All writing on performance

The pinned post above is the only write-up so far.

§ Related

Other topics