This is a great article by VMware expert Gabri van Zanten. It also is a great example of why I think Dynamic Memory is going to be a very popular feature.
In short, Gabri rightly states that using Large Pages is a tradeoff between memory savings and performance benefits. He also doubts if the use of Large Pages really bring any benefit to your application. I think that in VDI environments people want to maximize the use of their RAM without it having to be an exact science that people like Gabri have to write multiple articles about. As far as I have seen, Dynamic Memory does the job fine in a fairly transparent, ‘real-time’ way. It also reduces the risk of excessive swapping and prevents the risk of kernel mode RAM to be swapped out.
Anyway, still a great article to read by Gabri:
Everybody talks about the benefits of Transparent Page Sharing in vSphere environments and how they reduce the amount of memory needed in your vSphere host. Thanks to Transparent Page Sharing memory overcommit in a production environment has become mainstream.
Not long ago I’ve written these two posts:
- “Memory overcommit in production” http://www.gabesvirtualworld.com/memory-overcommit-in-production-yes-yes-yes/ which explains how Transparent Page Sharing works and how to use it in production.
- Another post of mine explains more on memory compression and how ESX starts ballooning and swapping when there is memory contention, see: http://www.gabesvirtualworld.com/memory-management-and-compression-in-vsphere-4-1/.
While writing that post I started thinking about the impact of Large Pages and Transparent Page Sharing on memory usage and how this would make it a more difficult in your day to day admin job to monitor your real free memory on the ESX host. This could therefore lead to less VMs per host.
Let me explain what the problem is.