Re:HTTP/2 and HTTP/3 explained
by GoblinSlayer on Friday March 15, 2024 @03:45AM
(#39713033)
In wireshark logs that I saw TCP almost immediately resends the lost packet and exponentially slows down after the resent packet is lost.
That's just plain wrong. I commented in more depth in https://news.ycombinator.com/item?id=39709591. In short, TCP treats packet loss as congestion signal and slows down. If the packet loss was due to congestion that's absolutely the correct response and it increases TCP's "goodput". But if the packet was lost due to noise then it has the opposite effect and goodput plummets to a fraction of what the link is capable of.