Comments on: KVM vs. XenServer vs. VMware Memory Overcommitment http://www.scriptkiddie.org/blog/2010/06/27/kvm-vs-xenserver-vs-vmware-memory-overcommitment/ Climate, Technical Diving, Economics, System Engineering, IT Security Sat, 04 Feb 2012 01:27:18 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Tom http://www.scriptkiddie.org/blog/2010/06/27/kvm-vs-xenserver-vs-vmware-memory-overcommitment/comment-page-1/#comment-391 Tom Wed, 20 Apr 2011 16:33:14 +0000 http://www.scriptkiddie.org/blog/?p=160#comment-391 VMware and swapping to disk. If I understand you statement correctly - Then, Yes, ESX(i) can swap to disk. This is a last resort and should be avoided, but it can do it. ESX(i) also allows memory compression, which scans the host memory and can compress memory (think of a zip file for your memory). Memory compression should also be avoid but, it is faster than swapping memory out to disk. A good write up on ESX(i) can be found at http://blogs.vmware.com/performance/2010/07/understanding-memory-resource-management-in-vmware-esx-server-41-.html VMware and swapping to disk.

If I understand you statement correctly – Then, Yes, ESX(i) can swap to disk. This is a last resort and should be avoided, but it can do it. ESX(i) also allows memory compression, which scans the host memory and can compress memory (think of a zip file for your memory). Memory compression should also be avoid but, it is faster than swapping memory out to disk.

A good write up on ESX(i) can be found at http://blogs.vmware.com/performance/2010/07/understanding-memory-resource-management-in-vmware-esx-server-41-.html

]]>