From 716fa9e840b7c3063574316fd7e0246a2bcb9332 Mon Sep 17 00:00:00 2001 From: Jasper Ras Date: Wed, 30 Jul 2025 10:37:50 +0200 Subject: vault backup: 2025-07-30 10:37:50 --- High Latency TCP Might Be Caused By TCP No Delay.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 High Latency TCP Might Be Caused By TCP No Delay.md (limited to 'High Latency TCP Might Be Caused By TCP No Delay.md') diff --git a/High Latency TCP Might Be Caused By TCP No Delay.md b/High Latency TCP Might Be Caused By TCP No Delay.md new file mode 100644 index 0000000..a70efc1 --- /dev/null +++ b/High Latency TCP Might Be Caused By TCP No Delay.md @@ -0,0 +1,14 @@ +[[TCP]] [[Networking]] + +# High Latency TCP Might Be Caused By TCP No Delay +https://brooker.co.za/blog/2024/05/09/nagle.html + +Describes a situation where two algorithms in TCP bite each other: +- Nagle's algorithm tries to prevent sending very small data packets to minimze header overhead +- Delayed ACK delays acks until data's ready + +So the first holds packets back until an ACK is received, the second holds ACK until the response is ready. + +Also due to modern systems the penalty for small datagrams is much lower. + +To get rid of Nagle's algorithm when latency matters: enable TCP_NODELAY. -- cgit v1.2.3