You said there will be I-FAAST 3.0 at previous posts. Where is it?

Hi Akif,

Yes I did mention this, and it is still "in the oven". Like many of the technologies we R&D, they can take many months (even years), to make it into a production release. You'll see I-FAAST 3.0 in the future, but even then it may be called by a different name.

I'm trialling DK2008 now but notice that it does not defrag the \$Extend\$UsnJrnl file. That file is becoming more and more fragmented on my system.
I tried a 'boot time' defrag with DK2008 and that did nothing to that file.
DK2008 continues to report that file as fragmented (so obviously the program recognises the file and that there's a problem with it).

Can you please explain?
Oliver

Hello, I sent you a comment a number of days ago about my observation (whilst trialling Diskeeper 2008) of DK2008's inability to defragment a system file - \$Extend\$UsnJrnl - but still recognise that the file was fragmented in the report. That file was cleaned up quickly by Perfectdisk with an offline defrag. DK's offline defrag did nothing with it.

I note that my comment to you has not appeared in your blog. Can you please advise why you did not post that comment?

Oliver

Hi Oliver,

A future build of Diskeeper will defragment this file at bootime (it's in the works). Microsoft is also planning some changes to make defragmenting this file more efficient.

-Michael

I note that my comment to you has not appeared in your blog. Can you please advise why you did not post that comment?

Hi Donn,

I do not see a comment listing from you, please resubmit it. Also, we have a spam filter on the blog, so please do not send URLs. Sorry for the trouble.

-Michael

On page 5, you use HDTach to measure the read speed of drives, with and without Diskeeper 2007/2008 installed. Doesn't this program read sequentially across the disk from the first cluster to the last? If so, file fragmentation should have no significant effect. The only effect would be if background processes were running that were competing with the HDTach benchmark and the background processes were accessing fragmented files, or creating files, etc.

Indeed, the results show no significant improvement in the average read speed when Diskeeper is installed, compared with when it is not.

However, comparing DK2007 with DK2008, the burst speed suddenly doubles when DK2008 is installed. Since the burst speed is the speed at which data is transferred from the hard drives on-board cache to the PC, DK should not make a difference here. Didn't you suspect that this result was somewhat of an anomaly?

Hi Andy,

I did not perform these tests. I'm also not familar with HDtach, but reading the description of the software it states it does raw reads.

I do agree that the purpose of this tool would not accurately test fragmentation, but can provide evidence that an running application does not impact the HDtach measures. I believe this was, or was one of, the author's purposes for this test.

As for the v2008 results, I'm not fluent enough with this other tool to speculate, but on a surface level it can certainly be an anomaly.

I'd have to run the the tests myself, and use a kernel debugger (check Fast I/O), to properly comment.