Jan Rysavy wrote:Is there some problem with speed and time estimation in Altap Salamander 2.5?
therube gave you an example where Salamander missed it, most likely not by some seconds caused by virus scanning, but caused by some of the inherent difficulties in estimating these times as i briefly mentioned in my previous post.
By no means did I intend to criticise or belittle Petr's work, in the contrary, my intent was to point out some of the difficulties he had to cope with, but also my astonishement that you spend that much of your resources on such a rather subordinate task. I guess this is what makes Altap Salamander such an excellent product.
Unfortunately,
therube did not give us much detail on his copy job Salamander did not estimate well. From what he says I assume he expected Salamander to do an estimation approximately like this:
Instance 1 has a tranfer rate of (8.6-3.6)*1024/(32*60) MB/s = 2.667 MB/s
Instance 2 has a transfer rate of (683-321)/(2*60+20) MB/s = 2.586 MB/s
So after 2:20, instance 2 finishes its task. Instance 1 has transfered another 373.333 MB. For the remaining 4.746.666 MB we sum up the transfer rates, so it takes another 903.6 s = 15:04. Therefore, the initial estimate for instance 1 ought to have been 15:04 + 2:20 = 17:24 (vs 32:00 by AS).
As we see from the second figure he gives us for instance 1, transfer rate indeed could have been summed up. It ended up to be (8.6-5.3)/(11*60) MB/s = 5.12 MB/s.
But the questions remain: how could one instance of AS know of the other instance's copy job, and how could AS know whether transfer rates could be summed up or whether they just were independent of each other?