Skip to content
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.

Sign up for GitHub

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

Jump to bottom

perf: Consider skipping committing to empty tables #735

Open
Nashtare opened this issue Oct 18, 2024 · 0 comments
Open

perf: Consider skipping committing to empty tables #735

Nashtare opened this issue Oct 18, 2024 · 0 comments
Labels
crate: evm_arithmetization Anything related to the evm_arithmetization crate. performance Performance improvement related changes
Milestone
Performance Tuning

Comments

@Nashtare
Copy link
Collaborator

Nashtare commented Oct 18, 2024 •
edited
Loading

We can extend the logic for "ignoring" unused tables by skipping altogether the commitment phase for those (as we already rely on dummy Merkle Caps. This will require a sibling PR for related changes on CTL handling on the plonky2 side.

A similar approach could be taken for the initial segment of each batch, for which the MemBefore table is non-empty but known ahead of time.
@github-project-automation github-project-automation bot moved this to Backlog in Zero EVM Oct 18, 2024
@Nashtare Nashtare added performance Performance improvement related changes crate: evm_arithmetization Anything related to the evm_arithmetization crate. labels Oct 18, 2024
@Nashtare Nashtare added this to the Performance Tuning milestone Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
crate: evm_arithmetization Anything related to the evm_arithmetization crate. performance Performance improvement related changes
Projects
Zero EVM
Status: Backlog
Milestone
Performance Tuning
Development

No branches or pull requests
1 participant
@Nashtare