charon-distributed-validator-node
charon-distributed-validator-node copied to clipboard
nethermind occupies too much virtual memory
🎯 Problem to be solved
nethermind occupies too much virtual memory, it needs optimization.
🧪 Tests
Hardware description:
VPS: 6G16G
- [✔ ] Works in local docker-compose
- [✔ ] Has a attested on a testnet at least once
👐 Additional acceptance criteria
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.