(Wish) TIME LEFT (for operations - synchronize, copy)....

[TotalCommander]

Hello everybody!

How 'bout putting some TIME LEFT when comparing files (synchronize directories) or copy from to? With time left we can evaluate how long it will take in some cases (same size files)... i think the pictures below shows it clearly:


Image: http://inlinethumb09.webshots.com/41800/2805433830103765406S600x600Q85.jpg


Image: http://inlinethumb49.webshots.com/27312/2629328690103765406S600x600Q85.jpg

So?

[Sir_SiLvA]

and you calculate that time HOW ?

[HolgerK]

... or copy from to? ...
http://inlinethumb49.webshots.com/27312/2629328690103765406S600x600Q85.jpg

Copy: 934.6 kbytes/s, 28m

Regards,
Holger

[sqa_wizard]

"Time left calculation" values are always wrong. There are too much dependencies which influences the real value.

The copy process consists at least of :
- reading the file entry from FAT
- reading the first block of source data
- writing the file entry to FAT
- writing the first block of destination data
- reading the 2nd block of source data
- ...

For several small files you have to read the FAT entries very often, which results in slow transfer rates.

Even the time for a single big file will vary:
- First KBytes will be transfered very fast (while filling the file cache) and the rest is transfered normal.
- Writing a file in an uninterrupted sequence to free sectors is much faster than spreading into parts all over the harddisk

Further more, your copy process is not the only one who accesses the disk. Other processes such as antivirus and even Windows is interrupting your transfer always but not constantly.

All programs I found are just rough guessing the time with variations of -100 to + 100 percent, which is not worth the effort IMHO ...

Just to mention the installation program saying "Time left: 2 sec" and staying another 3 minutes on the screen

[TotalCommander]

When I was thinking to the "Time left" I meant the time from the begining operation till now, not the time from now till the end of operation (it will always look wrong).

Because some times I use a lot of programs in the same time and the speed decrease. But if I look from time to time, I remember that for the first 25 % it takes around 5 mins and after 10 mins It reached anly 28%. So I can close some of my programs to finish sooner the operation....

So the TIME LEFT from the beginning, not TIME REMAINING till the end...

[HolgerK]

With time left we can evaluate how long it will take in some cases (same size files)...

Anyway, I don't see a big advantage in showing an elapsed time. This is nothing else than calculating: remaining_time * actual_progress / (100% - actual_progress).
Personal, I am more interested in the information how long i have to wait until the operation is finished.

But if I look from time to time, I remember that for the first 25 % it takes around 5 mins and after 10 mins It reached anly 28%

Isn't it easier to remember the transfer speed for the first 25% and compare it with the actual speed?
Or to remember the remaining time at 25 % (15min) and compare it with the remaining time at 28% (25.7min): "huuh increasing..."

So I can close some of my programs to finish sooner the operation....

Only a speed curve versus time diagram can deliver a useful information for your decision to close other processes.
And even with this diagram you have to know which program should be stopped because it interferes TC's progress.

Kind regards,
Holger

[petermad]

2TotalCommander

So the TIME LEFT from the beginning, not TIME REMAINING till the end...

To me "time left" and "time remaining" means the same and are interchangeable. I think the appropriate phrase for what you request is "time elapsed".

Apart from that I agree with HolgerK

[Hacker]

AutoHotkey: Show elapsed / remaining / total / start / finish times in title bar of progress dialogs
And there is a more advanced AutoIT script somewhere out there (here), too.

Roman