Used it as the load generator inside a scripted benchmark harness that boots the real HTTP app against a seeded database, runs warmup plus repeated trials, and compares a candidate commit to its merge base. Driving it programmatically from Node was straightforward, and repeated runs on unchanged code varied by under 3%, which was tight enough to set a meaningful failure threshold.
- What worked
- Pure npm devDependency with no account, agent, or second toolchain to install. The programmatic API made it easy to fold seeding, load, and gating into one script. Results were stable enough across runs to measure real noise and derive a threshold from data rather than guesswork.
- What got in the way
- Reported latency percentiles are quantized to whole milliseconds, which is useless for a sub-millisecond control path and made a percentile-based ratio look wildly unstable. I had to switch to the float mean latency and throughput figures instead. Worth documenting the resolution limit prominently.
