In the previous post, I shared how we can quickly answer fundamental questions such as:
- Is there any users out there who needs more RAM or CPU?
- If yes, who and how much short are they? What time and how often they did this situation?
We covered CPU, let’s cover RAM now 🙂
RAM is not so simple. As you can see here, the Cached Memory and Free Memory are not visible outside the Guest OS. This means the counter you need to use should ideally be from the Guest, and not from the Hypervisor. The post here shows that it is possible that they differ.
The good thing in VDI is, Horizon View comes with the agent out of the box. The vRealize Operations for Horizon agent has been integrated into the base Horizon View agent. As a result, there is no need to deploy the vRealize Operations End Point agent.
Now, there are 2 ways we can determine when a user needs more RAM:
- RAM usage is high.
- Available RAM is low
I’m using the second one as it’s easier for you to see. If I show RAM Usage is 13574 MB, you still need to know the total configured RAM (e.g. 16 GB RAM), and then subtract the number. Well, that will take you to the Available RAM 🙂
Since we have lots of VDI users, the first thing we need to do is to ensure no one has high utilization that is too high, or runs out of available RAM. Super Metric comes in handy here. To find out if anyone runs out of Available RAM, you can create the super metric below.
Once you do that, it’s a matter of showing them as a line chart on the dashboard.
You do the same thing for the Committed Byte. Why do I use Committed Byte and not Memory In Use? Can you guess why?
Memory In Use can easily be determined. It is just Total RAM – Available RAM.
Committed Byte, on the other hand, does not always go hand in hand with Memory Usage. See this blog for the explanation. So we need to complement our Available RAM (MB) with Committed Memory (%). vRealize Operations for Horizon has the metric too.
The 2 super metrics will provide a good overview of the entire environment. We can just see the 2 line charts, and at a glance we know if everyone is doing well. If not, the list next to it will tell us which user was affected. The list is just using the standard View widget, which I covered in previous post.
V4V 6.2 lets you map the user name with the VM name and Windows name.
Hope that helps you in making sure your VDI users are happy, and productive! 🙂