(Before, he's used to retransmit several of them) At 82.41s, macOS starts to send missing packets 1 by 1. Windows size is not full (bytes in flight: 725kB).NAS server window size : 1MB (since the begining).My question here is on the difference of TCP behavior of the server & between Windows and macOS.Network is loosing packets for sure, looks like burst in switch -> will investigate that appart.Server window size coeff : 圆4 (max: 4MB).Client window size coeff : x128 (max: 8MB).Upload to server, trace is made directly on client.Server is a NAS PowerScale (ex-Isilon) Dell/EMC - OneFS OS v8.2.2.Windows 10 clients don't have any problem.macOS 10.15.7 uploads of a 40GB folder to a PowerScale NAS share hang for dozen of seconds or even stop with an error.On some specific sites only (private optical fibers between sites in same city : iRTT is 0.2 ms in this example, and always inferior to 1ms).Update #3 : New trace sliced dynamically after TCP header by (previous fixed slice at 78 bytes was cutting TCP header in case of several SACK blocks, leading to confusion)ġst quick troubleshoot at a customer, not all traces are ok, not all info from them, but I'll go back for them Update #2 : A sliced trace with 78 bytes is available here : Deleted Update #1 : Server is not Windows Server but directly a NAS PowerScale Dell/EMC - OneFS OS v8.2.2
0 Comments
Leave a Reply. |