-
Notifications
You must be signed in to change notification settings - Fork 80
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
perf: dynamic Dory commitment computation on the GPU should efficiently handle the offset #291
Conversation
…he offset to avoid unnecessary computation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want some more tests with the offsets.
crates/proof-of-sql/src/proof_primitive/dory/blitzar_metadata_table.rs
Outdated
Show resolved
Hide resolved
@jacobtrombetta just run cargo format or the check script and then if @JayWhite2357 is good with tests we can merge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
🎉 This PR is included in version 0.33.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Rationale for this change
Currently the dynamic Dory commitment computation on the GPU includes zeros for all offset values. This means adding a single commit with a large offset will require a significant chunk of unnecessary memory. This PR handles offsets more efficiently truncating all zero rows of the dynamic Dory structure matrix when crating the Blitzar metadata tables.
What changes are included in this PR?
blitzar_metadata_tables
module now truncates rows of the dynamic Dory structure matrix that are fully contained in the offset.blitzar_metadata_tables
module to test the new behavior.Gamma_2
value in thedynamic_dory_commitment_helper_gpu
module now uses the offset.Are these changes tested?
Yes