4 ms·
No, assumign an already estabilished connection, TCP is just as fast if there's no packet loss, except for the tiny amount of time that the additional TCP stack
by fulafel 3y ago
No, assumign an already estabilished connection, TCP is just as fast if there's no packet loss, except for the tiny amount of time that the additional TCP stack logic takes on the CPU.
See eg here: https://cloud.google.com/blog/products/networking/using-netperf-and-ping-to-measure-network-latency https://cloud.google.com/blog/products/networking/using-netp...
- vetrom 3y agoYou may have induced latency driven by window sizing/scaling/acknowledgement RTT as well.
- fulafel 3y agoIf TCP says "you can't send more data yet because of congestion control" (like hitting the congestion window limit) then I guess you can categorise that as latency, depends on your viewpoint. RTT of acknowledgements shouldn't normally enter into it, no? You can send while previously unacknowledged data is in flight (as long as congestion control state allows).