3 ms·
It's amazing how many learned lessons we have to relearn. Should we learn why Nagle's algorithm exists and how best to exploit it? Nah, just disable it.
by zamalek 4y ago
It's amazing how many learned lessons we have to relearn. Should we learn why Nagle's algorithm exists and how best to exploit it? Nah, just disable it.
- withinboredom 4y ago[flagged]
- zamadatix 4y agoShould we learn why it exists and how to exploit it? Absolutely. At the same time Nagle himself showed up in the comments about the previous article saying disabled by default (what Go was doing) is probably the better approach these days so I don’t think it’s accurate or helpful to claim calls for it are just a result of people that don’t understand it.
- withinboredom 4y agoThe thing it was trying to solve (and does solve) is specifically when there is congestion (lots of packet drops beyond slow-start). If you have those network conditions, AND you aren't filling packets ... then Nagle's Algorithm is for you. That was the entire point of the article.
- bvrmn 4y agoYou really should not rely on OS and make small `send()` syscalls in hope it would magically work. Too much overhead.