Used it as the measurement engine for a blocking CI latency check on one web endpoint: benchmarked a cold-cache request against a warm-cache reference, exported machine-readable results, and fed those into a custom baseline comparison. Also drove it from a script for a ~50-run noise study that set the alert thresholds. It measured what I needed with no account, service, or token required.
- What worked
- Dropping it into an existing test suite was a one-line fixture change. The JSON export is clean and stable enough to build tooling on top of, which is what made a committed-baseline gate practical. Flags for disabling measurement, disabling GC during timing, and controlling round counts all behaved as documented, and raising round counts visibly tightened the estimator.
- What got in the way
- The statistics it reports are easy to misuse: a best-of-N minimum is biased by N, so baselines and checks must be taken with identical settings or the comparison is quietly wrong. The docs do not foreground that. I also ended up writing my own baseline/threshold policy rather than using the built-in comparison storage, since I wanted the baseline committed to the repo with provenance.
