This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
hi guys i want to know what page file size is recommended for a 4gb RAM . coz im into gaming and my pc is about 5 yrs old and i just want to know if there is such a thing about a recommended page file size in 4gb RAMS.
i have a :
Operating System
Windows 7 Ultimate 32-bit SP1, 4gb RAM ,and 500gb hdd
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
thanks for the advice sir leefrost. btw mine is a win7 32bit & 4gb ram not 64bit.
"For W7 in brief:
min size = RAM + 300mb = 3372mb (for 4GB of ram)
Max size = RAM x 3 = 9216mb (for 4GB of ram)"
That info. applies to the paging file of both 32bit or 64bit W7.
Erwin
When you have your C partition on a conventional fixed hard drive ( drive other than a solid state drive) and you use a Windows managed page file, it creates a situation where fragmentation occurs more quickly. The pagefile gets scattered all over the disk. If file fragments between scattered parts of the pagefile are removed the next file to be written, if it is of any size, is immediately in a fragmented state. This is because the available free disk space is fragmented. Using a third party defragmenter like Defraggler you can defragment free disk space.
Mithandir
With a fixed size page file, disk space is allocated to the pagefile equal to the size of the page file. The allocated space cannot be written to by other software and the page file is always located at the position on the drive where it is created. If the page file is contiguous at the time it is created it will always remain contiguous. For this reason the page file ceases to contribute to file fragmentation.
You ideally should not separate the pagefile from the system partition, although you might split the pagefile between two partitions but with the reduction in the cost of sold state drives buying tiny drives does not represent value for money. It is wasteful use of a free internal drive bay.
I really like this response as most people don't tell you this. For this reason, I've been wanting to create a set size as opposed to a variable size (min. to max.) Also, I do however create my page file on a second drive since my operating system lives on a Solid State Drive and constant writes to a pagefile just reduce life expectancy. Of course, this assumes the pagefile continually gets written to. I've experimented with size (setting it to 100Mb min.) and never seen it grow above that..... leading me to believe the Pagefile isn't even being used at all in my system (Win7 x64 with 4GB Ram, 232.89 GB useable SSD and 469.9 GB useable HD.) So, this brings me back to the original question, (assuming I want 1 size PF: Min.=Max.) set on my secondary drive (469.9GB E: drive) what size should the PageFile be? 3x RAM (which = 12,288 Mb not 9,000 ish like one person said...) I know this is an old thread but, people (like me) still come across it with the same question. Your response would be greatly appreciated.
I understand where/why you give this formula.... I don't understand the math though..... if I have 4GB of ram then shouldn't minimum size be = 4396MB? Are you quoting 3372MB due to RAM limitations of 32 bit Windows? I'm assuming we all know 1GB = 1024MB's....
Lee
It wasn't rubbish 20 years ago, or even 5 years ago. The difference is that Microsoft moved Windows forward but some computer users don't or can't move forward.. "well, it worked in Windows 95".. LOL
