d/iperf3-tls
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Revise documentation of UDP performance issues based on recent

Browse Source 
experiments.

Fixes Issue #55 (at least to the extent that it's not really an
iperf3 issue).
This commit is contained in:
Bruce A. Mah 2014-05-01 13:18:53 -07:00
parent 6b16244baa
commit e4e22a58a7
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -121,12 +121,17 @@ variables.
Known Issues
------------
* UDP performance: iperf2/iperf3 both only are only about 50% as fast
as nuttcp in UDP mode. We are looking into this, but in the meantime,
if you want to get UDP above 5Gbps, we recommend using nuttcp instead
(http://www.nuttcp.net/).
* UDP performance: Some problems have been noticed with iperf3 on the
ESnet 100G testbed at high UDP rates (above 10Gbps). The symptom is
that on any particular run of iperf3 the receiver reports a loss rate
of about 20%, regardless of the -b option used on the client side.
This problem appears not to be iperf3-specific, and may be due to the
placement of the iperf3 process on a CPU and its relation to the
inbound NIC. In some cases this problem can be mitigated by an
appropriate use of the CPU affinity (-A) option. (Issue #55)
* The -Z flag sometimes hangs on OSX.
* The -Z flag sometimes causes the iperf3 client to hang on OSX.
(Issue #129)
* On OpenBSD, the server seems to require a "-4" argument, implying
that it can only be used with IPv4.