Recommendation Engine Memory leak?

I have not seen a true memory leak, but I did disable hardware polling in my environment because it kept using the memory on my APEs.  I have moved all polling to my APEs to allow the poller to run the application more efficiently.

What products / versions are you running?  Is your main poller doing any polling?  If it is, I would look how much it is polling.

Sorry, read through that too fast.  I overlooked the Recommendation part.  I ended up disabling recommendations in my environment because I was also having problems with it.  I have not tried yet since upgrading to 6.4.

Daniel

I'll reach out to you to gather diagnostic data.  I want to dig into this deeper with the engineering team to address your issue. 

Case # 1143886 Created: Memory leak.

What was the result of your case? 

We upgraded 1 week ago and so far this is our only real problem.  The RecommendationService consistenly climbs to 9.5 GB fairly quickly after I restart it.  I tried turning off Policies that had a lot of things in them, but I'm just considering turning off the entire feature if I can't figure this out...

I am seeing the same issue as well with high memory

The result of the case was that 8GB is the low side of the memory requirement for the recommendation engine in our environment.  Our environment consists of about 120 ESXi hosts and around 1,200 servers.  I find this memory utilization unacceptable.  vROPS requires much less to do the same thing.  I am about to put in another 32GB of RAM and we will see what happens.

This scares me.  Keep me posted on what you find out.  My environment is a bit larger, so if you have to go to 32GB, I'm not sure that it's usable for me.

I also upgraded to 12.1 and have a memory leak on SolarWinds Information Service V3. Total was running 8 - 9G but now runs up to the 15G total. I've had a ticket in to dev. but no resolution yet. I need to restart this service everyday or it will cause a problem to the entire system.

I'm facing the same issue after upgrade to 12.1. I have to restart the poller every few days to resolve this issue.

I don't have this issue before the upgrade.