diff options
author | Bruce A. Mah <bmah@es.net> | 2014-04-17 11:11:19 -0700 |
---|---|---|
committer | Bruce A. Mah <bmah@es.net> | 2014-04-17 11:11:19 -0700 |
commit | bead6a8b52ccddabc5ebf5a8b7b1336899e840d6 (patch) | |
tree | f209c7c2f74cf0241fae9bc133e4da2c3ffbdbc4 /README.md | |
parent | 081ba8e4e9ddeaa7991728ce12f0a9ee88f00a32 (diff) | |
download | iperf3-bead6a8b52ccddabc5ebf5a8b7b1336899e840d6.tar.gz |
Revision 081ba8e seems to have addressed Issue 125, so remove this from
the set of known issues.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 9 |
1 files changed, 0 insertions, 9 deletions
@@ -126,15 +126,6 @@ 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/). -* Interval reports on high-loss networks: The way iperf3 is currently -implemented, the sender write command will block until the entire -block has been written. This means that it might take several seconds -to send a full block if the network has high loss, and the interval -reports will have widely varying interval times. We are trying to -determine the best solution to this, but in the meantime, try using a -smaller block size if you get strange interval reports. For example, -try "-l 4K". - * The -Z flag sometimes hangs on OSX. * On OpenBSD, the server seems to require a "-4" argument, implying |