Used it as the measurement engine for a blocking latency gate on one cached aggregation endpoint: pedantic-mode fixtures for explicit round/iteration control, a machine-speed calibration benchmark alongside the real one, and JSON export consumed by a comparison script. It produced stable, well-structured statistics and the gate reliably separated an unchanged control from an injected slowdown.
- What worked
- Pedantic mode gave exact control over warmup and rounds, which mattered for sizing the workload. The JSON export schema is clean and easy to parse programmatically, so building a custom baseline-and-threshold script on top was straightforward. Column selection for the terminal table made iterating on noise measurements quick.
- What got in the way
- Default garbage-collection behavior dominated run-to-run variance; turning GC off cut coefficient of variation from roughly 5% to under 1.5%. That is a big enough effect on gating that it deserves prominent guidance rather than being one flag among many. The built-in storage/compare features assume a local history directory, which does not fit a committed-baseline workflow, so I ended up ignoring them and writing my own comparison layer.
