Discussion in 'Operating Systems' started by Mr.Bigtime, Apr 20, 2009.
Best article on page file cons and pros I read in a long time. Very exhaustive.
I don't want to put a tl;dr version, prefer you guys read it yourself.
If you still think its too long, scroll to bottom to conclusions.
I keep mine on a seperate drive along with 90% percent of my apps and games and vm images.
1 drive, boot and operation system
2nd drive programs,games,other stuff
3,backup and pagefile.......system information software says 8% of pagefile is in use when system is running
system really fast
I havent't had my pagefile enabled in years and I have yet to run into a game or program error because of not having one.
yes you have 16GB how much is skyrim using for you ?
And yet, the conclusion says basically this : test it out yourself.
Helpful, ain't it?
Idk, I havent played it yet. i have to finish other games first.
Because 32-bit applications on Win64 are limited to no more then 4GB of usage by themselves [assuming compiled with PAE].
And there is the slight increase in memory usage when running without a pagefile to consider, as all commits MUST be put into physical RAM, even if no data has been written to it yet. I've seen some apps that actually do worse without a pagefile for this reason.
The only real reason to bother to go without a pagefile would be to save HDD space [which is ever less of a concern these days], or more likely, prolonging the lifespan of a SSD drive. Still, as we start to get more x64 apps that will gladly eat more then 4GB of RAM, the no pagefile crowd is going to start to run into applications that will happily eat into 8GB RAM like its nothing.
When 64-bit apps become the norm, I believe this'd already be a 64GB RAM club.
I mean, getting 16GB of DDR3 is already cheap now, and the transition to 64-bit apps are still slow, despite 64-bit OSes have sprung out for a few years already.
Compiled with LAA enabled (not PAE). Multiple 32bit apps can consume much more.
I disabled mine and never had that issue. Might just be you, but thats interesting though.
That error only occurs if your system reaches the commit limit, usually with 4GB or less ram.
Another reason to have it on (Just turned mine back on) is for a crash dump file, twice now in the last week I've had a random loss of power to my system and I have no idea why, so I thought I know I'll consult the crash dump file, went to access it and was like oh yeah no pagefile, no crash dump file, thats useful lol
So now hopefully if it happens again I might be able to find out the cause
Before getting the extra 8gb, the only game that I see that has some problems I think was MW3, it didn't dump but it freezes for 3 secs and then starts again. In a 2 hrs session, it happened twice...
Could be cause of the pagefile?
Nah it basically says there's absolutely no difference either way.
I thought Vista or Win 7 was smart enough to use ram instead of pagefile when there is enough ram
No, I played MW3 with PF disabled no problem.
that is up to debate, hell this whole topic is and can be up for debate.
Well for me when I disabled PageFile my crashes are gone in Fallout 3 and New Vegas, and I don't have any problems with disabled PF ;-)
Thanks for tips all xD