Benchmarks
Criterion results from the latest site build, across tree variants, operations, hash adapters, and sizes. Every row links to its full Criterion report. Lower is better.
Loading benchmark results…
MerkleForge vs rs-merkle vs merkle_light
From the published comparison run (cargo bench --bench comparison, i7-1185G7, 2026-08-17):
| Metric | MerkleForge | rs-merkle | merkle_light |
|---|---|---|---|
| 10K leaf construction | 22.77 ms | 3.69 ms | 2.29 ms |
| Proof size (10K tree) | 469 bytes | 448 bytes | 512 bytes |
| Proof verification | 1.84 µs | 6.39 µs | 1.78 µs |
Construction uses deterministic 32-byte leaves for every library; rs-merkle receives pre-hashed
SHA-256 leaves, matching its API. Proof size is each library's serialized proof byte count.
Reproduce
git clone https://github.com/1888-Labs/MerkleForge.git
cd MerkleForge
cargo bench --workspace
xdg-open target/criterion/report/index.html # `open` on macOS
# Focused groups
cargo bench --bench hash_throughput
cargo bench --bench binary_tree
cargo bench --bench sparse_tree
cargo bench --bench patricia_trie
cargo bench --bench comparison
cargo bench --bench bench_energy
# Comparative proof sizes
MERKLEFORGE_PRINT_COMPARISON_SIZES=1 cargo bench --bench comparison -- --listThe full published tables, environment, and caveats are on the Benchmarks docs page. To profile hotspots or measure energy, see Profiling & energy.