Replies: 1 comment
-
It's a little tricky to speculate on what's happening here, we could use some more information like what operating system / distribution you're using and what version of iperf3 you have. One possibility is that you're overrunning the socket buffers on either the sender (client) or receive (server) side. Perhaps try experimenting with the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
hi,
i'm having some weird behavior while using iperf with udp:
first, i'm changing both of my device to work with 10Mb/s speed.
i try to use iperf with datagram of 8Kb and that's my results:
iperf3 -c 1.0.0.1 -p 5201 -u -b 10mb -l 8kb
later i try send datagram of 1472b (mtu size) and that's my results:
iperf3 -c 1.0.0.1 -p 5201 -u -b 10mb -l 1472
later, i'm changing the speed of both device to 100Mb/s, and i get inverted results.
for 8Kb datagram:
iperf3 -c 1.0.0.1 -p 5201 -u -b 100mb -l 8kb
but for 1472b datagram:
iperf3 -c 1.0.0.1 -p 5201 -u -b 100mb -l 1472
I've tried changing the datagram to 1Kb and saw a new issue:
iperf3 -c 1.0.0.1 -p 5201 -u -b 100mb -l 1kb
the results are better than the 1472 datagrams, but i got an error that my rx ring got full in the process (meaning that my controller wrote to the dram faster than my cpu was able to read).
i have 2 questions:
thanks.
Beta Was this translation helpful? Give feedback.
All reactions