Referring to older post about getting the numbers of memory and CPU usage HERE, lets go deeper into the memory part.
The script collect the usage of memory active, instead of memory consumed. It is the amount of memory that is actively used, as estimated by VMkernel based on recently touched memory pages (REF).
That is not a very good indicator if you're doing a VM resizing plan, or chargeback. To get a better view, use consumed memory counter instead. This is closest guess of what is the amount of memory used by the guest VM.
Or, get Veeam One monitor ;-)
Read more about memory counters
Sunday, September 9, 2012
Active memory or consumed memory
Labels:
memory,
troubleshooting,
veeam,
vm,
vmware
Wednesday, September 5, 2012
Windows Slowdown, Investigated and Identified
reblogging from http://randomascii.wordpress.com/2012/09/04/windows-slowdown-investigated-and-identified/
all credits goes to original author, I'm merely archiving it for my personal future reference.
in short, if your free memory is high, and cached is low, there's a culprit in there.
all credits goes to original author, I'm merely archiving it for my personal future reference.
in short, if your free memory is high, and cached is low, there's a culprit in there.
Labels:
slowdown,
sysadmin,
troubleshooting,
windows
Subscribe to:
Posts (Atom)