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

nethermind occupies too much virtual memory #259

Open
CodeGp2018 opened this issue Feb 18, 2024 · 1 comment
Open

nethermind occupies too much virtual memory #259

CodeGp2018 opened this issue Feb 18, 2024 · 1 comment
Labels
protocol protocol team tickets

Comments

@CodeGp2018
Copy link

🎯 Problem to be solved

nethermind occupies too much virtual memory, it needs optimization.

🧪 Tests

Hardware description:
VPS: 6G16G
image

  • [✔ ] Works in local docker-compose
  • [✔ ] Has a attested on a testnet at least once

👐 Additional acceptance criteria

@github-actions github-actions bot added the protocol protocol team tickets label Feb 18, 2024
@idkravitz
Copy link

It has nothing to do with distributed validator node configuration, instead it has to do with how nethermind accesses ledger and state, it relies on mmap, which maps files to virtual memory, thus creating a virtual memory bloat, which itself isn't a disaster, since it's loaded and unloaded on demand.

If you feel that nethermind doesn't fit your needs you can switch to other EL nodes, like geth, You can find a geth setup example in examples/ directory of the repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol protocol team tickets
Projects
None yet
Development

No branches or pull requests

2 participants