counterblockd memory usage

[danielnbarbosa]

On an 8GB machine counterblockd (on mainnet) is sucking up over 7GB before being killed by the OOM killer and restarting, which it seems to deal with just fine. I know you specified 16GB RAM in your docs, but it just seemed unnecessary to me so I thought I could get away with 8GB. Why does counterblockd need so much RAM and can anything be done about it?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8997519-counterblockd-memory-usage?utm_campaign=plugin&utm_content=tracker%2F686853&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F686853&utm_medium=issues&utm_source=github).

[unsystemizer]

That's before the Docker version of Fed node came out, right?
I think it's better now, I recall I was able to run the entire FedNode (Docker) in a 4GB VM.
Edit: without bitcoind (running externally), I am able to run CP and CP on a host with 3GB RAM (using SSD disk). With Counterwallet and bitcoind it should be able to run fine in 4GB VM and light production on hosts with 8-12 GB I think.
For test/dev, try to limit mempool size in your bitcoin.conf.