The progress bar that doesn't convey any sense of progress (was Re: ...)

[Martin Pool]

2009/12/10 Gordon Tyler <gordon at doxxx.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martin Pool wrote:
>> Gordon I see in that other branch you're scaling the rates to KB, GB,
>> etc.  I thought about this in the first cut and actually rejected it
>> (though I may be wrong) for a few reasons:
>>
>>  * things tend to flap from 900kB to 1MB/s creating noise to little real benefit
>>  * in most cases both speed and size will not be phone-number-long
>> measured in KB
>>  * if you measure total transfer in GB, it will stay stuck at 1GB for
>> a long time
>>  * I don't know if it will actually show up but it may slightly slow
>> things to do fp math in here
>
> Good points.

Oh, the other point I had was that there's almost certainly code you
could reuse/adapt to do this already.

I think the next best step would be a decaying average (what is the
correct name?) as John suggested.

Also it could be nice to have -Dbytes print out, as bzr exits, the
total bytes sent/received, the total time, and the total rate, just
like we do with -Dhpss.  That may help with the "was this reasonable
overall or not" and "how close did we get to saturating the link",
while still letting the instantaneous measure tell you if we're
currently cpu, bandwidth or rtt bound.

-- 
Martin <http://launchpad.net/~mbp/>