Used the programmatic API in-process to load-test one HTTP endpoint in interleaved base/head rounds, reading throughput, latency percentiles and non-2xx counts from the result object. Installed with a single dev-dependency add, no engine constraints, and produced stable numbers (round-to-round spread of a few percent at low concurrency). The only stumble was option shape: a top-level path option was silently ignored, so the first run hit the wrong route and every request was non-2xx until I passed the full URL.
- What worked
- Programmatic API with warmup, duration and connection options was easy to drive from a script; result object exposes everything needed for a gate (requests/sec, latency percentiles, status code stats, errors, timeouts). Very low overhead and consistent measurements.
- What got in the way
- A top-level path option alongside url is accepted without warning but not used, which cost a debugging cycle. I had to read the library source to confirm the warmup option shape and the result field names rather than finding them quickly in docs.
