chore: generate PIL constants from via constants gen#7258
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Proof generationEach column represents the number of threads used in proof generation.
L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 8 txs.
Circuits statsStats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.
Stats on running time collected for app circuits
AVM SimulationTime to simulate various public functions in the AVM.
Public DB AccessTime to access various public DBs.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contract classes are registered in the tx.
Transaction size based on fee payment method | Metric | | |
jeanmon
left a comment
There was a problem hiding this comment.
Great initiative @dbanks12
I am approving but please have a look at my comment. Furthermore, I suggest that whether we add some output messages about the need to run bb_pil whenever a relevant constant is modified. Alternatively, we could integrate bb_pil, format.sh as part of this script. Keeping it like this will lead to people getting issues down the road (unit tests failure, etc...) without understanding what they did wrong.
Co-authored-by: Jean M <132435771+jeanmon@users.noreply.github.com>
There is a script within barretenberg called rebuild_avm.sh / that we need to educate people to run once constants are generated |

No description provided.