This repository contains the scripts and source code used to benchmark the arithmetic operations in the noir-bignum repository. The benchmarks are for both computer and mobile executions of the proving system.
In the mobile/
folder, you will find the source code needed to run the mobile benchmarks along with its documentation. Those benchmarks are implemented using the Noir React Native starter project.
In the benchmarking/
folder, you will find the scripts used to benchmark the noir-bignum library on a computer. Inside the folder, you will find detailed instructions on how to run the benchmark by yourself.
- Noir ≥ v0.32.0
- Barretenberg ≥ v0.46.1
Refer to Noir's docs and Barretenberg's docs for installation steps.
The purpose of the benchmark is to measure the performance of sum, subtraction, and multiplication of the noir-bignum repository. The computer benchmark measures three performance metrics: the number of gates of the circuit, the proving time, and the verification time. The mobile benchmarks measure just the proving time.
The benchmark considers five types from the noir-bignum library: U256
, U384
, U1024
, U2048
, and U4096
. In just one program, we run
We use the hyperfine
tool for the timing reports in the computer benchmark. Hence, the timing results are the average running time of 10 executions of the corresponding command, namely proving or verification. On the other hand, for the mobile benchmarks, we report the time measured by the app. The timing results are reported for both UltraPlonk and UltraHonk proving systems.
If you want to run the computer benchmark by yourself, you can install the requirements needed for the benchmarks. Then, the following command will give you the benchmark results for the multiplication operation using 50 operations per execution:
$ cd benchmarking/
$ bash scripts/run_all_experiments.sh -m -n 50
The results will be stored in the benchmarking/results/
folder.
For more options to run the benchmark and more information about the results, please refer to the detailed documentation.
We refer the reader to the mobile documentation to run the mobile benchmark, given that the setup requires more steps.