THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question

Revision history  [back]

Revision 2
André's avatar
176
André
updated 2021-03-09 19:09:00 +0000

It is not wrong, but SACK, Selective Acknowledgement, is not enabled on 10.10.250.2. So when packet loss occurs the file transfer stalls in your case and TCP slow start is triggered again.

Enable SACK when possible.

Revision 1
André's avatar
176
André
answered 2021-03-09 19:06:18 +0000

It is not wrong, but SACK, Selective Acknowledgement, is not enabled on 10.10.250.2. So when packet loss occurs the file transfer stalls in your case and TCP slow start is triggered again.

Also the TCP window size is set to 64k. With the low latency as in this case, increasing the window size will allow for higher throughput.

Enable SACK and increase window size when possible.