How to optimize Windows XP pagefile settings

vividstag31 said:Instead, you actually have to sit down and do the work right. They just don't get it and aren't capable of it.
For real though.

Why am I even wasting my breath on this nonsense? One look at that brainless comment above tells me everything I need to know.

Goodnight, folks!

Well, you might think it’s nonsense. But if you’ve ever actually dabbled in programming in your life, you’ll understand exactly what I mean. If not, then I suppose I shouldn't be surprised.

By the way, where on earth did Lawrence Miller4 disappear to? Did he perhaps try something out, or what?

I’m personally quite interested in this issue too, even though I have a pretty good idea of how the attempt will turn out.

Lawrence Miller4 said:I wasn't trying to be insulting.
Mmm, yeah—running VS .NET 2003, FTP, HTTP servers, plus some memory-hungry Adobe programs and the rest of the stuff everyone uses (like Winamp, VLC Media Player, etc.)... plus my machine is crunching through 800 threads at once without HT... I'm pretty sure that's barely touching 30% of my resources.

And look, if you honestly think my rig is the top-of-the-line powerhouse currently on the market, then maybe time has just passed you by a bit.

The only Linux distros I haven't messed with are Knoppix and Corel. Right now, I'm running SuSET 8.2.

One more thing—it's not exactly hard to pick up a Pentium 4 with 512 MB RAM these days. I figure someone who actually lives and breathes computers can afford a decent machine without breaking the bank. It seems to me you might be one of those people who either won't or can't afford a better setup, and honestly, I feel for you—but that doesn't give you the right to judge everyone else the way you just did. But hey, that's just my two cents.

Well, there he goes, feeling offended. 😁

Everything except the servers runs on a PII 333 MHz (overclocked to 416🙂 with 320MB RAM, all on a P2B board, which means ATA33). I even do video editing—you know, pulling clips off a camera and stuff. It doesn't exactly fly, but it gets the job done. Since this isn't my primary livelihood... it's fine.

Besides, I don't think there's any way to force Windows to max out the RAM before it starts hitting the page file. 😢
Unless you just disable the latter entirely.😁

A buddy of mine has several HDDs, each with its own OS installed, and he uses them for different tasks. But since you're running servers, that's probably not an option for you. Your other choice—since you make your living doing this—is to just buy another computer, man, since they aren't exactly expensive anymore. Run your servers on one and your multimedia on the other. Problem solved. I don't know if I'm misreading the situation here, but if you're running FTP and HTTP servers, people are connecting to them to upload or download things. In that case, the HDD is working hard, especially if you have multiple drives hooked up. It might not even be about the page file.
It’s pointless to guess like this. You really have to see it in person to know.

PS. Don't get all worked up; I didn't mean anything by it. Though, you have to admit, some people just love to nitpick. I work with someone like that all the time. 😁 😁

Look, Bryan Sanchez86, I’m telling you, it’s not about being insulted or anything, I just can't stand when people start making massive generalizations. It's like seeing people around me constantly dropping cash on the latest tech just so they can brag about having "new gear," even though they haven't got a clue what they actually bought or how it works.

By the way, I don't think there's any real way to force Windows to max out its RAM before it even touches the page file. Unless, of course, you just kill off the page file entirely.

Even if you flip that switch to disable the page file, the system is still gonna use it. Seriously, try disabling it, reboot Windows, and then check Task Manager—you’ll see that page file Usage isn't sitting at zero; it’s always hanging out at some value. It feels like that option to turn it off is basically just for show.

I see vividstag31 is itching to hear how my little experiment turned out, so... here's the scoop:

I set up a RAM disk drive and shoved the page file right onto it. Since my virtual drive driver was being stingy and only let me make a 100 MB RAM drive, I carved out a 95 MB page file on it. And honestly? I can definitely feel the speed boost. It’s not thrashing the hard drive nearly as much as it used to. On top of that little guy in the RAM, I’ve still got a fixed 1GB page file sitting on my C drive.

I did a bit of digging online and saw other folks trying this exact thing, but I kept running into people who were rocking more than 1 GB of RAM. Most of them who gave it a shot noticed a pretty massive jump in performance, so hey, for all you guys out there sitting on a mountain of RAM, give this a shot—maybe it'll make your life with Windows a little less miserable! 🙂 Maybe. 😁

All you gotta do is hunt down a RAM disk program that actually lets you scale the size however you want.

I'm running RAID 0 myself—honestly, I doubt you'd even notice a speed boost.

Hm... Theoretically, I can't quite wrap my head around where that speed boost is coming from, but I’ll give it a shot. I tried pushing 2GB on my end, but once I realized how little sense that made, I just sold off the extra RAM.

And what are you using to define the RAM disk?

On second thought...

