Windows without parallel (-P 32) isn't better than linux with same config ? #1849
Replies: 3 comments
-
Hi, each stream in iperf3 is running in a separate thread. If the multi-streams threads are running on several CPUs/Cores it may explain the results. What seems strange is why the throughput of single stream on the Windows Server is only 1.12Gb. Usually such limit is because of CPU limit, but 10Gb is usually an easy task for today's CPUs. It may be that somehow the TCP/System buffers (per CPU) are limited, somehow each CPU can use limited bandwidth of the interface, etc. To better understand the Windows Server behavior you may try:
|
Beta Was this translation helpful? Give feedback.
-
Thank you for your response.
For your second question, how can I check if iperf use different CPU/Core ? With Windows Tasks manager ? I will try everything tomorrow |
Beta Was this translation helpful? Give feedback.
-
Yes,
On Linux I am using |
Beta Was this translation helpful? Give feedback.
-
Hi,
I recently tested mutliple iperf3 (3.18) on my infrastructure but I notice strange througput results between Windows Server 2022 and Debian 12. Exactly, when I try the same command between Windows Server 2022 and Debian 12 I didn't have the same results on 10Gb Network Card on VMware ESXi Server.
My goal is to determine if I have misconfigurations on my Windows/Debian template, and if I need to optimize the network config beside OS.
Config:
Server => iperf3 -s --bind
Client => iperf3 -V --bind ip_interface -c ip_destination
Client MultiStream => iperf3 -V --bind ip_interface -c ip_destination -P 32
Windows Server without multistream: 1.12Gb
Debian without multistream: 9.1Gb
Windows Server with multistream: 8.96Gb
Debian with multistream: 9.28Gb
It's the big difference with and without multistream surprise me. Do you have any idea ?
Beta Was this translation helpful? Give feedback.
All reactions