For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

A New and Better Nagle Algorithm

Last year I wrote about the tradeoffs embedded in Nagle's algorithm. I also described our "AutoNagle" setting, which meant to take some of the pain out of figuring out what to do with this feature. B...
Published May 11, 2017
Version 1.0
application delivery
LTM
nagle's algorithm
Martin_Duke's avatar
Ret. Employee
I work in the Office of the CTO on both F5's standards engagement process in general, and specifically on the application of transport-layer innovation to F5's product line. F5 sponsors my service as Transport Area Director at the Internet Engineering Task Force (IETF), where I help to administer standards development worldwide.
View Profile
Martin_Duke's avatar
Ret. Employee
I work in the Office of the CTO on both F5's standards engagement process in general, and specifically on the application of transport-layer innovation to F5's product line. F5 sponsors my service as Transport Area Director at the Internet Engineering Task Force (IETF), where I help to administer standards development worldwide.
View Profile
AlgebraicMirror's avatar
AlgebraicMirror
Icon for Altostratus rankAltostratus
May 15, 2017

This is a really great article, and I'm really glad you guys decided to implement this feature. I've worked for a number of companies that used F5 equipment, and only at one of them was there a good understanding of what Nagle's algorithm was, and only at that company did anyone attempt to correctly turn it on or off. Even still, a lot of the time we didn't have the time to try to figure out whether Nagle was beneficial for a given application, so we just defaulted to leaving it off, accepting that we'd not be optimized. Having this be handled automatically is great and should benefit almost everybody.