bencher

Bencher

Run locally. Run in CI. Same bare metal every time.

Bencher is the first continuous benchmarking platform to run your existing benchmarks on the exact same bare metal both locally and in CI. It tracks results over time and fails the PR when there's a performance regression.

Built for teams where performance matters:

• Databases
• Compilers
• Browsers
• Runtimes
• Networking stacks
• Cryptographic libraries
• Operating Systems

Most teams start on GitHub Actions runners with a benchmark comparison script. That approach breaks down when noisy shared CI runners hide real performance regressions.

• Typical CI runners: >30% variance
• Bencher Bare Metal runners: <2% variance

When a number moves, it means something.

Benchmark for free →   Bare Metal Quickstart

Used by the teams behind Google Sedpack, Microsoft CCF, GitLab Git, Mozilla Neqo, Rustls, Servo, and Diesel.

🐰 Use the GitHub Action with your project

The Problem

Shipping a performance regression is expensive:

• A database regression on a hot path pages someone at 2am
• A compiler regression silently makes every downstream build slower
• A browser engine ships a 10% paint regression and users notice
• A crypto library that adds a microsecond to a handshake breaks an SLA

Without trustworthy benchmarks in the PR workflow, you find out when users do.

Local benchmarks aren't reproducible. Every check means stopping work to pull the baseline branch and wait on a comparison. Most engineers skip it.

CI runners are shared and noisy. Noisy benchmarks train engineers to ignore alerts. Performance regressions silently ship.

If you can't tell a real regression from noise, the results are worthless. So teams stop looking.

How Bencher Works

1. Run: Run your benchmarks locally or in CI using the exact same bare metal runners and your favorite benchmarking tools. The bencher CLI orchestrates running your benchmarks on bare metal and stores the results.
2. Track: Track the results of your benchmarks over time. Monitor, query, and graph the results using the Bencher web console based on the source branch, testbed, benchmark, and measure.
3. Catch: Catch performance regressions locally or in CI using the exact same bare metal hardware. Bencher uses state of the art, customizable analytics to detect performance regressions before they merge.

For the same reasons that unit tests are run to prevent feature regressions, benchmarks should be run with Bencher to prevent performance regressions. Performance bugs are bugs!

Example PR Comment