The commit Charge is not how much the paging file is actually used, it's how much the system has allocated, in case it needs it.
So if you have it set to defualt, which is auto, it will grow significantly when you launch a large program.
I knew this but went looking for more information and:
In general, unless you have good reason not to, it's best to just let Windows manage the page file. No program data will be paged out to disk unless absolutely necessary and the larger pool of virtual address space tremendously improves how efficiently Windows can handle the physical memory you have.
This ^^ is the answer, leave Windows to do its thing or set a large enough static pagefile. Disabling it gives no improvement in performance.
If anyone wants more info then the following might be of use:
This question is prompted by the following regularly observed phenomena I'd like to find an explanation for: Current commit is regularly higher than Physical usage + Pagefile size. What's up with ...
superuser.com
This System Information is from Process Explorer. There is still physical memory available but the system shows nearly no RAM left. Task Manager also shows that about 74% of total RAM is used. Si...
superuser.com
Regarding ED and VR memory use I've setup some proper monitoring now and on initial startup ED and WMR will use about 8.5gb of RAM with an appropriate commit. However, I have seen that the commit has grown considerably when I've finished playing so something is changing, I'm going to keep an eye on the actual RAM usage now.
Superfetch is a whole other kit and kaboodle, if you have recent machine with a fair amount of RAM, then you probably won't notice it,
If you have a recent machine with SSD's you don't need.
So it seems that Windows 10 will automatically enable/disable superfetch on each drive depending on what's most appropriate and will be disabled on SSDs.
Given that I still have spinning disks in my system I've re-enabled superfetch.
I have read some horror stories of people getting 100% SSD disk use before disabling, but there may be something else going on. For me I can't see a difference between on/off.
Further reading/viewing:
In the course of another thread trying to track down my Standby RAM usage, I looked at my Superfetch service. Lo and behold it was enabled, something which is not supposed to happen as having Windows installed on an SSD is supposed to automatically disable it. Given modern SSD endurance is...
community.amd.com
Microsoft tech troubleshooter extraordinaire Gov Maharaj and I help walk you through troubleshooting solutions to your tech support problems. If you have a problem you want to send us, you can use the
channel9.msdn.com
But having to limit SSD writes on an OS level will not do much, yes, they have a limited amount of writes to them but those are far more than most would ever reach.
For instance you would have to write an excess of 100GB to your M.2 for 50 years before you start seeing real degradation.
I have had mine for about two years and already considering upgrading.
I was really interested in this and found this from Techreport:
techreport.com
Some of the drives first started reporting errors between 200-300TB of writes.
One of my drives has a warranty of 300TBw or 10 years. At 100GB per day my warranty would run out after 8 years and 4 months and the first errors in the test would be ~5 years 5 months.
However, to be fair unrecoverable errors were way, way beyond that and realistically I will certainly will never come close to that level of use,
(although I do have a tendency to hang on to working drives for a long time with 2x ~12 year old drives in my current system.)