pathdb: handle persistent id when using nodebufferlist #121
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.
Description
When using nodebufferlist in pathdb, geth should maintain three node cache in memory for withdrawal proof. This pr fixes a case that when the length of history is greater than
StateHistory
but not beyond maxBufferSize, nodebufferlist still should keep three node cache.Start a load test that uses 1000 accounts and 1TPS for about 50 hours to verify this pr, metrics are shown below:
Rationale
N/A
Example
N/A
Changes
Notable changes: