-
Notifications
You must be signed in to change notification settings - Fork 110
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
change(state): Set iterator read bounds where possible in DiskDb #7731
Conversation
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.
This looks great!
But there's one edge case we still need to cover: variable-length keys.
We don't have any at the moment, but PR #7392 changes the size of a key, and its validation runs an iterator with one key size on a column family which has been changed to a different key size.
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.
Thanks!
Motivation
Unbounded RocksDB iterators are slow in column families with many delete tombstones.
This PR updates
DiskDb
to bound iterators when reading a range of keys.Close #7664.
Solution
DiskDb
methodsReview
Anyone can review.
Reviewer Checklist
Follow Up Work
address_utxo_locations()