#benchmark #criterion #cargo #reporting #performance #running #extension

app cargo-criterion

Cargo extension for running Criterion.rs benchmarks and reporting the results

7 releases (3 stable)

1.1.0 Jul 28, 2021
1.0.1 Jan 25, 2021
1.0.0 Jul 19, 2020
1.0.0-alpha1 Jun 29, 2020
0.0.1 Apr 27, 2020

#113 in Profiling

Download history 1009/week @ 2024-03-17 1044/week @ 2024-03-24 1088/week @ 2024-03-31 1114/week @ 2024-04-07 983/week @ 2024-04-14 823/week @ 2024-04-21 655/week @ 2024-04-28 801/week @ 2024-05-05 848/week @ 2024-05-12 912/week @ 2024-05-19 657/week @ 2024-05-26 970/week @ 2024-06-02 889/week @ 2024-06-09 729/week @ 2024-06-16 665/week @ 2024-06-23 267/week @ 2024-06-30

2,614 downloads per month


10K SLoC


Criterion-rs Cargo Extension

cargo-criterion is a Plugin for Cargo which handles much of the heavy lifting for analyzing and reporting on Criterion-rs benchmarks.

Table of Contents


  • Charts: Uses gnuplot or plotters to generate detailed graphs of benchmark results
  • Reports: In addition to the reports generated by Criterion.rs, cargo-criterion generates a historical report showing the performance of a function over time.
  • Configurable: cargo-criterion's plot generation can be configured using a criterion.toml file.


This assumes that you already have benchmarks which use Criterion-rs. If not, see the Criterion-rs Quickstart Guide. Note that Criterion.rs version 0.3.3 or later is recommended. Benchmarks which do not use Criterion.rs, or which use an earlier version, will run correctly but will not benefit from some of cargo-criterion's features.

First install cargo-criterion:

cargo install cargo-criterion

Then you can use it to run your Criterion-rs benchmarks:

cargo criterion


  • cargo-criterion seeks to improve iteration time for Criterion-rs benchmarks. By moving functionality into a separate executable which can be installed once and reused, Criterion-rs can shrink - meaning less code to compile and link into the benchmarks themselves.
  • Because cargo-criterion can oversee the whole benchmark process from beginning to end, it's better placed to deliver features that would be difficult to implement in Criterion-rs. These include:
    • Machine-readable output
    • Tracking benchmarked performance over time


First, thank you for contributing.

One great way to contribute to cargo-criterion is to use it for your own benchmarking needs and report your experiences, file and comment on issues, etc.

Code or documentation improvements in the form of pull requests are also welcome. If you're not sure what to work on, try checking the Beginner label.

If your issues or pull requests have no response after a few days, feel free to ping me (@bheisler).

For more details, see the CONTRIBUTING.md file.

Compatibility Policy

cargo-criterion supports the last three stable minor releases of Rust. At time of writing, this means Rust 1.50 or later. Older versions may work, but are not tested or guaranteed.

Currently, the oldest version of Rust believed to work is 1.46. Future versions of cargo-criterion may break support for such old versions, and this will not be considered a breaking change. If you require cargo-criterion to work on old versions of Rust, you will need to stick to a specific patch version of cargo-criterion.


cargo-criterion was originally developed and is currently maintained by Brook Heisler (@bheisler).


cargo-criterion is dual licensed under the Apache 2.0 license and the MIT license.


~195K SLoC