Virtual Memory Reporting

Hello All,

I have a question that I have been meaning to ask for a while, and I am just finally getting around to it. If it is answered elsewhere in the community, I apologize. I did a search, but didn't find an answer so I am posting here. Anyways, my question has to do with virtual memory reporting in Node Details screens. Virtual memory reporting does not seem to report accurately, but rather seems to report a combination of physical and virtual memory. Has anyone else seen this, and if so, is it a known issue? Can anyone provide any more background if they are aware of this?

At my previous company, we saw this often, and I am trying to determine if we are seeing it at my new place. At my previous environment, NPM was at 10.2, but it is at version 10.3.1 where I am at now, so if it was an issue that was resolved by a version upgrade, I might not see it. Thanks-

Find more posts tagged with

virtual_memory

physical_memory

Accepted answers

All comments

ssadlocha

Checking to see if anyone has any input yet on this. Please let me know if you have any information that might be helpful.

adatole

What platform are we talking about?

Meanwhile, this post:

http://thwack.solarwinds.com/message/163840#163840

Gives you an idea that reporting "Memory" can be highly subjective and even the built in OS-based tools often betray a bias of the coder more than an empirical representation of the system.

ssadlocha

In my original post I was referring to Windows servers, but I have also noticed it to a lesser degree with Linux servers. The post you linked is very helpful in understanding how memory is displayed though, thanks for that.