I have also noticed that DF is very much slow when defragging a lot of small files than other defraggers. I thought it was that way though.
I don't know if this is a bug or not but DF definitely needs a speed improvement in the defragging algorithm department.
OS = win xp pro 32 bit
CPU = AMD A8-5500, quad core, 3.2 GHz
HDD = Seagate Barracuda 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5, no RAID
RAM = 8 GB ddr3
One other 1 tb HDD, has win 7 but is not visible to this OS when win xp is running.
Not many files, approx 25,700 small files
Time for individual files varies, apparently by file size
Seconds per file = 1, 3, 12, 13, maybe a few seconds more for some
No delay between each file
At start, Defraggler estimates > 1 day,
After 38 minutes estimate = 5.00 hrs
After 42 minutes estimate = 4.00 hrs
After 43 minutes estimate = 3.50 hrs
After 44 minutes estimate = 2.25 hrs
After 45 minutes estimate = 2.00 hrs
After 51 minutes estimate = 0.50 hrs
After 54 minutes estimate = 10 minutes
After 55 minutes estimate = 5 minutes
After 58 minutes estimate = 2 minutes
After 58 minutes = done
actual time = about 58 minutes
There's my data. Analyze away.
Comment, I never met an app that did well at estimating completion time.
Don't know why. Some backup programs predict 4 days when they start but they finish in a bout 30-40 min.
Edited for clarity.
Offtopic:
You are running WinXP x86 WITH 8GB RAM?!!!
Your Operating System is probably "viewing" 3.5 GB at best. All the rest is lost.
Offtopic:
You are running WinXP x86 WITH 8GB RAM?!!!
Your Operating System is probably "viewing" 3.5 GB at best. All the rest is lost.
Yes. Good catch.
I hadn't even thought about that, just remembered that 8 gb is installed.
Its a dual boot setup. The computer came with win 7 on the factory HDD and 8 GB RAM.
I put win xp on a second HDD, and as you say, win xp recognizes about 3.3 gb RAM.
Fwiw, not off topic at all imho, you were double checking.
It would be exceptionally wasteful for the computer to be supplied with 8 GB of RAM in a 32 bit system.
Even Windows 7 could not use the top half.
You have a friend here that is willing to find a good home for your spare RAM :D
Is it possible that you were supplied with 64 bit hardware and possibly 64 bit Windows 7,
but for some reason your installed Windows XP is only 32 bit ?
@ Alan: "You have a friend here that is willing to find a good home for your spare RAM"
Thanks. What a guy, always thinking of others. Warms the heart.
And you are right, win 7 and the hardware are 64 bit, but win xp is 32 bit. Made the dual boot business sort of a challenge.
Back on topic, is there anything else I can do to help with the original issue of this investigation?
It doesn't happen on win xp 32 bit 3.3 gb RAM, etc, etc as far as I can see. That is, there is no discernable pause when switching from one file to another, and the completion time seems reasonable.
I have also noticed that DF is very much slow when defragging a lot of small files than other defraggers.
I think it's just one of those things where moving a ton of small files just takes more time versus moving larger files, well that's what I've noticed using most defrag tools and I've used many of them.
It's also up to the defrag algorithm, so maybe Defraggler is trying to do a better job at the added expense of it taking more time.
I'm also having this issue. Normal defrag is very, very slow on some drives (it ran overnight but managed to get to 1% on a 750GB drive) and quick defrag is like the normal defrag but inefficient. On some drives the normal defrag runs smoothly.
I'm on Win7 x64 SP1 with the latest updates.
Small up.
Defrag is extremely slow. Defrag was started about 30h ago. Now it's estimate completion in 12 Hours but this time increase by 30 minutes every hour...
If I compute my own estimated completion (based on two screenshots spaced 15 hours apart) i found : 1306 hours left (54 days)... ( It's a 540GB NTFS partition)
Yesterday I compute 48 days left...</span></span>
Edit : My hard drive is out of order. It has too many bad sectors.