Man of Honour
- Joined
- 17 Nov 2003
- Posts
- 36,750
- Location
- Southampton, UK
Why do people assume that Windows will use the pagefile over RAM anyway?
Moving PageFile
- Thread starter indyit
- Start date
Forgetting the pagefile for a minute another thing to check is to see if you have a hiberfil.sys in the root of c:? If you do and you don't hibernate you can get rid of that.
Open a CMD window and type 'powercfg -h off' and then it should let you delete it.
tbh if you are clever about where you install/save stuff and use something like CCleaner to keep on top of your temp files and hotfix uninstallers etc then 40GB should be more than enough for the o/s inc a decent pagefile.
Open a CMD window and type 'powercfg -h off' and then it should let you delete it.
tbh if you are clever about where you install/save stuff and use something like CCleaner to keep on top of your temp files and hotfix uninstallers etc then 40GB should be more than enough for the o/s inc a decent pagefile.
Though back on the pagefile thing for a bit Windows will always use it no matter how much ram you have and you definitely don't want to turn it off. But as for the recommended size there is no definitive size or rule based on amount of memory or the like as it's usage will vary with the machines usage. If you say have an application server with a fairly consistent usage in terms of what it is running, memory load etc then you could spend ages profiling it's memory usage and working out what is best but the time really wouldn't be worth the effort.
I think where the set your page file minimum size to that same as your physical ram comes from is from debugging and taking full memory dumps in the case of blue screens etc. The reason being is that when Windows blue screens the minimum it should remember is where on the disk the page file is and how big it is, that way it safely knows that if it needs to dump XGB of ram it has XGB if disk space to write it in with out overwriting other data. I believe this then gets renamed to your dmp file and the pagefile gets re-done on next boot.
I think where the set your page file minimum size to that same as your physical ram comes from is from debugging and taking full memory dumps in the case of blue screens etc. The reason being is that when Windows blue screens the minimum it should remember is where on the disk the page file is and how big it is, that way it safely knows that if it needs to dump XGB of ram it has XGB if disk space to write it in with out overwriting other data. I believe this then gets renamed to your dmp file and the pagefile gets re-done on next boot.
Yeah I turned that off, hibernation is redundant now so I took that away which freed up quite a bit of space. I have near to nothing installed on the SSD, but a lot of "programdata" and some games' save files end up on C. It's fully possible to have a 8GB pagefile on my SSD now.
That said I brought this thread up was for two reasons:
1) What are the pros/cons/consequences of having the pagefile elsewhere
2) What are the pros/cons/consequences of reducing the pagefile size.
From what I've gathered:
1) Leave it on the SSD
2) There are varying opinions on what size the pagefile should be but generally in my case have at least 4GB or just let Windows regulate it. I've taken the middle ground by leaving it in a 4 - 8 range.
