Revision history [back]

Hi, During our testing, I noticed when using Windows-10 - we observe less throughput. But when we use lInux - we see more throughput. But we intend to use Windows-10 only for this test.

When I analyzed the logs, below is my analysis so far:

Windows-10: 192.168.1.3, let's call Windows Peer : 192.168.1.176 , let's call peer.

traffic direction : Windows (iperf Client) to Peer (iperf server)

1. Windows sends TCP Seq-x to Peer
2. Peer sends a TCP ACK - x-1460 bytes .
3. Windows waits for ~100ms to ~200ms before re-transmitting the packet - which as seq-x.

Looks like TCP retransmission timeout is configured to be very large value: may be around 200ms? Is there a way I can change this to lower value? Yes, I'm running on a network - where some packet loss is expected.

-ram

Hi, During our testing, I noticed when using Windows-10 - we observe less throughput. But when we use lInux - we see more throughput. But we intend to use Windows-10 only for this test.

When I analyzed the logs, below is my analysis so far:

Windows-10: 192.168.1.3, let's call Windows Peer : 192.168.1.176 , let's call peer.

traffic direction : Windows (iperf Client) to Peer (iperf server)

1. Windows sends TCP Seq-x to Peer
2. Peer sends a TCP ACK - x-1460 bytes .
3. Windows waits for ~100ms to ~200ms before re-transmitting the packet - which as seq-x.

Looks like TCP retransmission timeout is configured to be very large value: may be around 200ms? Is there a way I can change this to lower value? Yes, I'm running on a network - where some packet loss is expected.

-ram

Hi, During our testing, I noticed when using Windows-10 - we observe less throughput. But when we use lInux - we see more throughput. But we intend to use Windows-10 only for this test.

When I analyzed the logs, below is my analysis so far:

Windows-10: 192.168.1.3, let's call Windows Peer : 192.168.1.176 , let's call peer.

traffic direction : Windows (iperf Client) to Peer (iperf server)

1. Windows sends TCP Seq-x to Peer
2. Peer sends a TCP ACK - x-1460 bytes .
3. Windows waits for ~100ms to ~200ms before re-transmitting the packet - which as seq-x.

Looks like TCP retransmission timeout is configured to be very large value: may be around 200ms? Is there a way I can change this to lower value? Yes, I'm running on a network - where some packet loss is expected.

-ram