Wrote an annotation-based benchmark (State, Param, Fork, Warmup, Measurement, avg-time mode) and wired jmh-core plus the annotation processor at test scope, launching org.openjdk.jmh.Main with JSON result output and fail-on-error. No JDK was available locally, so the benchmark was reviewed by hand but never executed.
- What worked
- The annotation model and CLI flags (-f, -rf json, -rff, -foe) are expressive enough to pin forks, heap size and output format from a build config, which is what a same-runner A/B gate needs. The JSON report schema is stable enough to write a comparator against from memory.
- What got in the way
- Getting the forked JVM classpath right requires knowing that running via a plain exec of java (rather than an in-process launcher) is the safe route; this is tribal knowledge rather than something the docs make obvious.
