Roger, thanks for this patch, but that's not quite what I had in
mind. Specifically, I'd like to keep calculating the download speed
exactly as now -- based only on current timings.
However, I would like the ETA to be based on the smarter model of
predicting overall speed. I'll try to modify
On Wed, 17 Apr 2002, Hrvoje Niksic wrote:
Roger, thanks for this patch, but that's not quite what I had in
mind. Specifically, I'd like to keep calculating the download speed
exactly as now -- based only on current timings.
However, I would like the ETA to be based on the smarter model of
On Tue, 9 Apr 2002, Hrvoje Niksic wrote:
I'll grab the other part and explain what curl does. It shows a current
speed based on the past five seconds,
Does it mean that the speed doesn't change for five seconds, or that you
always show the *current* speed, but relative to the last five
Daniel Stenberg [EMAIL PROTECTED] writes:
The meter is updated maximum once per second, I don't think it makes
sense to update the screen faster than that.
Maybe not, but I sort of like it. Wget's progress bar refreshes the
screen (not more than) five times per second, and I like the idea of
On 2002-04-10 01:14 +0200, Hrvoje Niksic wrote:
Andre Majorel [EMAIL PROTECTED] writes:
If find it very annoying when a downloader plays yoyo with the
remaining time. IMHO, remaining time is by nature a long term thing
and short term jitter should not cause it to go up and down.
: contact [EMAIL PROTECTED]; run by ezmlm
X-Mailing-List: [EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
To: Wget List [EMAIL PROTECTED]
Subject: Re: Current download speed in progress bar
Mail-Followup-To: Andre Majorel [EMAIL PROTECTED],
Wget List [EMAIL PROTECTED]
Mime
On Wed, 10 Apr 2002, Hrvoje Niksic wrote:
Agreed wholeheartedly, but how would you *implement* a non-jittering
ETA? Do you think it makes sense the way 1.8.1 does it, i.e. to
calculate the ETA from the average speed?
One common programming technique is the exponential decay model.
I
Roger L. Beeman [EMAIL PROTECTED] writes:
On Wed, 10 Apr 2002, Hrvoje Niksic wrote:
Agreed wholeheartedly, but how would you *implement* a non-jittering
ETA? Do you think it makes sense the way 1.8.1 does it, i.e. to
calculate the ETA from the average speed?
One common programming
Since I implemented the progress bar, I've progressively become more
and more annoyed by the fact that the download speed it reports is the
average download speed. What I'm usually much more interested in is
the current download speed.
This patch implements this change; the current download
On Tue, 9 Apr 2002, Hrvoje Niksic wrote:
Should we revert to the average speed for ETA, or is there a smarter way to
handle it? What are other downloaders doing?
I'll grab the other part and explain what curl does. It shows a current
speed based on the past five seconds, it shows an average
Hrvoje Niksic wrote:
The one remaining problem is the ETA. Based on the current speed, it
changes value wildly. Of course, over time it is generally
decreasing, but one can hardly follow it. I removed the flushing by
making sure that it's not shown more than once per second, but this
Maurice Cinquini [EMAIL PROTECTED] writes:
I don't think using only a fraction of a second is a reliable method
for estimating current bandwidth. Here are some factors that can
make for a wildly varing ETAs when just looking at the last fraction
of a second.
- TCP slow start.
-
Daniel Stenberg [EMAIL PROTECTED] writes:
On Tue, 9 Apr 2002, Hrvoje Niksic wrote:
Should we revert to the average speed for ETA, or is there a smarter way to
handle it? What are other downloaders doing?
I'll grab the other part and explain what curl does. It shows a current
speed based
Tony Lewis [EMAIL PROTECTED] writes:
I'm often annoyed by ETA estimates that make no sense. How about showing two
values -- something like:
ETA at average speed: 1:05:17
ETA at current speed: 15:05
The problem is that Wget is limited by what fits in one line. I'd
like to keep enough space
Hrvoje Niksic wrote:
I'll grab the other part and explain what curl does. It shows a
current
speed based on the past five seconds,
Does it mean that the speed doesn't change for five seconds, or that
you always show the *current* speed, but relative to the last five
seconds? I may be
Tony Lewis [EMAIL PROTECTED] writes:
Could you keep an array of speeds that is updated once a second such that
the value from six seconds ago is discarded and when the value for the
second that just ended is recorded?
Right now I'm doing that kind of trick, but for the last N reads from
the
Andre Majorel [EMAIL PROTECTED] writes:
If find it very annoying when a downloader plays yoyo with the
remaining time. IMHO, remaining time is by nature a long term thing
and short term jitter should not cause it to go up and down.
Agreed wholeheartedly, but how would you *implement* a
17 matches
Mail list logo
