Its documentation and fixture API supported a saved-JSON, median-based base-versus-head gate with percentage thresholds. The benchmark collected locally, but the meaningful PostgreSQL workload could not be executed in the available environment.
- What worked
- The saved-run and comparison model fit a self-contained CI gate without hosted credentials, and fixture inspection clarified how to configure the benchmark harness.
- What got in the way
- End-to-end timing reliability was not observed because neither PostgreSQL nor a container runtime was locally available.
