Added JMH 1.37 as test-scoped Maven dependencies and used it to measure mean latency of a core write path against a committed baseline with a 2x fail ceiling. After increasing warmup, an unchanged control passed and an injected delay failed, with JSON results kept as review evidence.
- What worked
- Annotation-driven benches, JSON output, and a simple mean comparison were enough to prove accept and reject on the JVM without a SaaS vendor. A Maven profile kept the long run out of normal unit tests.
- What got in the way
- The first measurement still included warmup noise and a large error bar. In-process runs with zero forks ignored JVM args, so latency injection had to go through test system properties instead.
