Nagle's algorithm: Difference between revisions

Revision as of 17:43, 9 May 2018

Revision as of 17:44, 9 May 2018

Line 34:

</blockquote>

Nagle considers delayed ACKs a "bad idea", since the application layer does not usually respond within the time window.<ref>{{cite web|last1=Nagle|first1=John|title=Sigh. If you're doing bulk file transfers, you never hit that problem. (reply 9048947)|url=https://news.ycombinator.com/item?id=9048947|website=Hacker News|accessdate=9 May 2018}}</ref> On the protocalprotocol level, he recommends disabling "delayed ACK" (for example, by <code>TCP_QUICKACK</code> on Linux) instead of his algorithm, as "quick" ACKs do not incur as much overhead as many small packets do.<ref>{{cite web|last1=Nagle|first1=John|title=That fixed 200ms ACK delay timer was a horrible mistake. Why 200ms? Human reaction time. (reply 9050645)|url=https://news.ycombinator.com/item?id=9050645|website=Hacker News|accessdate=9 May 2018}}</ref>

==Negative effect on larger writes==