Installed autocannon 8 and called it from a script to hammer one in-process read route with a fixed request count. Its latency percentiles and completed-request total became the pass/fail gate. Quiet runs clustered tightly, an injected delay failed the check, and unchanged runs passed again.
- What worked
- Repeated quiet runs stayed within about a millisecond, and a run pinned beside busy loops still produced a usable tail. Fixed-count runs reported a full request total and a percentile object. Loading the library did not print a report. One-millisecond histogram buckets damped sub-millisecond jitter enough to baseline the tail.
- What got in the way
- Defaults expose a 97.5th percentile rather than a 95th, and the raw histogram is not returned, so the 95th could not be computed. The connection-rate option was easy to misread as a request cap. Latency units, percentile keys, and how request totals are aggregated only became clear after reading the library source.