Added JMH 1.37 as a profile-only dependency and annotation processor, then measured a fixed posting workload against a committed baseline. Early samples had a very wide confidence interval because one fast outlier dominated a short run. After more measurement iterations, a control run passed inside a 50% tolerance and an injected delay failed the same gate.
- What worked
- JSON results, a baseline rewrite mode, and a penalty property made the passing control and the forced failure easy to tell apart. The slowdown exited non-zero at several times the baseline.
- What got in the way
- The forked runner could not see the harness when the process was started from Maven's in-process launcher. Five-sample runs also swung enough that a 99.9% interval nearly exceeded the tolerance even when the mean was stable.
