New
#11
Huge pagefile
-
-
New #12
So, is the consensus that if you have 16 Gigs+ of ram, you don't need page file?
-
-
New #14
I have my page file manually set to 400 MB minimum (The minimum recommended by Windows for crash dumps to work properly) and 2048MB maximum (which is slightly more than the 1905MB Windows recommends for my system). I have 8GB of RAM and a fairly fast SATA SSD in my laptop and so far Windows hasn't used more than the 400MB I initially allocated to it.
-
New #15
The pagefile size can increase to the the size of your RAM after a system crash if your pagefile size is automatically set.
For the next 4 weeks after a crash, the system managed page file will have a minimum size at least the size of the amount of ram in the system - 16GB in my case. Delete the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\LastCrashTime and the page file will revert to its former System Managed size - 2432MB in my case .I hope this tip helps anyone mystified by the same issue.
-
New #16
Needing a pagefile is not related to ssd or hdd. It is related to how much RAM you have, and how much RAM PC needs.
Typically PCs with 1-4 GB will page frequently.
Typically PCs with 8 GB will page now and then, and PCs with 16+ GB will hardly ever page.
It really depends on what user does. 16 GB certainly seems excessive.
There is no one right answer as to what is optimum for a given user.
Manually setting the pagefile is simply a trade off between actual size and required size.
OP just needs to gradually reduce size a couple GB or so and assess if any issues in OPs normal working patterns.
Always good to leave some margin of course.
-
New #17
I've set my minimum to 1GB and maximum to 4GB. My laptop's got 8GB ram and I can only use 6.95GB of it.
-
New #18
In order to set a proper pagefile size, you have to understand what paging is and what applications use it and how much. Just because you have 16GB RAM, does not mean you need a 16GB page file. Removing paging completely is not a good idea either.
Check Task Manager often and see how much paging is committed, I am almost certain 4GB will be more than enough, unless you run a lot of heavy applications at the same time. I am currently using 185MB paging on a system with 8GB of RAM and 2 VMs running at 100% CPU usage.
-
-
-
New #20
Hi there
@CountMike
and where do you think that 2.6 GB is cached -- yes it's in an OS file !!!!!
the paging pool is currently the in demand processes which might be sufficient - depending on what's running or not.
The OS is designed to run with a paging file -- size required depends on all sorts of factors but it's definitely a bad idea to run with none at all.
If you are just doing basic internet surfing, e-shopping (inc banking etc) email or running a spread sheet or a word doc then it won't make any difference but once you start loading the system up say with VM's and other things you will definitely need a paging file.
With VM's though it is worth taking a small hit on their performance since you want to avoid "double paging" i.e where both the HOST and the VM's are both paging especially if the VM's are on slower HDD's. That's a separate issue though and if you are using LINUX as a VM then swap placement areas become important - best to have a native formatted HDD / SSD for that =-- have a tiny Windows virtual HDD for the main /boot partition and have the rest of the Virtual OS on the SSD / HDD with at least / (root) and swap on the native device. That way you should avoid the HOST machine doing double paging when the Linux VM is loaded up or busy or needing its swap space..
Cheers
jimbo
Quote
Related Discussions
