Originally posted by: wanderer27
I also have mine set to flush out (empty) the Swapfile whenever I shutdown - it's a Registry setting.
It's a bit slower on shutdown but reduces the chance of internal Pagefile fragmentation.
That registry key is really for security purposes not so much for fragmentation.
It can also be set via group policy. Run gpedit.msc and goto Computer | Windows Settings | Security Settings | Local Policies | Security Options and look for "Shutdown: Clear virtual memory pagefile"
If using XP/2003 or above I *think* your built in defragmenter will handle the pagefile for you. If not you can use sysinternals pagedefrag from Microsoft:
http://technet.microsoft.com/e...nternals/bb897426.aspx
To clarify earlier statements:
1. The overall rule is to let Windows handle it.
2. If you have more than one drive you will see the tiniest of benefits by having the pagefile on a separate spindle from your OS/Programs. Separate partition on a single drive does *not* count. Even on a separate spindle the benifit will take a benchmark to see and you still won't see it under most normal operating loads.
3. With Vista at least (I can't believe I've been using it so long I'm rusty at XP) you can still do "system managed size" on a per drive rather than per system basis.
4. Be aware that pagefile settings can have an impact on your ability to obtain a memory dump. My rules on this: If you know how to load windbg make sure you can get a dump. If you are configuring a production server make sure you can get a dump. Anything else you needn't be concerned much.
5. Even with multiple spindles...unless you are configuring a high load SQL server it's probably not worth the hassle to get the tiniest of fractions of performance. See #1.
6. If you ever turn off your pagefile you're a retard. Don't argue this unless you've done your research (at which point you will concede and turn it on) and you are ready to bring your A-game to the argument.