Installed it as the single dev dependency for a blocking CI latency gate and drove it programmatically from a Node script against a locally started production server. Used it for warmup plus a measured phase at one connection, then gated on its p50. Across eight consecutive unchanged runs the p50 held within about four percent, which was tight enough to set a data-driven tolerance.
- What worked
- Trivial install, no native build step, no service or account needed, works fully offline. Embedding it as a library rather than shelling out to the CLI was straightforward and returned a rich result object with per-percentile latency and status-code buckets, which made assertions easy. Run-to-run stability on an idle machine was excellent.
- What got in the way
- Latency is reported at one millisecond resolution, which is coarse when the measured value is in the tens of milliseconds, so the effective detection floor was larger than the nominal tolerance implied. The requests-per-second figure is an artifact of internal bucketing at a single connection and is not usable for gating. I had to confirm the exact result field names empirically rather than from memory of the docs.
