Sat 23 Oct 2010 05:35:51 PM UTC, comment #1:
This was confusing to me when I encountered it as well. This behavior still exists in Wget 1.12.
Running
time wget -r http://freenode.net
will give a quick (~20 second) demonstration of issue.
The time reported in the "Downloaded:" summary is the time spent actually downloading (see total_download_time getting incremented in http_loop and getftp), while the difference between the starting and FINISHED time stamps reflect the total wall clock time for the wget run.
I'm not sure if you consider this source of confusion a real bug or not, but in case you do, I've attached a patch against wget-1.12 that prints a total elapsed wall clock time in addition to the time spent downloading. It only changes the summary for recursive queries, which are the ones that print the elapsed download time. The output looks like this:
--2010-10-23 13:27:18-- http://freenode.net/
...
FINISHED --2010-10-23 13:27:41--
Total wall clock time: 23s
Downloaded: 119 files, 1.1M in 6.6s (166 KB/s)
The patched wget passes the test suite included in the tarball. The man page doesn't mention the summary at the end of recursive downloads, so I didn't see anything to change there.
(file #21769)
|