Windows paging file on virtual servers

[MancTech]

Hi,

 

We have almost all our servers now virtualised using Hyper-V stored on 3 server 2019 Hyper-V hosts.

 

Its my understanding that virtual servers should have no need for a paging file except for crash log files and maybe domain controllers. As long as the server has enough RAM to deal with day to day demands surely any local stored files are just going to put extra load on the local storage array especially when you multiply that by 10 servers per host?

 

Researching on the web I seem to come across conflicting information on this so hoping someone can point me in the right direction. Do you guys run paging files and let windows manage their size on your virtual servers?

 

Thanks

[Michael]

I leave it 'as is' virtual or physical, a paging file is always going to be required regardless of server roles.

 

To minimise the requirement, just be more generous with your disk and memory allocations.

[psydii]

I think this article suggested a paging file in each VM is recommended to act as a buffer if the hyper-v memory manager isn't able to adjust quickly enough for the chaning workload. It also offers some performance counters to keep an eye on, and actions to take if they are being crossed.

 

https://learn.microsoft.com/en-us/windows-server/administration/performance-tuning/role/hyper-v-server/memory-performance#correct-memory-sizing-for-child-partitions

[Tefters]

Leave paging file as default and let it manage itself.

 

Rule of thumb used to be 1.5x amount of ram and on a separate disk but I gave that up years ago.

[PotNoodleTech]

I have never removed page files on any of mine - doesnt sounds like a good idea.

[dmj]

I think the idea that you shouldn't have swap/paging comes from containerised environments, rather than virtualised. Even that is changing with kubernetes swap on (although it doesn't support windows yet).