Welcome! Log In Create A New Profile

Advanced

Re: Why tcp_nodelay default to on?

November 03, 2012 01:10AM
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

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Why tcp_nodelay default to on?

howard chen November 03, 2012 01:04AM

Re: Why tcp_nodelay default to on?

Igor Sysoev November 03, 2012 01:10AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 145
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready