Last Modified: Sep 13, 2023
Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 13.1.1, 14.0.0, 126.96.36.199, 188.8.131.52
14.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 11.5.7
Opened: Apr 25, 2018 Severity: 4-Minor
When Nagle is enabled in the TCP profile, the number of PUSH flags generated by the BIG-IP system drops substantially compared to the Nagle-disabled case, or to the Nagle-enabled case prior to v12.1.2-HF1. This matters most when there is a single outstanding unsent segment in the send buffer awaiting acknowledgment of all other data.
If the client withholds ACKs, this can save handset power, but it also causes Nagle's algorithm to withhold the last bit of data, increasing latency.
-- Nagle is enabled. -- Running BIG-IP software versions later than v12.1.2-HF1. Note: The problem is only impactful when the client withholds ACKs when there is no PUSH flag.
Set Nagle to the 'Auto' setting or 'Disabled'. Mote: To take advantage of some of the Nagle benefits, use 'Auto'.
Revised PUSH flag setting logic to set the flag in cases where sending is Nagle-limited.