Installed 0.14.0 and used it as an in-process median-latency gate for a list HTTP path, with a committed baseline, a noise-tolerant threshold, and a same-job injected slowdown. Once the measured host stayed up, it produced medians, spread, and review artifacts that the control passed and the slowdown failed.
- What worked
- Statistical summaries were enough to pick headroom for runner noise and to keep a blocking pass/fail without a separate load-test service. Control and slowdown in one executable fit the existing dotnet CI path.
- What got in the way
- When the app under test died during setup, the run ended as missing statistics rather than a clear host error, so the first failures were easy to misread as a benchmark-library problem. A few result-export details needed a quick surface check.
