We have a few clients that had their servers completely stalled due to the fact that GetEventStore (GES) ate up all their memory. We can reproduce the issue in-house both with version 1.0.1 and 2.0.1 of GES; they show the exact same behavior.
If we have a data-set with 13 chunks (each 256 MB) GES immediately allocates about 13*256 MB ~ 3.3 GB RAM while starting up. The memory is NOT released afterwards. As soon as we stop GES the memory is released. See attached screenshot of the Task Manager.
To run the tests we start GES from the command line with the following parameters
EventStore.SingleNode.exe --db c:\path-to-db --ip=some-ip-address
Event when adding -c 0 to the command line parameters, i.e.
EventStore.SingleNode.exe --db c:\path-to-db --ip=some-ip-address -c 0
the situation does not change significantly. GES uses maybe 200 MB less.
Some of our customers have already 20+ chunks and their numbers are growing fast.
Usually the environment we use is a dedicated VM with 8 GB of RAM. In the above cases we could mitigate the situation by adding another 8 GB RAM but customers are concerned.
I feel like we do something fundamentally wrong but looking at the documentation (specifically the command line parameters) we do not see anything evident. Any help is appreciated