From bead6a8b52ccddabc5ebf5a8b7b1336899e840d6 Mon Sep 17 00:00:00 2001 From: "Bruce A. Mah" Date: Thu, 17 Apr 2014 11:11:19 -0700 Subject: [PATCH] Revision 081ba8e seems to have addressed Issue 125, so remove this from the set of known issues. --- README.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/README.md b/README.md index 16082e5..fc17bef 100644 --- a/README.md +++ b/README.md @@ -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