Network & Infrastructure / IPv6, TCP & Transport Engineering
TCP window scaling and a high-bandwidth path that stays slow
A long-distance transfer uses only a fraction of link capacity despite low packet loss. The receiver's effective window may be smaller than the bandwidth-delay product.
Environment and inputs: Dual-stack routed networks and transport endpoints; validate the complete path and the active operating-system version. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Record handshake window-scale negotiation, advertised windows, round-trip time, application read rate and endpoint buffer limits. Capture the handshake because later packets alone may not reveal the negotiated scale.
Explain the result
TCP throughput is constrained by both flow control and congestion control. A receiver-limited flow can stay slow on an otherwise uncongested path when it cannot keep enough data in flight.
Plan the fix
Size endpoint and application buffering for the measured workload within memory limits. Fix slow application consumption before assuming that a larger kernel maximum will improve performance.
Check the result and rollback
Compare sustained goodput, window behavior and memory use under realistic concurrency. Restore prior tuning if memory pressure rises or latency worsens without a measured increase in useful throughput.