🚀 go-pugleaf

Ed H. <nospam@usit.net> wrote in article
<35f2c738.19269758@msnews.microsoft.com>...
> 
> Silly me.  I was assuming you had Diskeeper set to a low background
> priority so it wouldn't take away from system performance and
> potentially increase defragmentation.
> 
> I guess if you misuse any tool, it won't work as advertised.
> -- 

You have apparently not used Diskeeper on large fragmented files or on
large, badly fragmented drives.  You can set the diskeeper priority as low
as you want, but once it starts working on a large (100+ MB) file, it
doesn't matter how low its priority is, it will still slow your system down
significantly (assuming a single processor system) while it works on each
individual file.  If you don't believe me, try the following.  Create ten
100+ MB files in the NTFS drive of your choice.  Next, compress those five
files.  Next, decompress those files.  Next, compress them again.  Your
drive should now be badly fragmented (at least those ten files).  Now start
diskeeper running in the background at its lowest priority (set to
defragment that drive, of course).  After a couple of minutes, start some
cpu and disk intensive operation (such as 3D rendering) and see what
happens to your performance.  If diskeeper, never actually starts
defragmenting any large files, performance may not be greatly affected. 
However, once it starts defragmenting a large file, system performance will
slow to a crawl.

-Steve