Daniel Burrows wrote:
On Thursday 30 September 2004 10:41 am, Nikolaus Schulz wrote:e.g. when updating the packages list, aptitude displays data throughput values like "12B/s", "stalled" etc, and the progress bar doesn't move. But the real average throughput usually ranges at least above 40kB/s. Guessed cause: I'm running aptitude as an apt-proxy client, and apt-proxy seems to pass the data at very variable rates to the clients. This makes aptitude's measurement of net load and progress fail completely.aptitude just relys on apt's calculation of download rate, so I'm reassigning to apt. I personally doubt this will be "fixed", though: apt displays the current download rate,
Hmm. It does regular spot tests. More or less. Which need not describe reality when the load varies a lot.
and so naturally if nothing is being downloaded for long periods of time it'll say "stalled". I consider this a feature.
If it's a feature, it should catch the traffic peaks, but it doesn't. Probably it just doesn't poll the traffic load often enough.
In any case -- supposed the user is mainly interested in how long it may take and how quickly the overall task proceeds, I think it would make sense not to print the exact download rate at particular, random points in time, but the average for the last few seconds. -- IIRC Opera does this, for example.
This again might require to check the traffic load more often. Regards, Nikolaus