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

pathdb: handle persistent id when using nodebufferlist #121

Merged
merged 4 commits into from
Jul 5, 2024

Conversation

sysvm
Copy link
Contributor

@sysvm sysvm commented Jun 13, 2024

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:
image

Rationale

N/A

Example

N/A

Changes

Notable changes:

  • N/A

@github-actions github-actions bot requested review from krish-nr and redhdx June 13, 2024 02:24
Co-authored-by: will@2012 <[email protected]>
@sysvm sysvm changed the title fix: add frame for no proof state after force flushing nodebufferlist pathdb: handle persistent id when using nodebufferlist Jun 20, 2024
@sysvm sysvm added the R4R Ready for review label Jun 20, 2024
joeylichang
joeylichang previously approved these changes Jun 20, 2024
trie/triedb/pathdb/nodebufferlist.go Outdated Show resolved Hide resolved
@sysvm sysvm force-pushed the nl_flush branch 2 times, most recently from fa3e08b to 7bc4627 Compare June 20, 2024 04:06
joeylichang
joeylichang previously approved these changes Jun 20, 2024
trie/triedb/pathdb/nodebufferlist.go Outdated Show resolved Hide resolved
Copy link
Contributor

@krish-nr krish-nr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sysvm sysvm merged commit aead14e into bnb-chain:develop Jul 5, 2024
1 check passed
@sysvm sysvm deleted the nl_flush branch July 5, 2024 03:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R4R Ready for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants