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.
Lee
Mark was writing about Windows Vista and Server 2008. This Article, probably written in 2009, supports your claim and does relate to Windows 7:
http://windows.microsoft.com/en-gb/windows/change-virtual-memory-size#1TC=windows-7
With the substantial increases in installed RAM users have been installing since 2009 I would doubt that many would consider a multiplier of 3 is necessary.
Quite obviously, neither does Mark ! : )
...and neither do I as I was just quoting the formula that code writer used for "system managed size" before 64bit OS became the new standard. It will suit the OP fine on his 32bit OS. I set 6GB max for my x64 OS but it just sits on the 3372mb min. size and never moves. No expanding and contracting and I do use Photoshop, but only lightly.
3x max ram is a totally ridiculous formula nowadays of course (except for 32bit) but yes, there are plenty of people out their with 32GB of ram on their "casual use" computer and 1 or 2TB hard drives, who would indeed use that X3 "formula" (example in this thread: "what is the feasibility of using a small SSD drive to just store the entire PF on?"), along with the regular use of reg. cleaners and other snake oil performance "optimizers".
Teeth gnashing stuff to see, but these users are not stupid, they are just sailing in a sea of uncontrolled conflicting internet advice and knowledge. They find more and more solid ground as experience grows. Hopefully anyway : )
It is hard to dissuade them, because that well meaning advice (and not so well meaning) is all over the internet telling them to use such "magic" PF formulas and "performance enhancing" software!
I still can't believe the amount PC rubbish I used to believe 20yrs. ago or for that matter, 5yrs ago! :-0
Mithandir
does the pagefile get cleared upon shutdown/restart? If this is so, then what's all the talk about fragmentation?
When a Windows Managed pagefile is cleared on shutdown it leaves the disk space vacated as small fragments of free disk space scattered across the partition. This means that the next time files are written they are scattered in small fragments across the partition where the free disk space exists, the only exception being tiny files which are smaller than the pockets of free disk space.
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.
Another thought: multipliers and formulas used for the PF size will probably vary from each user's individual needs.
