Is Defraggler napping on the Job?

This is downright ridiculous. Over 30 minutes now to defrag 13GB of data (mostly large files) on a 5TB drive that is currently 54GB full.

Drive is USB3, 200MB/s Read, 190MB/s write.

I could have moved all 54GB of data off and back onto it in 20 minutes....

So what exactly is it doing?

11:20 http://i.imgur.com/JMT6DBk.jpg

11:30 http://i.imgur.com/BpaTRzZ.jpg

11:40 http://i.imgur.com/qdqFvi9.jpg

12:00 http://i.imgur.com/2oKdWMF.jpg

45 minutes currently remaining....

I don't remember this app being awful when first released.

Edit: I cancelled it about 20 minutes later and finished the defrag and optimize in under a minute with another defrag tool.

OS and DF versions?

is this the first time you have run DF on the 5TB drive?

how old is the 5TB drive?

I seem to recall reading in a past thread about DF not liking drives over 3TB (but it could just have easily been regarding some other program)

5TB is 2 weeks old nothing wrong with it.

I just downloaded the latest Defraggler from the builds page (no install, zip) 2.18.945 x64, latest as far as I can tell.

I've been using other defrag tools previously in the last week, and decided to try Defraggler again.

The drive is used primarily for raw OBS encodes only ( large 2GB+ video encodes).

Edit: OS is Windows 8.1 64 Pro

so this is the first time you have run DF on this drive?

what is your OS?

I went through the review history of back versions and discovered this;

  • v2.13.670 (18 Feb 2013)

    - Added Quick Defrag scheduling.

    • Added Fragmentation Threshold to scheduled defrag options.

    • Added option to close Defraggler after defragmentation is complete.

    • Added support for 3TB external drives.

    • Added support for drives with allocation units greater than 4KB.

    • Added support for ReFS file systems.

    • Updated translations.

    • GUI and usability improvements.

    • Minor bug fixes.

So if that was to add 3TB support, maybe 5TB isn't handled very well yet.