http://bugzilla.novell.com/show_bug.cgi?id=623148
http://bugzilla.novell.com/show_bug.cgi?id=623148#c1
Reinhard Max
[...] Is this as it should be?
With such large files and high transfer rates, I would expect that the time it takes to write out the dots (one per 1kB) does have a significant impact on the total transfer rate.
I recognize that using the "--progress=dot" option means that more info is written to the screen, but should this be included in the calculation of transfer rate. Thoughts?
Well, wget does not display the speed of the network link, but the overall throughput, so anything that slows down the wget process (be it CPU load, disk load, or even writing out the progress indicator) affects the actual transfer rate (from the remote server all the way to the local disk).
Note: The way we ran into the problem is that our tests actually write the wget output to a file, and this forces the use of the "dot" reporting style.
Some possible ways to get around the slowdown: 1. --progress=bar:force enforces the bar style progress meter even when writing to a file. 2. --progress=dot:mega uses less dots per transferred data and thus should speed things up. 3. When using wget in a scripted environment, it might be appropriate to use the -nv option to switch off the progress indicator completely and only display summary information and errors. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.