Re: [Bug-wget] wget output, dot vs bar differences

[Hrvoje Niksic]

julius <address@hidden> writes:
> 10650K .......... .......... .......... .......... .......... 97% 11.3M 0s
> 10700K .......... .......... .......... .......... .......... 98% 10.5M 0s
> 10750K .......... .......... .......... .......... .......... 98% 16.3M 0s
> 10800K .......... .......... .......... .......... .......... 99% 15.6M 0s
> 10850K .......... .......... .......... .......... .......... 99% 18.3M 0s
> 10900K .......... .......... .......... .......... .......... 99% 24.9M 0s
> 10950K                                                       100%  399G=3.7s
>
> at the end, the 11.3M for example probably shows the current speed.

11.3M is the speed for the current line of dots.  Progress display tries
to bit smarter about what constitutes the "current" speed.

> since the download goes up 50K very steady, how do you calculate the
> number at the end?

That looks like a bug.  The number at the end is supposed to be
10950K/3.7s =~ 2.89 MB/s.

> and why is there no time dimension?

The "=3.7s" is the time it took for the whole download to finish.  Do
you mean something else by "time dimension"?

> capturint the output of --progress=bar:force shows:
>
> 2% [>                                      ] 19,818,776  4.38M/s  eta 3m 39s
>
> i can see that in the later one the file size goes up with changing
> values, values around 50K while in the first its exactly 50K. why the
> difference?

In thermometer mode each "=" is a percentage of file size, the exact
percentage depending on line width.  As more of the file gets
downloaded, the displayed file size increases.  The progress bar is
printed no more than five times per second, so if the file is being
downloaded at 4.4 MB/s, reported size will increase by around 900K each
time around.

The "dots" display works differently: each dot represents a fixed amount
of downloaded content, 1K by default.  Dots are grouped in rows, each
consisting of 50 dots, which means that each row represents 50K *by
definition*.  The faster the download, the faster the rows of dots will
be printed -- in a 4.4 MB/s download, Wget will print around 90 rows per
second.  For dot display to be useful with currently typical bandwidths,
you should use --progress=dot:mega, or something like that.  (You can
use this to gauge what bandwidths Wget was originally written for -- we
were looking at slowly progressing individual dots *all the time*.)

> why not add the whole size that has been downloaded, which is some MB/s ? 

That is exactly what is printed at the end:

100%[===============================================>] 124,858      321KB/s   
in 0.4s   

124,858 is the file size, 321 KB/s is the average speed, and 0.4s is the
download time.