Opened 14 years ago

Last modified 14 years ago

#4873 new Bug report

transfer time left & throughput rate invalid if limits are set during transfer

Reported by: Minsc TDP Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version: WinXP


The throughput rate and time left estimates are correct assuming the transfer limits have not been configured.

If they are configured during a transfer, the limit is applied properly to the live transfer without interruption (a very useful feature) but the time left and throughput rate are based on a running average including all previous data prior to the limit being set. All of that data is no longer applicable.

A simple solution would be to simply reset the time left estimate and throughput counters anytime the limits are set (or make that an option).

Another option is to separate throughput into "Throughput Overall" and "Throughput Now". For time left, it simply needs to be a best estimate given the current data throughput, so it simply should not take into consideration any transfer speed data prior to about 1 minute from "now".

Change History (1)

comment:1 by Minsc TDP, 14 years ago

A simple way to observe this is, with a long running transfer, set a limit for a while and then increase it. You'll notice the time left countdown is accelerated and the KB/s is simply incorrect though slowly being adjusted over time.

Note: See TracTickets for help on using tickets.