Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
trie/triedb/pathdb: improve dirty node flushing trigger #28426
trie/triedb/pathdb: improve dirty node flushing trigger #28426
Changes from all commits
665597c
f6a2209
bb59ab4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
An interesting implicit thing here is that nodebuffer.flush() will "surely" push the disk layer beyond
oldest-1
. This is kind of true, most of the time, since only the 128 diff layers re main after the flush andlimit
in theory is more like 90K.Thus two questions/requests:
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.
Ah, no
oldest = bottom.stateID() - limit + 1
, so flushing everything will move the disk layer tobottom.stateID()
.In that case
oldest - 1
will bebottom.stateID() - limit + 1 - 1
==bottom.stateID() - limit
. So anything above 0 limit should be ok.