version 1.1.1.2, 2021/03/17 00:36:45
|
version 1.1.1.3, 2023/09/27 11:14:54
|
Line 18 such as nuttcp and netperf, but were missing from the
|
Line 18 such as nuttcp and netperf, but were missing from the
|
These include, for example, a zero-copy mode and optional JSON output. |
These include, for example, a zero-copy mode and optional JSON output. |
Note that iperf3 is *not* backwards compatible with the original iperf. |
Note that iperf3 is *not* backwards compatible with the original iperf. |
|
|
Primary development for iperf3 takes place on CentOS Linux, FreeBSD, | Primary development for iperf3 takes place on Ubuntu Linux, FreeBSD, |
and macOS. At this time, these are the only officially supported |
and macOS. At this time, these are the only officially supported |
platforms, however there have been some reports of success with |
platforms, however there have been some reports of success with |
OpenBSD, NetBSD, Android, Solaris, and other Linux distributions. |
OpenBSD, NetBSD, Android, Solaris, and other Linux distributions. |
Line 30 For more information see: https://software.es.net/iper
|
Line 30 For more information see: https://software.es.net/iper
|
|
|
Source code and issue tracker: https://github.com/esnet/iperf |
Source code and issue tracker: https://github.com/esnet/iperf |
|
|
|
Discussion forums: https://github.com/esnet/iperf/discussions |
|
|
Obtaining iperf3 |
Obtaining iperf3 |
---------------- |
---------------- |
|
|
Line 60 Invoking iperf3
|
Line 62 Invoking iperf3
|
iperf3 includes a manual page listing all of the command-line options. |
iperf3 includes a manual page listing all of the command-line options. |
The manual page is the most up-to-date reference to the various flags and parameters. |
The manual page is the most up-to-date reference to the various flags and parameters. |
|
|
For sample command line usage, see: | For sample command line usage, see: |
|
|
https://fasterdata.es.net/performance-testing/network-troubleshooting-tools/iperf/ |
https://fasterdata.es.net/performance-testing/network-troubleshooting-tools/iperf/ |
|
|
Line 76 These flags include:
|
Line 78 These flags include:
|
-Z, --zerocopy use a 'zero copy' sendfile() method of sending data |
-Z, --zerocopy use a 'zero copy' sendfile() method of sending data |
-A, --affinity n/n,m set CPU affinity |
-A, --affinity n/n,m set CPU affinity |
|
|
Bug Reports | Bug and Security Reports |
----------- | ------------------------ |
|
|
Before submitting a bug report, please make sure you're running the |
Before submitting a bug report, please make sure you're running the |
latest version of the code, and confirm that your issue has not |
latest version of the code, and confirm that your issue has not |
Line 97 sensitive information.
|
Line 99 sensitive information.
|
If you have a question about usage or about the code, please do *not* |
If you have a question about usage or about the code, please do *not* |
submit an issue. Please use one of the mailing lists for that. |
submit an issue. Please use one of the mailing lists for that. |
|
|
|
If you suspect there is a potential security issue, please contact the |
|
developers at: |
|
|
|
iperf@es.net |
|
|
Relation to iperf 2.x |
Relation to iperf 2.x |
--------------------- |
--------------------- |
|
|
Note that iperf2 is no longer being developed by its original | Although iperf2 and iperf3 both measure network performance, |
maintainers. However, beginning in 2014, another developer began | they are not compatible with each other. |
fixing bugs and enhancing functionality, and generating releases of | The projects (as of mid-2021) are in active, but separate, development. |
iperf2. Both projects (as of late 2017) are currently being developed | The continuing iperf2 development |
actively, but independently. The continuing iperf2 development | |
project can be found at https://sourceforge.net/projects/iperf2/. |
project can be found at https://sourceforge.net/projects/iperf2/. |
|
|
iperf3 contains a number of options and functions not present in |
iperf3 contains a number of options and functions not present in |
Line 120 Some iperf2 options are not available in iperf3:
|
Line 126 Some iperf2 options are not available in iperf3:
|
|
|
-r, --tradeoff Do a bidirectional test individually |
-r, --tradeoff Do a bidirectional test individually |
-T, --ttl time-to-live, for multicast (default 1) |
-T, --ttl time-to-live, for multicast (default 1) |
-x, --reportexclude [CDMSV] exclude C(connection) D(data) M(multicast) | -x, --reportexclude [CDMSV] exclude C(connection) D(data) M(multicast) |
S(settings) V(server) reports |
S(settings) V(server) reports |
-y, --reportstyle C report as a Comma-Separated Values |
-y, --reportstyle C report as a Comma-Separated Values |
|
|
Line 149 responsibility for the content of these pages.
|
Line 155 responsibility for the content of these pages.
|
Copyright |
Copyright |
--------- |
--------- |
|
|
iperf, Copyright (c) 2014-2020, The Regents of the University of | iperf, Copyright (c) 2014-2023, The Regents of the University of |
California, through Lawrence Berkeley National Laboratory (subject |
California, through Lawrence Berkeley National Laboratory (subject |
to receipt of any required approvals from the U.S. Dept. of |
to receipt of any required approvals from the U.S. Dept. of |
Energy). All rights reserved. |
Energy). All rights reserved. |