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

Bound memory of unfinalized blocks #189

Open
Scooletz opened this issue Nov 24, 2023 · 0 comments
Open

Bound memory of unfinalized blocks #189

Scooletz opened this issue Nov 24, 2023 · 0 comments
Labels
🐌 performance Perofrmance related issue

Comments

@Scooletz
Copy link
Contributor

Currently, all the blocks that are not finalized are stored in-memory. Only blocks that are finalized are stored in the database in a persistence manner. Only at that point a block memory will be released. Make it in the way so that if there's a flood of blocks and the flushing is not the fastest, an OOM will not happen.

The following options can be done:

  1. Limit the count when Blockchain.StartNew happens make it blocking until flusher flushes enough
  2. Limit on the memory pool level, so that it does not allocate too much and blocks when a chunk is requested beyond limit
  3. ...others...
@Scooletz Scooletz added the 🐌 performance Perofrmance related issue label Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐌 performance Perofrmance related issue
Projects
None yet
Development

No branches or pull requests

1 participant