There are two key best practices about VMware VM Windows page files (swap files).
Step 1:
I’ve found for optimum performance, it’s best to allow Windows to manage the page file. (seeĀ illustration)
Step 2:
I’ve also found it’s best to configure ESX to store the page files in a shared data-store so when VMs are vMotioned the page file is not copied to the new location. This reduces the time during the vMotion process. Read aboutĀ VMware SWAP File.
Read more aboutĀ Storing a virtual machine swap file in VMware KBĀ 1004082.
This is also a VMware Health Check best practice.
Bonus Tip:
- vSphere for BeginnersĀ – 3 Tips everyone should know when setting up vSphere for the first time.
Your Turn:
Do you have a VMware Windows Page file best practice you would like to share, please comment…
Steve Moore
If vMotion is not in use, say with VMware Essentials (not Plus), wouldn’t you think a small local RAID 1 array on each VMware host would optomize access speed to swap files that are only accessed from guests on that host?
VM Install
Hi Steve,
The simple answer to your question is ‘Yes’.
However, if you are having problems with perfornce and seeing a lot of swapping, chances are you need to increase memory on the VM and/or host.
That or cut back on how many VMs are sharing physical resources.
Joe
Steve Moore
Thanks. It’s not a matter of problems, just optimizing to avoid them. Thanks again.