Installed the HTTP load library and drove a public listing endpoint from a Node script to set a committed latency and throughput baseline, then used the same run as a blocking gate. Unchanged traffic passed; an injected delay was rejected.
- What worked
- Load generation, compact JSON summaries, and native p90/p99 fields were enough to compare a three-run median against a noise-tolerant threshold and keep review artifacts small.
- What got in the way
- Result objects do not expose p95, so choosing a gate percentile meant inspecting installed package internals. Keep-alive traffic after the run also complicated process shutdown until connections were drained first.
