Which memory metric should I be using to measure a VMs memory use? An end user recently asked me why the memory usage inside of their VM (i.e. Task Manager) is different from what they see in their vROPS dashboard (both in real time and historical). A legitimate question that I've never asked myself.
To measure a VMs memory use in vROPS, assuming it should mirror what the OS is reporting, which metric should I be using? Guest Active Memory (%), Usage %, Workload %. something else?
Thank you daphnissov. Heres my takeaway.
After some testing (see screenshot below), it seems the "Memory|Usage (%)" and "Memory|Workload (%)" metrics are the closest to what the guest OS (Task Manger) reports. "Active Memory" and "Consumed Memory" are too extreme compared to Task Manager.
Based on the testing (and the author's recommendation in the comments section of the article you provided), I think I should use the "Memory|Workload (%)" metric in my VM dashboard going forward. Would you agree that is the best solution to give users an accurate representation of their VMs memory activity?
The "Memory|Utilization (KB)" and "Guest|Needed Memory (KB)" metrics seem to be useful as well, especially as the are used by the capacity engine and rightsizing recommendations. I will be including these metrics as supplements in my VM dashboard.
I just tell my end users not to use the memory metrics in vrops as it is a mine field trying to explain the differences to application users that just about know there own name to log in in the mornings.
Made easy for me as we "officially" dont use vrops for VM monitoring