Add a couple of important FAQs, update packages list and supported platforms.
Этот коммит содержится в:
родитель
12e0c9be82
Коммит
e134d88ffe
19
docs/faq.rst
19
docs/faq.rst
@ -75,6 +75,25 @@ I'm trying to use iperf3 to test a 40G/100G link...What do I need to know?
|
||||
- https://fasterdata.es.net/host-tuning/100g-tuning/
|
||||
- https://fasterdata.es.net/performance-testing/network-troubleshooting-tools/iperf/multi-stream-iperf3/
|
||||
|
||||
My receiver didn't get all the bytes that got sent but there was no loss. Huh?
|
||||
iperf3 uses a control connection between the client and server to
|
||||
manage the start and end of each test. Sometimes the commands on
|
||||
the control connection can be received and acted upon before all of
|
||||
the test data has been processed. Thus the test ends with data
|
||||
still in flight. This effect can be significant for short (a few
|
||||
seconds) tests, but is probably negligible for longer tests.
|
||||
|
||||
A file sent using the ``-F`` option got corrupted...what happened?
|
||||
The ``-F`` option to iperf3 is not a file transfer utility. It's a
|
||||
way of testing the end-to-end performance of a file transfer,
|
||||
including filesystem and disk overheads. So while the test will
|
||||
mimic an actual file transfer, the data stored to disk may not be
|
||||
the same as what was sent. In particular, the file size will be
|
||||
rounded up to the next larger multiple of the transfer block size,
|
||||
and for UDP tests, iperf's metadata (containing timestamps and
|
||||
sequence numbers) will overwrite the start of every UDP packet
|
||||
payload.
|
||||
|
||||
I have a question regarding iperf3...what's the best way to get help?
|
||||
Searching on the Internet is a good first step.
|
||||
http://stackoverflow.com/ has a number of iperf3-related questions
|
||||
|
@ -6,7 +6,10 @@ Obtaining iperf3
|
||||
Binary Distributions
|
||||
--------------------
|
||||
|
||||
Binary packages are available for several supported operating systems:
|
||||
Note that ESnet does not distribute binary packages of iperf3. All of
|
||||
the packages listed in this section are provided by third parties, who
|
||||
are solely responsible for their contents. This is an incomplete list
|
||||
of binary packages:
|
||||
|
||||
* FreeBSD: `benchmarks/iperf3
|
||||
<http://freshports.org/benchmarks/iperf3>`_ in the FreeBSD Ports Collection
|
||||
@ -14,7 +17,16 @@ Binary packages are available for several supported operating systems:
|
||||
<https://apps.fedoraproject.org/packages/iperf3/>`_ and
|
||||
`iperf3-devel
|
||||
<https://apps.fedoraproject.org/packages/iperf3-devel>`_ in Fedora
|
||||
19 and 20 and in Fedora EPEL 5, 6, and 7.
|
||||
19 and 20 and in Fedora EPEL 5, 6, and 7. iperf3 is included as a
|
||||
part of RedHat Enterprise Linux 7.3 and later (as well as CentOS 7.3
|
||||
and later).
|
||||
* Ubuntu: `iperf3 <https://launchpad.net/ubuntu/+source/iperf3>`_,
|
||||
is available in Trusty (backports), and as a part of the main
|
||||
release in Vivid and newer.
|
||||
* macOS: via HomeBrew.
|
||||
* Windows: `iperf3 binaries for Windows
|
||||
<https://iperf.fr/iperf-download.php#windows>`_ are available from
|
||||
iperf.fr (and other sources).
|
||||
|
||||
Source Distributions
|
||||
--------------------
|
||||
@ -56,7 +68,7 @@ GitHub using:
|
||||
|
||||
``git clone https://github.com/esnet/iperf.git``
|
||||
|
||||
Primary development for iperf3 takes place on CentOS 6 Linux, FreeBSD 10,
|
||||
and MacOS X 10.8. At this time, these are the only officially supported
|
||||
Primary development for iperf3 takes place on CentOS 7 Linux, FreeBSD 11,
|
||||
and macOS 10.12. At this time, these are the only officially supported
|
||||
platforms, however there have been some reports of success with
|
||||
OpenBSD, Android, and other Linux distributions.
|
||||
NetBSD, OpenBSD, Windows, Solaris, Android, and iOS.
|
||||
|
Загрузка…
x
Ссылка в новой задаче
Block a user