|
3 months ago | |
---|---|---|
.. | ||
README.md | 3 months ago | |
hash.rs | 1 year ago | |
merkle.rs | 4 months ago | |
smt-subtree.rs | 4 months ago | |
smt-with-entries.rs | 4 months ago | |
smt.rs | 1 year ago | |
store.rs | 1 year ago |
In the Miden VM, we make use of different hash functions. Some of these are "traditional" hash functions, like BLAKE3
, which are optimized for out-of-STARK performance, while others are algebraic hash functions, like Rescue Prime
, and are more optimized for a better performance inside the STARK. In what follows, we benchmark several such hash functions and compare against other constructions that are used by other proving systems. More precisely, we benchmark:
We benchmark the above hash functions using two scenarios. The first is a 2-to-1 $(a,b)\mapsto h(a,b)$ hashing where both $a$, $b$ and $h(a,b)$ are the digests corresponding to each of the hash functions.
The second scenario is that of sequential hashing where we take a sequence of length $100$ field elements and hash these to produce a single digest. The digests are $4$ field elements in a prime field with modulus $2^{64} - 2^{32} + 1$ (i.e., 32 bytes) for Poseidon, Rescue Prime and RPO, and an array [u8; 32]
for SHA3 and BLAKE3.
h(a,b)
Function | BLAKE3 | SHA3 | Poseidon | Rp64_256 | RPO_256 | RPX_256 |
---|---|---|---|---|---|---|
Apple M1 Pro | 76 ns | 245 ns | 1.5 µs | 9.1 µs | 5.2 µs | 2.7 µs |
Apple M2 Max | 71 ns | 233 ns | 1.3 µs | 7.9 µs | 4.6 µs | 2.4 µs |
Amazon Graviton 3 | 108 ns | 5.3 µs | 3.1 µs | |||
Amazon Graviton 4 | 96 ns | 5.1 µs | 2.8 µs | |||
AMD Ryzen 9 5950X | 64 ns | 273 ns | 1.2 µs | 9.1 µs | 5.5 µs | |
AMD EPYC 9R14 | 83 ns | 4.3 µs | 2.4 µs | |||
Intel Core i5-8279U | 68 ns | 536 ns | 2.0 µs | 13.6 µs | 8.5 µs | 4.4 µs |
Intel Xeon 8375C | 67 ns | 8.2 µs |
h([a_0,...,a_99])
Function | BLAKE3 | SHA3 | Poseidon | Rp64_256 | RPO_256 | RPX_256 |
---|---|---|---|---|---|---|
Apple M1 Pro | 1.0 µs | 1.5 µs | 19.4 µs | 118 µs | 69 µs | 35 µs |
Apple M2 Max | 0.9 µs | 1.5 µs | 17.4 µs | 103 µs | 60 µs | 31 µs |
Amazon Graviton 3 | 1.4 µs | 69 µs | 41 µs | |||
Amazon Graviton 4 | 1.2 µs | 67 µs | 36 µs | |||
AMD Ryzen 9 5950X | 0.8 µs | 1.7 µs | 15.7 µs | 120 µs | 72 µs | |
AMD EPYC 9R14 | 0.9 µs | 56 µs | 32 µs | |||
Intel Core i5-8279U | 0.9 µs | 107 µs | 56 µs | |||
Intel Xeon 8375C | 0.8 µs | 110 µs |
Notes:
Before you can run the benchmarks, you'll need to make sure you have Rust installed. After that, to run the benchmarks for RPO and BLAKE3, clone the current repository, and from the root directory of the repo run the following:
cargo bench hash
To run the benchmarks for Rescue Prime, Poseidon and SHA3, clone the following repository as above, then checkout the hash-functions-benches
branch, and from the root directory of the repo run the following:
cargo bench hash