Used it as an in-process Node library to drive HTTP load against a locally spawned server for a paired A/B latency comparison across many interleaved trials. It installed cleanly, the programmatic API took one call to get right, and the result object had everything needed to build a gate on top of.
- What worked
- Programmatic invocation returning a plain result object made it trivial to script repeated trials and compute ratios. Connection/request-count options gave reproducible, bounded runs rather than time-based ones. Throughput and mean latency were stable enough across repeats to build a threshold on.
- What got in the way
- The latency percentiles in the result are rounded to whole milliseconds, which at single-digit-millisecond response times means a quantization step larger than the regression threshold I wanted. I only discovered this by dumping the raw result and inspecting field precision; the docs do not flag the resolution limit. Had to switch the gated metric to mean latency and wall-clock duration, which do carry finer precision.
