Why tcp_nodelay default to on?

[Igor Sysoev]

On Nov 3, 2012, at 9:02 , howard chen wrote:

> From the doc: http://wiki.nginx.org/ReadMoreAboutTcpNodelay
> 
> TCP_NODELAY is for a specific purpose; to disable the Nagle buffering algorithm. It should only be set for applications that send frequent small bursts of information without getting an immediate response, where timely delivery of data is required (the canonical example is mouse movements).
> 
> 
> 
> So my understanding for most web app, it should be disabled so we can use the "Nagle buffering algorithm", only disable when you have special need, like logging mouse movements as in the example?
> 
http://nginx.org/en/docs/http/ngx_http_core_module.html#tcp_nodelay

    The option is enabled only when a connection is transitioned into the keep-alive state. 

Otherwise there is 100ms delay when nginx sends response tail in the last incomplete TCP packet.


--
Igor Sysoev
http://nginx.com/support.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20121103/8557b6c4/attachment.html>