Windows Page File/Memory Optimization

  • Two Factor Authentication is now available on BeyondUnreal Forums. To configure it, visit your Profile and look for the "Two Step Verification" option on the left side. We can send codes via email (may be slower) or you can set up any TOTP Authenticator app on your phone (Authy, Google Authenticator, etc) to deliver codes. It is highly recommended that you configure this to keep your account safe.

Jacks:Revenge

╠╣E╚╚O
Jun 18, 2006
10,065
218
63
somewhere; sometime?
ok so this is something that has bugged me for years and every once in awhile it comes up when I'm looking for ways to help increase performance in certain games. most recently, it came up when I encountered the common issues that have been reported with Grand Theft Auto IV.

all things considered, I've got a pretty above average system.
quad core @ 2.5 with an ATI HD4870 @ 512 onboard.
the processor and GPU alone usually pound through most games and I've found that (to date) I don't really need anything more than 3 gigs RAM. my OS is 64-bit so if I ever wanted 4gigs or more I'm ready.

the part where I always get confused is when people talk about being able to squeeze extra bits of performance out of any machine by altering RAM in your Page File. but there's so many conflicting reports about how exactly you should go about doing this.

a Google search on the matter can provide up to 5-6 different methods for "properly" optimizing your memory.
sometimes after reading through an article on the subject, I think I'm about to grasp it. but then I read another article that contradicts the first. and then I read a third article which says that the previous two aren't necessarily correct. meanwhile, a 4th article will claim that NO method is correct and that they're all dangerous.
the bottom line seems to be that there's no single/definite way to optimize your page file without potentially harming your system.

I guess my question is; what's the deal with RAM optimization through Windows Page File?
is there any correct method to this madness?
should I even bother?

here, this is what mine looks like right now:
28bv22u.jpg


how should I "optimize" that or make it any better?
is there even a point to this when I already have over 3g RAM?

some articles claim that optimizing will only yield results on a system with less than a gig. others claim that even people with a lot of RAM could still benefit.

needless to say, I'm confused as f*ck.
 
Last edited:

-n7-

Member
May 12, 2006
411
0
16
Edmonton, AB
Leave it alone.

Seriously.

Get more RAM if you are running out or getting close to.
That will provide actual benefits.

Messing with the pagefile will not provide anything worth getting exciting about, & can definitely break things.
 

SkaarjMaster

enemy of time
Sep 1, 2000
4,872
11
38
Sarasota, FL
With XP, I set my page file to the same initial and maximum size (custom size) and this is usually around 2 GB (2048 MB); just noticed you have 3 GB now and that's fine also, so 3072 MB if you want (I have this on my latest system I believe). The only reason to keep the same initial and max sizes is so the page file doesn't get fragmented, but sometimes it can still get fragmented but the chances are a lot less. I've been messing with this issue since Win98SE (possibly since Win95 but not sure exactly) and have no idea what this does in Vista/7, but there is a lot of conflicting stuff out there. It's still kinda confusing even once you know the difference between RAM and virtual memory, etc.
 

Jacks:Revenge

╠╣E╚╚O
Jun 18, 2006
10,065
218
63
somewhere; sometime?
so the consensus appears to be that there's no real point in messing with it on a system that already has 3 or more gigs RAM.

I mean 99% of the time I don't seem to run into any memory issues. it was just something I've always heard about (the page file deal) and never really understood.
 

Wormbo

Administrator
Staff member
Jun 4, 2001
5,913
36
48
Germany
www.koehler-homepage.de
Ideally the page file should be on the system drive and not be fragmented too much. You can easily achieve that with on-board tools if the system drive has enough free disk space. Simply disable the page file on the system drive (requires a reboot; if you don't like the thought of not having any page file at all, simply create one on another drive, but with that amount of RAM windows should works fine without it for a while), defrag the drive and then enable the page file again. If after deactivating the page file, there's still lots of green scattered over the graph, then that's likely the hibernation mode file. Disable hibernation mode for defragging if it really prevents larger blocks of free space.

A fixed page file size prevents the file from growing uncontrollably and getting scattered all over the available space. Creating a fresh one with enough large blocks of free space available should cause only little fragmentation or even none at all.

To find out what size you need, start the most RAM-demanding combination of apps that you will ever be using and check page file usage in Task Manager. Not sure how Windows calculates its recommendation, but you should hardly ever get a problem with 2 to 3 GB if you already have that much RAM.