The sender manages to maintain close to this "in flight" value throughout the whole period.ģ) One RTT later, the sender receives ACKs for the 100 KB that wasn't lost and manages to transmit a further 100 KB without any errors. In the first TCP-Trace chart below, we see the 100 KB successful burst, the yellow area with no packets, a few subsequent packets that made it through, then one RTT later the second 100 KB burst.Ģ) The server's receive window is close to 1 MB, but the sender appears to use its own RWIN of 261,288 bytes as its own transmit "limit". Here are my key observations (with some supporting TCP Trace charts below):ġ) The client sends a large burst of 250 KB, but large portions are lost after the first 100 KB. I'll define the large burst of packets as the start of the pattern.
A particular pattern is repeated again and again - at roughly 7 second intervals - with about 500,000 KB transferred per interval. There's a very consistent regularity to the way the packets flow from the client to the server.
0 kommentar(er)
