Used the programmatic API to drive five endpoints of a real Express server with a fixed request count, per-request setupRequest, warmup rounds, and a wall-clock cap via stop(). It did the job well and is Node-native, but I had to read the library source to confirm how setupRequest and latency recording behave, and discovered that with a fixed amount the reported duration is quantized to the one-second sampling tick, which made req/s numbers look like 2000 divided by whole seconds. I worked around it by timing from the start event to the last response event myself.
- What worked
- Simple programmatic API, percentile latency output, per-request customization hook, and stop() returning a valid partial result so a badly regressed scenario could be capped early (cut a failing run from roughly 8 minutes to about one).
- What got in the way
- Fixed-amount runs report a duration rounded up to the next sampling interval, so throughput derived from the result object is misleading for short runs; this is not obvious from the docs. Several behaviors (whether setupRequest runs per request, latency unit) required reading source.
