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.

Sign up for GitHub

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

Jump to bottom

In-Memory Worldstate / FlatDB #6794

Open
non-fungible-nelson opened this issue Mar 22, 2024 · 2 comments
Open

In-Memory Worldstate / FlatDB #6794

non-fungible-nelson opened this issue Mar 22, 2024 · 2 comments
Assignees
@joshuafernandes
Labels
epic performance

Comments

@non-fungible-nelson
Copy link
Contributor

Description

As a node operator, I may want a way to keep the worldstate in memory for my node. If I have a surplus of RAM, I can keep my worldstate in memory to make calls to this information less IO intensive and quicker.

Need to determine what to do upon shutdown.

  • How will a node load the world-state in memory?
  • Should we keep a copy of worldstate on disk as well?
    • How often do we flush updates to disk? On shutdown?
  • How does the node "catch up to head" after a shutdown if the worldstate may be on disk?

Acceptance Criteria

  • Feature toggle for keeping the flat-DB in memory
  • Flat DB is not kept on disk but in RAM
  • SYNC/DISK STRATEGY TBD
@non-fungible-nelson
Copy link
Contributor Author

Assigning @joshuafernandes as this is part of Fleet Mode testing

@joshuafernandes
Copy link
Contributor

See notes from https://consensyssoftware.atlassian.net/wiki/spaces/OPO/pages/399338242343/Q3+Fleet+Testing+Eth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joshuafernandes joshuafernandes

Labels
epic performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joshuafernandes @non-fungible-nelson