POE-Stash-indexer icon indicating copy to clipboard operation
POE-Stash-indexer copied to clipboard

MongoDB server - huge RAM usage

Open PaulBenn opened this issue 8 years ago • 2 comments

Hi!

I'm using the indexer on Windows (with a few minor tweaks) gathering data from the start of the stream to around now, which I estimate will take about 26 days and no more than 4 terabytes. However I have a small problem - RAM usage by MongoDB server goes up straight to 99% after about 10 minutes. Do you know if this is caused by a memory leak somewhere in the code or if this is normal for processing jobs of this size?

Thanks and sorry if this is a stupid question. Paul

PaulBenn avatar Jan 19 '17 13:01 PaulBenn

Hi Paul,

Regarding memory leaks, I can't vouch that there are none in this code. However, I used to ran this code for days and I didn't have stability issues. I do not actively maintain this code anymore. I kinda switched to a newer codebase using C++/MySQL which has been completely debugged and tested with Valgrind to prevent memory leaks. This new indexer also has a very small memory consumption.

licoffe avatar Jan 19 '17 13:01 licoffe

I see - I've taken a quick look at that codebase, but can't really tell, would it be easy to switch over to mongo? not sure I want to deal with sql schemas and queries right now.

PaulBenn avatar Jan 19 '17 18:01 PaulBenn