feat: update noir version being benchmarked to 1.0.0-beta.6
#1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey, thank you for including Noir in this work. I'm the Noir team lead at Aztec Labs.
One thing I noticed when reading your paper is that it seemed like you were benchmarking based on a pretty early build of Noir (v0.3.2). Both the Noir compiler and the proving system Barretenberg have gone through a lot of changes in these past 2 years so I thought it would be useful to update these benchmarks to give a better picture of how Noir performs today.
Prior to June 2024,
nargohad Barretenberg embedded into it and thenargo provecommand would combine compilation, witness generation and proving into a single command. We've since removed any proof generation/verification capabilities fromnargoand instead this is done with barretenberg's standalone binarybb. I've updated the dockerfile to download the published releases ofnargoandbbrather than building from source for simplicity.As part of this update I've reworked how some of the benchmarks work in a way which I believe is in line with the other proving systems.
nargo checkandnargo compilehave been excluded from the benchmark as we don't measure rust compilation times for arkworks/gnark.One other thing to note is that our proving system has now changed so that
bbproduces ultrahonk proofs rather than turboplonk proofs as nargo did as of the release which you're currently benchmarking. If you're interested in more information on this change then I can put you in touch with some team members who work more closely on barretenberg.