System: Windows XP Pro with SP3
there is some strange behaviour seems to be all related to either the underlying system or maybe the original Ultradefrag design. I have observed the following for several versions of Ultradefrag, now:
When defagging big volumes with plenty of files and a high fill rate Ultradefrag does not haul all non-continous data to free space at the very end of the media. In contrast it hauls a certain amount of data to the end of the media, but then starts to haul the data to the beginning and "tries" to fit all gaps towards the beginning. Alt least Ultradefrag accepts gaps and some fragmented areas, though it should have created a continuous record, due to configuration.
Corresponding to the parameter refresh_interval, set in the configuration file, the Windows GUI of Ultradefrag performs the refresh of the display content. As noticable by the I/O activity LED the current defragmentation cycle is temporarily halted, right in the split second the refresh of the display happens. Right after the cycle continues a/o is replaced by a new cycle. While this oddity is happening hundreds of Thousands of times during one defragmentation process, I suspect it to have an undeniable impact on the whole duration. Is there a way to lower the outcast or at least to solve this impact by conceptional changes in Ultradefrag?
Best Regards Udo Erwin Müller