Seems mad how anyone is disabling pagefile to increase performance, even with 32gb of ram for example FS2020 can crash without any pagefile.
Its a tough decision. My original decision to go to 32gig of ram is when FF15 was crashing the entire OS (and that was with a pagefile), the game has been known to use as much as 60 gig of memory in a 128 gig system.
I then originally kept pagefile enabled as it increases virtual memory capacity and on that basis for system stability is a sound decision to make.
But then I discovered in various games I had stuttering due to i/o, after lengthy diagnosis I found even though I wasnt close to using most of my ram (excluding standby cache which is supposed to be treated as free ram, but windows hesitates in this, hence me saying its bad at memory management) it was swapping out game assets to disk with 32GIG!!! of ram. As soon as I disabled swap it fixed the issues.
Currently I do have a pagefile again but its at the smallest size I can get away with, it can be as low as 256 meg (if you set to 16 it bumps up to 256), but I found a 1 gig swapfile is better for stability. Those with 16 gigs of ram or less though should not do this (I have 12 gig commit right now on my desktop), thats not enough ram to shrink the pagefile as much as that, I also have on my RTSS OSD virtual memory utilisation so I can keep an eye on it. hwinfo can monitor it, then from there can add to OSD.
For those who are interested do this.
Open task manager and click memory tab, in there you see a commit level (this is actual usage), you will also see a cached amount next to it this is typically both read and write cache combined.
Now click on open resource monitor at bottom of task manager window. From there click on memory tab.
You should now see a long bar in bottom box, this is great information.
There is - In use, Modified, Standby and Free -
In use and Modified cannot be reallocated, modified is basically data in cache not yet written to disk, so needs to be written to be freed, In use is committed ram for applications to use.
However Standby should be available to the OS to allocate, its basically read cache of data available on disk. The controversy here is when Windows runs out of "free" memory, it prefers to to use swapfile rather than allocate to apps from standby allocation. This is why it can start to use swapfile when ram commit is low.
Note as well the "in use" may be lower than the commit level, a app asks for XX amount of memory, windows allocates it and this is committing the memory, however the app may not use all of it, so the "in use" can be lower. Windows as I understand it unlike linux cannot over commit meaning its much easier to get OOM issues.
When commit reaches virtual memory capacity its game over.