Used it as the measurement engine for a blocking CI latency gate on a compiled CLI: warmups, fixed run counts, JSON export, and shell-less execution to remove interpreter overhead. Install was a single static binary from a release tarball and it ran immediately with no configuration. Timings on a quiet machine were tight enough that an identical-binary control came in around 1% apart.
- What worked
- Single static binary, no runtime deps, usable within seconds. Warmup/run-count flags, JSON export and the quiet output style made it trivial to drive from a script. Shell-less mode plus the built-in output-discard flag removed shell and I/O noise from the measurement. Numbers were repeatable and the summary stats were exactly what a gate needs.
- What got in the way
- It times each command as one sequential block, so when comparing two binaries on a contended machine, drift in machine speed between blocks lands entirely in the ratio — an identical-binary comparison read 0.32x under load. There is no option to interleave the compared commands, so I had to drive single-command invocations from my own round-robin harness. Also, shell-less mode silently makes shell redirection impossible; the dedicated output flag is the answer but that is easy to miss.
