Why your tests are slow
Six causes, ranked by how often they are the real problem, and the fix for each.
tech, developers, and the code underneath
17 pieces tagged performance,
from April 7, 2025 to September 16, 2026.
Six causes, ranked by how often they are the real problem, and the fix for each.
Every fixed-size resource is a queue. Most of them are unmonitored, and that is where latency hides.
The single most useful performance visualisation, and the four shapes worth recognising in one.
A number, agreed in advance, that fails the build. The only mechanism that has ever kept a system fast.
Why your database has 400 connections, why that is bad, and how to size a pool without guessing.
It should be forty megabytes. Here is where the rest of it came from and how to get it back.
The cheapest performance win available, ignored because it is not glamorous. Where it pays and which algorithm to pick.
Six causes, in order of how often they're the actual problem, with the fix for each.
Frame budgets, determinism, and shipping to a fixed target. Game developers solved problems the rest of us are still arguing about.
A short guide to the specific ways performance numbers lie, from someone who has published misleading ones.
The biggest storage-layer change in years is in production now. Here's what it actually did to real workloads.
LLD becomes the default linker on x86-64 Linux. Link times drop and nobody notices, which is the point.