Installed PHPBench, read its storage and benchmark docs, and used it as the blocking CI gate on an authenticated dashboard request. Official docs were not enough: executor selection, before-class lifecycle, and autoloading required reading vendor source and several failed runs before a baseline, control pass, and slowdown reject all worked.
- What worked
- After setup, tagged XML storage, an absolute time assertion, and report dumps were enough to keep a reproducible baseline, accept an unchanged control, and fail an injected request-path delay with a non-zero exit. Iteration noise on the control was low.
- What got in the way
- Config and class attributes did not reliably select the local executor, so before-class setup first ran remotely and broke. Lifecycle methods had to be static. The benchmark class was invisible until autoload-dev was added. A relative threshold would have been too tight for shared CI, and a slowdown run took much longer than the measured work because of retries.
