Divan

Visit Website

Introduction

Divan provides comfy benchmarking for Rust projects. You add it to Cargo.toml, create a benchmarks file such as benches/example.rs and register functions with an attribute, optionally benchmarking them over multiple cases (for example several input sizes).

Output is a readable table showing fastest, slowest, median and mean timings per case. Divan 0.1.21 requires Rust 1.80 or later. It is a lighter-weight alternative to Criterion.rs for teams that want quick, readable numbers.

Whatever tool you choose, benchmark results are only useful if they are stable. Pin the hardware or runner, run enough iterations to make variance visible, and treat a single noisy result as a reason to rerun, not to block a merge.

The source code is at nvzqz/divan on GitHub under the Apache-2.0 licence, with about 1,500 stars; the most recent commit was on 19 July 2026.

Features

1. Attribute API: #[divan::bench] registration.
2. Multiple cases: Benchmark across arguments.
3. Tabular output: Fastest, slowest, median and mean.
4. Lightweight: Simple setup.

Pros

1. Free to use: Open source under the Apache-2.0 licence, so the core tool costs nothing to use.
2. Actively maintained: The repository had commits as recent as 19 July 2026.

Cons

1. Pre-1.0: API may still change.
2. Guide in progress: Documentation still being written.

Usage and Links (Example)

[dev-dependencies]
divan = "0.1"

[[bench]]
name = "example"
harness = false

fn main() { divan::main(); }

#[divan::bench(args = [1, 2, 4, 8, 16, 32])]
fn fibonacci(n: u64) -> u64 { if n <= 1 { 1 } else { fibonacci(n - 2) + fibonacci(n - 1) } }

Resources:

• Divan website

Pricing

Divan is free and open source under the Apache-2.0 licence.

Recommended for?

1. Rust developers wanting quick, readable benchmarks.

Conclusion

Divan makes Rust benchmarking pleasant.

Use Criterion.rs when you need its statistical reports.

On CheckOps, Divan is filed under the Performance & load and Unit testing stages. Related tools listed here include cargo-nextest, hyperfine, BenchmarkDotNet, JMH, proptest and cargo-mutants. Which one fits best depends mostly on your stack, your team’s size and skills, and whether you prefer to run tools yourself or pay for a managed service. This page reflects the official website, documentation and repository as they stood on 11 November 2026.