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.

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

Optimize performance of sequential DZKPs #1370

Open
andyleiserson opened this issue Oct 24, 2024 · 0 comments
Open

Optimize performance of sequential DZKPs #1370

andyleiserson opened this issue Oct 24, 2024 · 0 comments
Labels
performance This affects protocol performance

Comments

@andyleiserson
Copy link
Collaborator

andyleiserson commented Oct 24, 2024

The change in #1350 to use record IDs to index proof batches caused a modest performance regression.

Before After
25M 3 hr 4 min 3 hr 16 min
2M 15 min 16 s 17 min 38 s

Comparing the shorter runs, the difference appears to be in the share conversion step. I suspect it has to do with the way that OrderingSender sequences communications (record n+1 is not accepted into the channel until after record n) somehow reducing the amount of validation work that can be done in parallel, but I haven't completely worked out how.

Originally posted by @andyleiserson in #1350 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance This affects protocol performance
Projects
None yet
Development

No branches or pull requests

1 participant