On Sat, 27 Jul 2013, Michael Dowling wrote:
I reran my various performance tests, and I can confirm that adding CURLOPT_TCP_NODELAY resolves the performance issue.
Great!
Is there any way curl could automatically detect when it would be appropriate to use this option by default?
Not that I can think of. I would guess that it is hard for us to second-guess the TCP stack's behavior generically. I think we should start with considering some mention about this in the section where CURLOPT_READFUNCTION is described, but I'm not sure what to say...
-- / daniel.haxx.se ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
