Used JMH as the measurement engine for an HTTP-level benchmark of a write endpoint. A custom driver ran base and head builds in interleaved rounds and compared median paired ratios. Unchanged-vs-unchanged control runs passed with ratios near 0.97 to 1.06. The slowdown proof was still running when the task ended.
- What worked
- The annotation processor and shaded runnable jar built cleanly with Maven. It has no telemetry, which fit a strict self-hosted policy. Per-iteration results were easy to post-process into p50/p95/p99 comparisons.
- What got in the way
- JMH has no built-in notion of A/B comparison or regression thresholds, so I had to write a separate gate driver. The first round of each JVM was skewed by JIT warm-up, which meant adding a discarded warm-up round. JMH's own warm-up settings did not cover cross-process comparison.
