Mine as well, ANYBODY can finish that sentence anyway they want. It still works. My main page file is static (size unchanging), in its own partition on a separate drive from the Windows partition. That partition is the first on the drive, at the outer edge of the platters. It is twice my RAM size but I also have a small (512 MB) static swap file on the system (C:\) partition. I experimented by changing the settings so I had a Windows managed page file on the C partition (20 GB of unfragmented free space) and it was a bit more sluggish when for example I had Firefox* open with about 8 tabs and I started another memory hungry app (Xnews). Of course playing around with settings is fun and can be instructive, but there are no magic settings which will make up for not having enough RAM for your usage pattern .

* I have set Firefox to release memory when minimised, and at the moment it shows 163,692 K memory usage, but when I minimise it it goes down to 57,620 K.

Type: “about:config” in Firefox address bar and hit Enter:

In the appeared window press the button that is labeled I’ll be careful, I promise!

Right click in the page and select: New -> Boolean

In the new appeared window type: config.trim_on_minimize and press OK

Select True value in the appeared window and press Enter

Restart Firefox.
Years ago on my site one of my mods - who was really quite an expert - was a huge proponent of making the pagefile static (setting min & max the same) to avoid fragmentation. The theory of course was that when the system reboots all data in VIRTUAL memory is released and any fragmentation would be minimal. The fact is, however, that even when the setting is dynamic Windows only expands the pagefile when necessary and on reboot it resets to the MINIMUM size, all data is released, and the result is essentially exactly the same. Bottom line, leave the pagefile alone. Pretty much anything you read in forums about adjusting the size of the pagefile is ABSOLUTE nonsense.

Quantos - no offense but your post above is not only not relevant to the OP's question, it is also incorrect. Windows is not always in control of what is or is not paged to virtual memory. But I really don't want to get into a whole pagefile thing here. These THREADS became so inane and contentious that I eventually banned them on my forum 5 years ago.re. Allan's post, I wholeheartedly agree. I don't think I made it clear enough that the difference on my system (XP pro SP3 1 GB RAM) between a tweaked-to-*censored* page file setup and letting Windows manage the whole shebang was absolutely minimal, and IMHO not worth the time I spent making the adjustments.
Quote from: Allan on November 11, 2009, 05:52:48 AM

Bottom line, leave the pagefile alone. Pretty much anything you read in forums about adjusting the size of the pagefile is absolute nonsense.

* I have set Firefox to release memory when minimised, and at the moment it shows 163,692 K memory usage, but when I minimise it it goes down to 57,620 K.

Type: “about:config” in Firefox address bar and hit Enter:

In the appeared window press the button that is labeled I’ll be careful, I promise!

Right click in the page and select: New -> Boolean

In the new appeared window type: config.trim_on_minimize and press OK

Select True value in the appeared window and press Enter

Restart Firefox.

SysInternals has a tool that defragments the page file at boot. I think it was called "PageDefrag". It takes forever though and I certainly didn't see much of an improvement.