{"id":115667,"date":"2024-05-10T13:52:08","date_gmt":"2024-05-10T11:52:08","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/predlozhenie-po-vklyucheniyu-rezhima-tcp_nodelay-po-umolchaniyu"},"modified":"2024-05-10T13:52:08","modified_gmt":"2024-05-10T11:52:08","slug":"predlozhenie-po-vklyucheniyu-rezhima-tcp_nodelay-po-umolchaniyu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/predlozhenie-po-vklyucheniyu-rezhima-tcp_nodelay-po-umolchaniyu","title":{"rendered":"Proposal to include TCP_NODELAY mode by default","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Marc Brooker, an engineer at Amazon Web Services (AWS), addressed misconceptions related to enhancing the efficiency of small message transmission using Nagle's algorithm, which is the default in the TCP\/IP stack. The recommendations center around disabling Nagle's algorithm by default, which can be done for specific applications by setting the TCP_NODELAY option for network sockets using the setsockopt call, a practice already established in projects like Node.js and curl. <\/p>\n
Nagle's algorithm allows for aggregating small messages to reduce traffic \u2014 it suspends the sending of new TCP segments until an acknowledgment is received for previously sent data. For example, without aggregation, sending 1 byte additionally sends 40 bytes with TCP and IP packet headers. Under modern conditions, using Nagle's algorithm leads to noticeable increases in latency, which are unacceptable for interactive and distributed applications. <\/p>\n
There are three main arguments in favor of using the TCP_NODELAY option by default, which disables Nagle's algorithm: <\/p>\n
\n
The incompatibility of Nagle's algorithm with the \"delayed ACK\" optimization, where the ACK response is not sent immediately but after receiving the response data, poses a problem. In Nagle's algorithm, the arrival of the ACK packet signals the sending of aggregated data, and if the ACK packet does not arrive, sending occurs only after a timeout. Thus, a vicious cycle arises where the ACK packet does not serve as a signal, as the other side does not receive data due to its accumulation on the sender's side, and the sender does not send it until timeout because it does not receive the ACK packet.\n