defrag hangs at 10%

The workaround, however, is simple: Temporarily remove the swap file before defragmenting the drive. "

Yup. I has done read that befur. And that is just what it is. A temporary workaround.

And doing it that way I would have to say it may need doing everytime defrag is run.

Put it on another partition. Set it to a Minimun size and forget it.

BillyBob

 

Everyone seems to believe the the swapfile is like every other file, and that having a defragged one is bad.
From an I/O (reading and writing) point of view, there should be little/no difference with a fragmented file or a non fragmented file.

I/O to the swapfile is done in 4K pieces, and there is no guarantee (or reason) that the next I/O is going to occur to the very next record (which would normally be the case with any other type of data file). Meaning, the disk heads are potentially going to move anyways. And, in between the heads moving to accomodate disk swapping, there could be other I/O going on from other running programs, which are going to move the heads away.

One good thing that defragging the file does, is that it places it all together AND reduces the overall fragmentation of the disk. Ie: Defrag doesn't have to step around the various pieces, as BillyBob points out.

The bad thing is that the resulting, nicely defragged file, is now going to be farther to the inside of the disk. That is, onto a slower portion.

This is one of the reasons why many people are now saying, just let windows manage it which will allow it to spread itself throughout the disk.

And, as always, buying more ram alleviates the need to even have to worry about it.

**Also, note that the PC World people haven't caught up to the fact that setting a Max on the swapfile is bad, and unnecessary to create a contigous file.
"Return to your Virtual Memory settings and enter the same value in the Minimum and Maximum boxes "

And also implicitly recommends that you use Cacheman to restrict the File Cache!!!

And, avocate running "memory managers" like FreeMem to create Free Memory!!!

At least they are a little better than PC Mag which recommends disabling VM and then running a Scandisk Thorough in order to defrag your swapfile. Then, when you are done, set the Min/Max to 2.5 times your installed ram!!!!

 

Yup. Setting a max size on the swap file is not ( or may not be ) a good idea.

With a min size of 300-400 meg there should be no need for more. But, one never knows. And 400meg out of 7.9gig is nothing.

Yes, the amount of Ram does reduce the need for swap file. BUT there is no harm done by allocating a specific minimum size and location. And by doing this it will be there immediately if needed.

I really think that the swap files gets used more than we think it does.

And by having it at a fixed Minimum size and on another partition it is ALWAYS at the same location. ( unless the user does something to change it ) It does not get moved around as it would if left for Windows to handle.

As I said before that left for Windows to handle and you have say a 20gig drive the swap file * COULD be * scattered from one end to the other.

This is one of the reasons why many people are now saying, just let windows manage it which will allow it to spread itself throughout the disk

There is no way in hell anyone will ever convince me that this does not slow Windows down.

And another thing that I have seen done. The Swap file was on the C: drive and left for Windows to handle. It was forgotten about and the drive was loaded too heavily. I do not think I need to say any more about what happened. Of course if not paying attention that could happen with a fixed size too I suppose.

Now mind you, I am referring to Win3.1 thru Windows ME.

Yes, Windows 3.1 had what was known as a PERMANENT ( size was user defineable ) swap file. And it STAYED where it was put. And it could be put at a user defined location. ( on another partition if desired ) If it recommedned 9meg I set it as 15meg. Seems rather small compared to today doesn't it ? Today that is just a good sized file.

And maybe a better and faster thing yet is to have the swap file on a drive on the 2nd controller.

I used to have that but just have not done it because of HD speeds slowing things down. The swap file was on a 500meg HD on the 2nd controller all by itself.

Set it and forget it.

And as far as defrag goes unless I have been adding or removing a lot of software none of my drives take more than 1 minute to defrag. And that includes the checking for errors. But none of my partitions are over 7.9gig. The C: drive is usually done in about 30 to 45 seconds. I usually defrag C: ( depending on what I have been doing ) about once a week. The other 5 drives get done whenever. ( again depending on what I have done wtih them )

BillyBob