I have 8gb ram . so i think it is enough.The only way to reduce the page file is to purchase more physical (ram) memory. The reason the page file increases is when ram is at full capacity.
I don't think so either.I have 8gb ram . so i think it is enough.
Is that realistic with only 8GB of ram?Unless your OS drive is really crammed on free space, there's no need to disable it. Although you can if you like, you just won't get any BSOD crash logs with it disabled. Personally, I've been without a page file on and off for the past 10 years and never noticed any performance difference either way.
Depends on the tasks you perform and if they need the page file or not. Everything I've done, I've not had an app crash on me yet with it disabled in systems with 8GB of RAM. My main system has had 16GB of RAM for a while now tho. Like the past 5-years. Before that was 6-8GB. I run VMs, do video and photo editing from time to time, play some games, and a bunch of other random things that only a storage nut like myself would do. lolIs that realistic with only 8GB of ram?
Set it to custom, 1GB initial , 8GB max. Then monitor page file growth. If it ever grows to 2GB, then set initial to 2GB.My page file size is 5.6 GB . I have 8gb ram . It says that the recommended size is 1914 MB in settings but it is taking 5.6 GB. It is set to automatic manage only.
Untrue. You've just been extremely fortunate not to have hit the wall. When there is no more RAM or swap space available to fulfill a memory request, Windows is prone to crash with sometimes catastrophic results. I've lost count of the number of times I've had to clean up the mess when users thought themselves smarter than the Windows engineers when it came to managing memory......but Windows isn't going to kill him or corrupt anything by not having it.
I forgot to mention, a disclaimer to my statement sorry. "In my experience," I have yet to see Windows crash due to the PF disabled. Actually, I think i'm going to try to get it to today lol.Untrue. You've just been extremely fortunate not to have hit the wall. When there is no more RAM or swap space available to fulfill a memory request, Windows is prone to crash with sometimes catastrophic results. I've lost count of the number of times I've had to clean up the mess when users thought themselves smarter than the Windows engineers when it came to managing memory.
Exactly. I did happen to test things out with the PF disabled on my main system. I maxed out a ram disk and then filled up the remaining free RAM space with apps. Windows starts getting unstable when there's only a few hundred MB free, the browser would crash, etc. But, it didn't fully crash the system. It still worked. Unmounted the ram disk, re-enabled PF, did a SFC /scannow and Dism /Online /Cleanup-Image /ScanHealth and got no corruption.It won't necessarily crash because of no pagefile.
But when it does crash for other reasons, it won't give you a dumpfile to diagnose.