Daniel Stenberg wrote:
On Thu, 30 Apr 2015, Tim Ruehsen wrote:
Originally, Gisle talked about CPU cycles, not elapsed time.
That is quite a difference...
Thousands of cycles per invoke * many invokes = measurable elapsed time
True it seems, but Iv'e not tried SSL times on a local-net.
Some more info with the aid of the URL you provided:
wget -q -O NUL
"https://download-installer.cdn.mozilla.net/pub/firefox/releases/37.0.2/win32/en-GB/Firefox
Setup 37.0.2.exe"
results in 9931 DLL attach/detaches!
For a 40 MByte file that is approx. 1 new thread per 4 kByte read.
I was thinking that increasing read-buffer would help. But where?
The code is bit of a mess IMHO. Increasing the Rx buffer in
fd_read_body() didn't help. Is this the chief in this regard?
Without getting any numbers, I can see in 'Process Explorer'
that all those run_with_timeout() calls (and no '-T0') amount
to some more user+kernel time. I guess using a profiler is next.
Or maybe someone knows of a Win-program that can report total
CPU (kernel/user) time from the cmd-line?
BTW. My ISP gives me 25 Mbit/s in and 10 MBit/s out.
--
--gv
