[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-wget] Re: Bug in informed dowloaded time
From: |
Matthew Woehlke |
Subject: |
[Bug-wget] Re: Bug in informed dowloaded time |
Date: |
Wed, 12 Aug 2009 11:09:19 -0500 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.21) Gecko/20090320 Fedora/2.0.0.21-1.fc10 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 |
Please don't top post.
Mariano Acciardi wrote:
Are you using same version than me? Because the report is different.
I appear to be using "1.11.5-devel", however I find it unlikely that
1.11.4 would have the bug you believe it to have.
When I investigate this issue was because real time in human perception
to download is not the time wget report.
As I stated, I think this is expected.
I'm using a very slow connection (mobile gprs) and download all wap page
(16K) takes 12s in average, with wget and other programs included firefox.
I'm seeing all downloaded process, and real time to downloaded all files
takes 10-15 seconds each time. Is sure that is not 1.4 second
I really think that this is an error, I tried several times and behavior
is the same.
Well it is easy to check. Start a download, and watch closely wget's
output. From the moment you see 'Saving to:' and the progress bar appear
to the moment the progress bar indicates completion, see if you think
that amount of time is 1.4s or 11.3s. Given those numbers, it shouldn't
be difficult to tell. (Actually you would need to do this with a single
file, in which case I think you would see results similar to mine; an
overall time of about 2 seconds, and a download time of a fraction of a
second.)
My guess is that it takes quite some time to get the handshakes and such
round-tripped between you and the server. Since this time is not
included in the number wget reports, this would account for the
discrepancy you are seeing.
11 K/s and high latency sounds reasonable for the type of connection you
describe.
--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
ESIG: .sig file not available