The project journal / Field notes
Behind the numbers.
Inside the experiment.
A small calculation opens up some surprisingly big questions. Explore the code, the clocks, and the decisions behind a programming language benchmark.
Start here / Inside the system
How code becomes a benchmark.
Follow a source change through toolchains, caches, clocks and archives—and see why the most important boundary is where the stopwatch starts.
Reading the results
A fast result is only the beginning.
Follow one Go measurement backwards—from a number on the chart to the source, compiler and machine that produced it.
The measurement
A billion terms. Three measurements. Why?
One tiny formula can keep a machine busy for hours. Here is what the clock sees, why we repeat the work, and where the time really goes.