Quote:
Imperator Fyron said:
Make sure to disable virtual memory _before_ doing the defragmentation, so that the drive can be defragmented as much as possible. Reenable virtual memory after it the defragmentation process is completed. This ensures an even more continuous block of HD clusters for the swap file. Also, you might consider disabling the auto-magic management. It tends to be unnecessary (assuming you have the size set to a large enough amount) and slows down the computer when Windows changes the size of the swap file all the time. You can do this by setting the minimum size to the same value as the maximum size. This will also have the advantage of locking the swap file in place, preventing it from being created in fragmented parts of the hard drive as it is resized. It will stay in the same clusters of the drive. It is critical to defragment before fixing the size of the swap file for this very reason.
|
If you're into all that, you might want to drop by
{here} as well. This little freeware program will defrag the (now permanant) windows swapfile. Windows tends to create it fragmented. They have other small, free, well-thought out, utilites on that site.
Quote:
Having a separate drive partition for the swap file can be handy as well (assuming you fix its size).
|
I've heard that's not too great an idea. The separate partition helps prevent data from fragmenting the swapfile, that's true. But the drive heads really have to work overtime, reading two separate directories, zipping from file table to data part -- not so speedy. Now a separate hard drive to contain the swapfile, sure, that'll help.