ports/iperf3
ports/iperf3
1
1
Форкнуть 0
Код Релизы Активность

Minor tweaks to README.

Просмотр исходного кода
Этот коммит содержится в:
Bruce A. Mah 2014-02-28 10:08:35 -08:00
родитель c897d7368a
Коммит f274eea090
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4984910A8CAAEE8A
1 изменённых файлов: 2 добавлений и 2 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

4
README
Просмотреть файл

@ -92,7 +92,7 @@ These flags include:
* UDP performance: iperf2/iperf3 both only are only about 50% as fast * 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, 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 if you want to get UDP above 5Gbps, we recommend using nuttcp instead
(http://www.nuttcp.net/) (http://www.nuttcp.net/).
* Interval reports on high-loss networks: The way iperf3 is currently * Interval reports on high-loss networks: The way iperf3 is currently
implemented, the sender write command will block until the entire implemented, the sender write command will block until the entire
@ -103,7 +103,7 @@ determine the best solution to this, but in the meantime, try using a
smaller block size if you get strange interval reports. For example, smaller block size if you get strange interval reports. For example,
try "-l 4K". try "-l 4K".
* -Z flag on OSX sometimes hangs * The -Z flag sometimes hangs on OSX.
* On OpenBSD, the server seems to require a "-4" argument, implying * On OpenBSD, the server seems to require a "-4" argument, implying
that it can only be used with IPv4. that it can only be used with IPv4.