Skip to content

Conversation

@jsign
Copy link
Collaborator

@jsign jsign commented Jul 22, 2025

🗒️ 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

@jsign jsign marked this pull request as ready for review July 22, 2025 22:21
Copy link
Member

@marioevz marioevz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@marioevz marioevz changed the title ci/benchmark: add current mainnet gas limit chore(ci/benchmark): add current mainnet gas limit Jul 22, 2025
@marioevz marioevz merged commit c8cb0ba into main Jul 22, 2025
13 checks passed
@marioevz marioevz deleted the jsign-bench-gas-limit branch July 22, 2025 23:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants