-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iperf3 performance numbers #375
Comments
Have you tried increasing the sending and receiving socket buffer sizes with the |
We've seen up to 70Gbps with single stream iperf3, so I dont think its a problem with the tool. Can you send the exact commands you are using for iperf2 vs iperf3? Also, these pages might be helpful: |
Hi I'm Daniel from the Windows TCPIP team, |
The original bug report didn't say what platform was being used, in particular they didn't say they were on Windows. We haven't gotten any responses to our requests for other information, so closing for now. It can be reopened if more information surfaces. I do wonder if we should include some of the information provided by @dahavey regarding Windows network performance (in this issue and in #463) into the FAQ, although I haven't thought yet about what's the best way to do that. |
Hi,
I have received more and more inquiries from our customer regarding low performance numbers acquired from iperf3 compared to iperf. Below is a report:
If I send iPerf3 traffic:
From I4S to I4S = Performance is 3-400 Mbit
From I4S to B4S = Performance is 3-400 Mbit
From B4S to B4S = Performance is 3-400 Mbit
From I4S to I2S = Performance is 6-7Gbit
From B4S to I2S = Performance is 6-7Gbit
(Same numbers if I reverse the data flow)
In above, all these “I4S”, “B4S”, “I2S” represent various 10G SFP+ cards.
Could you please give me some advice? I wonder what flags/parameters people usually use to test 10G/100G with iperf3?
If using iperf, all these 10G connections can get 9+ Gbps with correct parameters set. But no matter what parameters I added, iperf3 numbers don't look good at all.
Thank you.
The text was updated successfully, but these errors were encountered: