High Memory Utilisation after upgrade to NPM 10.1.2

After upgrading to Orion 10.1.2 physical memory usage on a number of servers has gone from less than 10% usage upto 90%+ usage. Exactly the same thing happened when I tried upgrading to version 10.1.1 and I was hoping this had been fixed with the latest release. Has anybody else experienced this and is there a fix for the problem?

Thanks,
Ross.

Find more posts tagged with

memory_leak

memory_utilization

orion_npm

Accepted answers

All comments

mgibson

The same has happened to me. I was told by support that the 10.1.2 upgrade would solve my High CPU utilization on my primary poller. It has not, in fact it may be worse. however, in my case I also upgraded my SQL server to 2008 and I have a hardware limitation of 12 gb memory and of course SQL wants it all, I think I may have a backlog of info as I see many deadlocks. I plan on having the DBA cap the SQL Server Memory use so that this is issue will be alleviated(as far as the DB is concerned), this does not solve my poller maxing out my poller CPU. I alos have over 100 Orion Web users which is contributing and are monitoring over 7000 elements on the primary poller, and the netflow streams does not help.