It’s honestly absurd to suggest that converting "excess" RAM into a performance boost actually works. It just goes to show how little Microsoft truly understands their own architecture. Logic dictates that you should be running purely on raw RAM, and only switch over to using the swap or the
page file Usage
when you've completely run out of space, right?🤔

neonhawk53 said:The only issue is finding a RAM disk utility that actually lets you scale the size however you want.

I'm running a RAID 0 setup myself, and honestly, I doubt anyone would even notice a speed boost.

RAID 0?

RAM is still significantly faster. Besides, the whole RAM disk trick works because Windows doesn't know how to utilize memory effectively to begin with.

Here are some solutions:

I’m dealing with the exact same headache, and this fix works perfectly for me.
👍 👍 👍 👍

What kind of hardware specs are we talking about here for this to actually run smoothly?

Pentium 4 with 256MB DDR and a 40GB hard drive

Nothing changed on my laptop.
I’ll try testing this on my desktop, which runs a 2.6GHz Intel. It’s packed with 1.5GB of RAM—three 512MB sticks—but honestly, compared to the 256MB I started with, I haven't felt any real boost. I am leaning toward that solution involving moving the page file Usage to a RAM disk, even though, as I mentioned before, it feels like a total long shot. Then again, thinking about it now, it wouldn't be the first—or the last—ridiculous move from Microsoft.

Lawrence Miller4 said:Even if you turn off the page file Usage, it seems to keep running anyway—I guess it just doesn't listen.

I don't know—never actually tried it, I guess. 🙂

I set up a RAM disk and shoved my page file onto it—since the virtual drive driver limited me to just 100 MB, I managed to squeeze a 95 MB page file in there. I guess I can actually feel the speed boost, maybe.

Could you explain how to actually do that? Or maybe just drop a link—if it helps, I’m hoping this old junker of mine might pick up the pace a little.

Skines this little tool to get things moving. Personally, I’m not exactly jumping for joy over this software—I’m pretty sure there’s something way more polished out there—but hey, it gets the job done if you need it.

Once you’ve got the program installed, you’ll see a new device pop up in your Device Manager representing that "virtual disk." Just right-click its properties and crank that virtual disk size up to whatever the maximum limit the driver will let you get away with. After that, head over to Control Panel settings -> Advanced -> performanca Settings -> Advanced -> Change and set up an additional page file, but make sure you point it specifically to that "disk" you just whipped up!

Voila!
Good luck!

http://www.cenatek.com/product_ramdisk.cfm
http://www.ramdisk.tk/
http://www.setiathomescreensaverspee...setiathome.htm
http://www.majorgeeks.com/download271.html

Got a few more for you guys.

Lawrence Miller4 said:Hey everyone!

It’s honestly driving me nuts when I’m working on my PC for more than a little bit. After I've been at it for a while, Windows starts going absolutely crazy with all this constant reading and writing to the page file, and man, it just taaaaaakes forever. I wouldn't even complain if I was running some ancient dinosaur, but I've got a Pentium 4, 2.2GHz, 512MB RAM, and a 40GB disk. ..

1. You really ought to put the page file on its own separate partition

2. In your specific situation, that partition should probably be around 1.25 GB

3. And it definitely needs to be FAT32 (since it handles smaller volumes way faster)

4. Then, inside Windows (under the virtual memory management settings), you basically "move" the virtual memory over to that partition—let's call it the swap drive—and set both the minimum and maximum SWAP size to the same 1.20 GB value

5. Turn off those annoying "disk full" notifications

6. Go into your environment variables and move the TMP and TEMP variables over to the D: drive (or honestly, anywhere else, just keep them off the C: drive

7. Make sure to completely disable system restore, clear out all your temp folders, and get rid of any other useless junk sitting on the C: drive

8. Give the PC a restart

9. Then, when things are quiet, run a defrag on the C: drive

10. Turn system restore back on, but only for the C: drive (you don't really need it for the others)

11. And then just sit back and watch how smooth the PC runs...

Whatever, man
rowdytrucker27😉

Is there actually any legitimate reason why keeping the Page file on its own partition is supposedly better? To me, it seems completely pointless, yet I feel like I’ve heard this suggestion a hundred times already.

How exactly do you think he decides? What’s the actual payoff there?

Honestly, it doesn't matter where it sits if it isn't a temporary file—meaning, if you just set the size yourself. Years ago, people used to criticize Microsoft for making the swap file land on whatever drive it felt like. Ideally, you'd be able to define that file starting from the very end of the disk, from the last cluster moving upward, for as much space as needed. But Microsoft just isn't capable of thinking that way.

If you set a specific size, Windows won't waste all that time constantly resizing it.
Using a dedicated partition with a fixed size means memory stays allocated the same way every time. No need for constant defragmentation.

Having a second physical drive also helps speed things up since the system can read programs and handle the swap independently.