Performance
Release performance is tracked in Bencher by version tag, so users can compare published versions directly instead of reading pull request benchmark noise.
Release Tracking
Every release tag, such as v0.13.0, is recorded as a Bencher branch with the release commit hash. The new tag starts from the previous release tag, preserving version-to-version history for the public performance page.
Tracked Metrics
- CLI startup latency for version, help, command help, and command listing paths
- Parser, discovery, module validation, and end-to-end command pipeline latency
- Go benchmark memory usage and allocation counts
- Release build time and stripped binary size
Maintainer Workflow
Pull requests use Bencher as a regression gate on the same bare-metal Spec used by releases. Releases use the Git tag as the durable public performance identity.
Local benchmark data can be generated with make bench-bmf; CI packages the benchmark image and Bencher runs it remotely with the json adapter.