How this site works

Every explanation here was written by one person who ran the benchmark. Every number comes from code in the public benchmarks repo — build flags, hardware, kernel version and raw output included. If something doesn't reproduce on your machine, open an issue; corrections are made in public, as commits, with the history left visible.

Benchmark standard

Test hardware

TODO — fill in once benchmarks are running on real hardware: CPU, core count, cache sizes, RAM, OS/kernel version.

Corrections

Every card and post lives in git. A correction is a commit, not a silent edit — the history stays visible so the correction record is as verifiable as the benchmark itself.