chore(ci/benchmark): add current mainnet gas limit #1934
Merged
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.
🗒️ Description
From the zkEVM benchmark perspective, we are close to start running the full benchmark suite across multiple zkVMs. Thinking with @kevaundray around which gas limit to use, we think using the current mainnet gas limit would be ideal.
While proving times should be linear with the gas limit, publishing results with 30M gas makes the interpretation of numbers a bit harder. Also, not only are proving times important, but also "memory usage" inside the zkVMs -- and many zkVMs have tight max memory limits which we might not reach with 30M, but we might with 45M (current gas limit), so we might not catch a crash.
This PR proposes adding 45M to the list and modifying it over time to always represent the current gas limit on mainnet.
cc @marioevz