Link copied. Please paste this link to share this article on your social media post.
Why is Mongoose.Service Taking so Much Memory?
I was noticing a strange issue when testing my company's processor. When the processor starts, Mongoose.Service uses a decently small amount of memory. Maybe ~85 MB. As the processor continues going though on/off cycles using a schedule, the amount of memory Mongoose.Service uses increases without appearing to bottleneck.
At first, I assumed that the issue was occurring due to issues with my company's processor. I changed the processor to try to decrease the amount of memory needed and reduce the possibility for a memory leak to occur. It did not help. The amount of memory used by Mongoose.Service continued to creep up without appearing to bottleneck.
On a hunch, I ended the processor and took it off a schedule. I then added Schneider's Null Processor, a processor whose only task is to sleep for 5 seconds before ending, and added it to a 30 second schedule. I then restarted SmartConnectorService. Mongoose.Service, as expected, started with using 88.3 MB. I let the Null Processor run overnight. Currently, the Null Processor ran 2,539 times and uses 2,375 MB of memory, roughly 10x the memory used with my company's processor running in production at a facility with >3,000 points and which uses caching to keep track of memory.
Why is Mongoose.Service using so much memory, and what can I do to fix this problem?
I have attached three files: a log file, a screen shot of Task Manager, and a screen shot of Resource Manager. Would also send the dump file, but it's too large.