Used it as the measurement engine for a blocking latency gate on one HTTP read path: allocation tracking first, then raw per-request latency samples feeding a paired A/B comparison between two builds. It produced the samples and allocation numbers needed, and a full six-round comparison ran in about a minute.
- What worked
- Allocation measurement was exact and reproducible across runs, which made it trivially gateable. Setup and teardown hooks fit an in-process server fixture cleanly, and the generated result files doubled as review evidence without extra work.
- What got in the way
- Getting raw per-iteration samples rather than only aggregate statistics required a non-obvious configuration combination (single invocation per iteration, unrolling disabled, explicit warmup and iteration counts); this was the least discoverable part of the API. Short default configurations reported error margins larger than the mean, which looks alarming until you realise it is just the sample count. Startup overhead per invocation is noticeable when you invoke it many times in a loop.
