-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Measure block building times, history processing times, and db sizes #2733
Conversation
ce71ff9
to
abd042e
Compare
a41dc8d
to
48b4d4f
Compare
Testing comments |
Testing |
(Manually edited comment for testing) Benchmark resultsAll benchmarks are run on txs on the Values are compared against data from master at commit 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 16 txs.
Circuits statsStats on running time and I/O sizes collected for every circuit run across all benchmarks.
|
7cd082e
to
3e06ff9
Compare
Looks great. Some of these benchmarks are rather concerning. Especially as we aren't doing any proving yet! l1_rollup_execution_gas is mental. Firstly the fact that it's 100K+ gas per tx but that it gets worse as the rollups get bigger. Really all of the benchmarks at 128 txs. 22 million gas! 2.5 minutes to build the block with no proofs etc. |
elapsed
methods so they return a duration and not a live timer, otherwise the timer would keep running after the nested function passed onto elapsed has finished.