On Sat, 26 Sep 2015, Tatsuhiro Tsujikawa wrote:
I could reproduce this. First thing I noticed was TCP_NODELAY. If I
enabled it with --tcp-nodelay option, I immediately got around 50MiB/s. But
it is not still as fast as nghttp and normal HTTP/1 transfer. I did quick
profiling using google perftools, and it reported the following:
Thank you so much for your keen eyes and detailed report. I'll do my home work
now and see what I can do to elimitate some of that.
I'm also thinking we should probably consider TCP_NODELAY set by default, at
least for HTTP/2 ...
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
