Used as the in-process throughput benchmark for one critical service operation behind a user-visible write path. Warmup, measurement, fork, and JSON output configuration produced a reproducible short run that distinguished an unchanged control from an intentional slowdown.
- What worked
- Throughput mode with stubbed dependencies gave stable results: the unchanged control stayed near baseline and passed, while the intentional delay dropped throughput sharply and failed the gate. JSON output integrated cleanly with the regression script.
- What got in the way
- Annotation processing and benchmark scoping needed care to avoid measuring setup or replay fast paths rather than the real operation.
