IPerf - IPerf3 and IPerf2 User Documentation

14/10/2015
iPerfiPerf3andiPerf2userdocumentation
iPerf - The network bandwidth measurement tool

Active measurements in TCP, UDP and SCTP
Home
Download iPerf binaries
Public iPerf3 servers
iPerf user docs
French iPerf forum
Contact
Table of contents :
1. Change between iPerf 2.0, iPerf 3.0 and iPerf 3.1
2. iPerf 3 user documentation
3. iPerf 2 user documentation
Change between iPerf 2.0, iPerf 3.0 and iPerf 3.1

iPerf2 features currently supported by iPerf3 :
TCP and UDP tests
Set port (-p)
Setting TCP options: No delay, MSS, etc.
Setting UDP bandwidth (-b)
Setting socket buffer size (-w)
Reporting intervals (-i)
Setting the iPerf buffer (-l)
Bind to specific interfaces (-B)
IPv6 tests (-6)
Number of bytes to transmit (-n)
Length of test (-t)
Parallel streams (-P)
Setting DSCP/TOS bit vectors (-S)
Change number output format (-f)
New Features in iPerf 3.0 :
Dynamic server (client/server parameter exchange) Most server options from iPerf2 can
now be dynamically set by the client
Client/server results exchange
iPerf API (libiperf) Provides an easy way to use, customize and extend iPerf functionality
https://iperf.fr/iperfdoc.php#change
1/15
14/10/2015
-R, Reverse test mode Server sends, client receives

-O, --omit N : omit the first n seconds (to ignore TCP slowstart)
-b, --bandwidth n[KM] for TCP (only UDP for IPERF 2): Set target bandwidth to n bits/sec
(default 1 Mbit/sec for UDP, unlimited for TCP).
-V, --verbose : more detailed output than before
-J, --json : output in JSON format
-Z, --zerocopy : use a 'zero copy' sendfile() method of sending data. This uses much less CPU.
-T, --title str : prefix every output line with this string
-F, --file name : xmit/recv the specified file
-A, --affinity n/n,m : set CPU affinity (cores are numbered from 0 - Linux and FreeBSD only)
-k, --blockcount #[KMG] : number of blocks (packets) to transmit (instead of -t or -n)
-4, --version4 : only use IPv4
-6, --version6 : only use IPv6
-L, --flowlabel : set IPv6 flow label (Linux only)
-C, --linux-congestion : set congestion control algorithm (Linux and FreeBSD only) (-Z in
iPerf2)
-d, --debug : emit debugging output. Primarily (perhaps exclusively) of use to developers.
-s, --server : iPerf2 can handle multiple client requests. iPerf3 will only allow one iperf
connection at a time.
New Features in iPerf 3.1 :
-I, --pidfile file write a file with the process ID, most useful when running as a daemon.
--cport : Specify the client-side port.
--sctp use SCTP rather than TCP (Linux, FreeBSD and Solaris).
--udp-counters-64bit : Support very long-running UDP tests, which could cause a counter to
overflow
--logfile file : send output to a log file.
iPerf2 Features Not Supported by iPerf3 :
Bidirectional testing (-d / -r)
Data transmitted from stdin (-I)
TTL : time-to-live, for multicast (-T)
Exclude C(connection) D(data) M(multicast) S(settings) V(server) reports (-x)
Report as a Comma-Separated Values (-y)
Compatibility mode allows for use with older version of iPerf (-C)
iPerf 3 user documentation

GENERAL OPTIONS
Command
Description
line option
-p, --port n The server port for the server to listen on and the client to connect to. This should be the same
in both client and server. Default is 5201.
--cport n Option to specify the client-side port. (new in iPerf 3.1)
-f, --format A letter specifying the format to print bandwidth numbers in. Supported formats are
[kmKM]
'k'=Kbits/sec'K'=KBytes/sec
'm'=Mbits/sec'M'=MBytes/sec
2/15
14/10/2015
The adaptive formats choose between kilo- and mega- as appropriate.

-i, -Sets the interval time in seconds between periodic bandwidth, jitter, and loss reports. If noninterval n zero, a report is made every interval seconds of the bandwidth since the last report. If zero, no
periodic reports are printed. Default is zero.
-F, --file
client-side: read from the file and write to the network, instead of using random data;
name
server-side: read from the network and write to the file, instead of throwing the data away.
-A, -Set the CPU affinity, if possible (Linux and FreeBSD only). On both the client and server you
affinity
can set the local affinity by using the n form of this argument (where n is a CPU number). In
n/n,m-F
addition, on the client side you can override the servers affinity for just that one test, using
the n,m form of argument. Note that when using this feature, a process will only be bound to a
single CPU (as opposed to a set containing potentialy multiple CPUs).
-B, --bind Bind to host, one of this machine's addresses. For the client this sets the outbound interface.
host
For a server this sets the incoming interface. This is only useful on multihomed hosts, which
have multiple network interfaces.
-V, -give more detailed output
verbose
-J, --json output in JSON format
--logfile
send output to a log file. (new in iPerf 3.1)
file
--d, -emit debugging output. Primarily (perhaps exclusively) of use to developers.
debug
-v, -Show version information and quit.
version
-h, --help Show a help synopsis and quit.
SERVER SPECIFIC OPTIONS
Command
Description
line option
-s, --server Run iPerf in server mode. (This will only allow one iperf connection at a time)
-D, -Run the server in background as a daemon.
daemon
-I, -write a file with the process ID, most useful when running as a daemon. (new in iPerf 3.1)
pidfilefile
CLIENT SPECIFIC OPTIONS
Command
Description
line option
-c, --client Run iPerf in client mode, connecting to an iPerf server running on host.
host
--sctp
Use SCTP rather than TCP (Linux, FreeBSD and Solaris). (new in iPerf 3.1)
-u, --udp Use UDP rather than TCP. See also the -b option.
-b, -Set target bandwidth to n bits/sec (default 1 Mbit/sec for UDP, unlimited for TCP). If there are
bandwidth multiple streams (-P flag), the bandwidth limit is applied separately to each stream. You can
n[KM]
also add a / and a number to the bandwidth specifier. This is called "burst mode". It will send
the given number of packets without pausing, even if that temporarily exceeds the specified
bandwidth limit.
-t, --time n The time in seconds to transmit for. iPerf normally works by repeatedly sending an array of
len bytes for time seconds. Default is 10 seconds. See also the -l, -k and -n options.
3/15
14/10/2015
-n, --num
n[KM]
The number of buffers to transmit. Normally, iPerf sends for 10 seconds. The -n option
overrides this and sends an array of len bytes num times, no matter how long that takes. See
also the -l, -k and -t options.
-k, -The number of blocks (packets) to transmit. (instead of -t or -n) See also the -t, -l and -n
blockcount options.
n[KM]
-l, --length The length of buffers to read or write. iPerf works by writing an array of len bytes a number of
n[KM]
times. Default is 128 KB for TCP, 8 KB for UDP. See also the -n, -k and -t options.
-P, -The number of simultaneous connections to make to the server. Default is 1.
parallel n
-R, -Run in reverse mode (server sends, client receives).
reverse
-w, -Sets the socket buffer sizes to the specified value. For TCP, this sets the TCP window size.
window
(this gets sent to the server and used on that side too)
n[KM]
-M, --set- Attempt to set the TCP maximum segment size (MSS). The MSS is usually the MTU - 40 bytes
mss n
for the TCP/IP header. For ethernet, the MSS is 1460 bytes (1500 byte MTU).
-N, --no- Set the TCP no delay option, disabling Nagle's algorithm. Normally this is only disabled for
delay
interactive applications like telnet.
-4, -only use IPv4.
version4
-6, -only use IPv6.
version4
-S, --tos n The type-of-service for outgoing packets. (Many routers ignore the TOS field.) You may
specify the value in hex with a '0x' prefix, in octal with a '0' prefix, or in decimal. For example,
'0x10' hex = '020' octal = '16' decimal. The TOS numbers specified in RFC 1349 are:
IPTOS_LOWDELAYminimizedelay0x10
IPTOS_THROUGHPUTmaximizethroughput0x08
IPTOS_RELIABILITYmaximizereliability0x04
IPTOS_LOWCOSTminimizecost0x02
-L, -flowlabel n
-Z, -zerocopy
-O, --omit
n
-T, --title
str
-C, --linuxcongestion
algo
Set the IPv6 flow label (currently only supported on Linux).

Use a "zero copy" method of sending data, such as sendfile(2), instead of the usual write(2).
This uses much less CPU.
Omit the first n seconds of the test, to skip past the TCP TCP slowstart period.
Prefix every output line with this string.
Set the congestion control algorithm (Linux only for iPerf 3.0, Linux and FreeBSD for iPerf
3.1).
See also https://github.com/esnet/iperf
iPerf 2 user documentation

4/15
14/10/2015
Tuning a TCP connection

Tuning a UDP connection
Running multicast servers and
clients
IPv6 Mode
Representative Streams
Running iPerf as a daemon
Running iPerf as a Windows
Service
Adaptive Window Sizes
Compiling
GENERAL OPTIONS
Command Environment variable
Description
line option
option
-f, --format
$IPERF_FORMAT
A letter specifying the format to print bandwidth numbers in.
[bkmaBKMA]
Supported formats are
'b'=bits/sec'B'=Bytes/sec
'k'=Kbits/sec'K'=KBytes/sec
'm'=Mbits/sec'M'=MBytes/sec
'g'=Gbits/sec'G'=GBytes/sec
'a'=adaptivebits/sec'A'=adaptiveBytes/sec
-i, --interval # $IPERF_INTERVAL
-l, --len #[KM] $IPERF_LEN
-m, -print_mss
$IPERF_PRINT_MSS
The adaptive formats choose between kilo- and mega- as

appropriate. Fields other than bandwidth always print bytes, but
otherwise follow the requested format. Default is 'a'.
NOTE: here Kilo = 1024, Mega = 1024^2 and Giga = 1024^3 when
dealing with bytes. Commonly in networking, Kilo = 1000, Mega =
1000^2, and Giga = 1000^3 so we use this when dealing with bits. If
this really bothers you, use -f b and do the math.
Sets the interval time in seconds between periodic bandwidth, jitter,
and loss reports. If non-zero, a report is made every interval seconds
of the bandwidth since the last report. If zero, no periodic reports
are printed. Default is zero.
The length of buffers to read or write. iPerf works by writing an
array of len bytes a number of times. Default is 8 KB for TCP, 1470
bytes for UDP. Note for UDP, this is the datagram size and needs to
be lowered when using IPv6 addressing to 1450 or less to avoid
fragmentation. See also the -n and -t options.
Print the reported TCP MSS size (via the TCP_MAXSEG option) and
the observed read sizes which often correlate with the MSS. The
5/15
14/10/2015
MSS is usually the MTU - 40 bytes for the TCP/IP header. Often a
slightly smaller MSS is reported because of extra header space from
IP options. The interface type corresponding to the MTU is also
printed (ethernet, FDDI, etc.). This option is not implemented on
many OSes, but the read sizes may still indicate the MSS.
-p, --port #
$IPERF_PORT
The server port for the server to listen on and the client to connect
to. This should be the same in both client and server. Default is 5001,
the same as ttcp.
-u, --udp
$IPERF_UDP
Use UDP rather than TCP. See also the -b option.
-w, --window $TCP_WINDOW_SIZE Sets the socket buffer sizes to the specified value. For TCP, this sets
#[KM]
the TCP window size. For UDP it is just the buffer which datagrams
are received in, and so limits the largest receivable datagram size.
-B, --bind
$IPERF_BIND
Bind to host, one of this machine's addresses. For the client this sets
host
the outbound interface. For a server this sets the incoming interface.
This is only useful on multihomed hosts, which have multiple
network interfaces.
For iPerf in UDP server mode, this is also used to bind and join to a
multicast group. Use addresses in the range 224.0.0.0 to
239.255.255.255 for multicast. See also the -T option.
-C, -$IPERF_COMPAT
compatibility
-M, --mss #
[KM}
$IPERF_MSS
-N, --nodelay $IPERF_NODELAY

-V (from v1.6 .
or higher)
Compatibility mode allows for use with older version of iPerf. This
mode is not required for interoperability but it is highly
recommended. In some cases when using representative streaming
you could cause a 1.7 server to crash or cause undesired connection
attempts.
Attempt to set the TCP maximum segment size (MSS) via the
TCP_MAXSEG option. The MSS is usually the MTU - 40 bytes for the
TCP/IP header. For ethernet, the MSS is 1460 bytes (1500 byte
MTU). This option is not implemented on many OSes.
Set the TCP no delay option, disabling Nagle's algorithm. Normally
this is only disabled for interactive applications like telnet.
Bind to an IPv6 address
Server side:
$ iperf -s -V
Client side:
$ iperf -c <Server IPv6 Address> -V
-h, --help
-v, --version
Note: On version 1.6.3 and later a specific IPv6 Address does not
need to be bound with the -B option, previous 1.6 versions do. Also
on most OSes using this option will also respond to IPv4 clients using
IPv4 mapped addresses.
Print out a summary of commands and quit.
Print version information and quit. Prints 'pthreads' if compiled with
POSIX threads, 'win32 threads' if compiled with Microsoft Win32
threads, or 'single threaded' if compiled without threads.
SERVER SPECIFIC OPTIONS
6/15
14/10/2015
Command Environment variable

Description
line option
option
-s, --server
$IPERF_SERVER
Run iPerf in server mode. (iPerf2 can handle multiple client requests)
-D (from v1.2 .
Run the server as a daemon (Unix platforms)
or higher)
On Win32 platforms where services are available, iPerf will start
running as a service.
-R (only for .
Remove the iPerf service (if it's running).
Windows,
from v1.2 or
higher)
-o (only for
.
Redirect output to given file.
Windows,
from v1.2 or
higher)
-c, --client
$IPERF_CLIENT
If iPerf is in server mode, then specifying a host with -c will limit the
host
connections that iPerf will accept to the host specified. Does not
work well for UDP.
-P, --parallel # $IPERF_PARALLEL
The number of connections to handle by the server before closing.
Default is 0 (which means to accept connections forever).
CLIENT SPECIFIC OPTIONS
Command
line option
-b, -bandwidth #
[KM]
-c, --client
host
-d, --dualtest
Environment variable
Description
option
$IPERF_BANDWIDTH The UDP bandwidth to send at, in bits/sec. This implies the -u option.
Default is 1 Mbit/sec.
$IPERF_CLIENT
Run iPerf in client mode, connecting to an iPerf server running on

host.
$IPERF_DUALTEST
Run iPerf in dual testing mode. This will cause the server to connect
back to the client on the port specified in the -L option (or defaults to
the port the client connected to the server on). This is done
immediately therefore running the tests simultaneously. If you want
an alternating test try -r.
-n, --num #
$IPERF_NUM
The number of buffers to transmit. Normally, iPerf sends for 10
[KM]
seconds. The -n option overrides this and sends an array of len bytes
num times, no matter how long that takes. See also the -l and -t
options.
-r, --tradeoff $IPERF_TRADEOFF Run iPerf in tradeoff testing mode. This will cause the server to
connect back to the client on the port specified in the -L option (or
defaults to the port the client connected to the server on). This is
done following the client connection termination, therefore running
the tests alternating. If you want an simultaneous test try -d.
-t, --time #
$IPERF_TIME
The time in seconds to transmit for. iPerf normally works by
repeatedly sending an array of len bytes for time seconds. Default is
10 seconds. See also the -l and -n options.
-L, -$IPERF_LISTENPORT This specifies the port that the server will connect back to the client
listenport #
on. It defaults to the port used to connect to the server from the
client.
-P, --parallel # $IPERF_PARALLEL
The number of simultaneous connections to make to the server.
7/15
14/10/2015
-S, --tos #
$IPERF_TOS
Default is 1. Requires thread support on both the client and server.

The type-of-service for outgoing packets. (Many routers ignore the
TOS field.) You may specify the value in hex with a '0x' prefix, in octal
with a '0' prefix, or in decimal. For example, '0x10' hex = '020' octal =
'16' decimal. The TOS numbers specified in RFC 1349 are:
IPTOS_LOWDELAYminimizedelay0x10
IPTOS_THROUGHPUTmaximizethroughput0x08
IPTOS_RELIABILITYmaximizereliability0x04
IPTOS_LOWCOSTminimizecost0x02
-T, --ttl #
$IPERF_TTL
-F (from v1.2 .
or higher)
-I (from v1.2 .
or higher)
The time-to-live for outgoing multicast packets. This is essentially

the number of router hops to go through, and is also used for
scoping. Default is 1, link-local.
Use a representative stream to measure bandwidth, e.g. :-
$ iperf -c <server address> -F <file-name>
Same as -F, input from stdin.
Tuning a TCP connection

The primary goal of iPerf is to help in tuning TCP connections over a particular path. The most
fundamental tuning issue for TCP is the TCP window size, which controls how much data can be in the
network at any one point. If it is too small, the sender will be idle at times and get poor performance. The
theoretical value to use for the TCP window size is the bandwidth delay product,
bottleneck bandwidth * round trip time
In the below modi4/cyclops example, the bottleneck link is a 45 Mbit/sec DS3 link and the round trip time
measured with ping is 42 ms. The bandwidth delay product is
45 Mbit/sec * 42 ms
= (45e6) * (42e-3)
= 1890000 bits
= 230 KByte
That is a starting point for figuring the best window size; setting it higher or lower may produce better
results. In our example, buffer sizes over 130K did not improve the performance, despite the bandwidth
delay product of 230K.
Note that many OSes and hosts have upper limits on the TCP window size. These may be as low as 64 KB,
or as high as several MB. iPerf tries to detect when these occur and give a warning that the actual and
requested window sizes are not equal (as below, though that is due to rounding in IRIX). For more
information on TCP window sizes, see the LaFibre.info. Here is an example session, between node1 in
Illinois and node2 in North Carolina. These are connected via the vBNS backbone and a 45 Mbit/sec DS3
link. Notice we improve bandwidth performance by a factor of 3 using proper TCP window sizes. Use the
adaptive window sizes feature on platforms which allow setting window sizes in the granularity of bytes.
node2>iperfs
8/15
14/10/2015
ServerlisteningonTCPport5001
TCPwindowsize:60.0KByte(default)
[4]local<IPAddrnode2>port5001connectedwith<IPAddrnode1>port2357
[ID]IntervalTransferBandwidth
[4]0.010.1sec6.5MBytes5.2Mbits/sec
node1>iperfcnode2
Clientconnectingtonode1,TCPport5001
node2>iperfsw130k
TCPwindowsize:130KByte
node1>iperfcnode2w130k
TCPwindowsize:129KByte(WARNING:requested130KByte)
Another test to do is run parallel TCP streams. If the total aggregate bandwidth is more than what an
individual stream gets, something is wrong. Either the TCP window size is too small, or the OS's TCP
implementation has bugs, or the network itself has deficiencies. See above for TCP window sizes;
otherwise diagnosing which is somewhat difficult. If iPerf is compiled with pthreads, a single client and
server can test this, otherwise setup multiple clients and servers on different ports. Here's an example
where a single stream gets 16.5 Mbit/sec, but two parallel streams together get 16.7 + 9.4 = 26.1 Mbit/sec,
even when using large TCP window sizes:
node2>iperfsw300k
TCPwindowsize:300KByte
9/15
14/10/2015
node1>./iperfcnode2w300k
node1>iperfcnode2w300kP2
A secondary tuning issue for TCP is the maximum transmission unit (MTU). To be most effective, both
hosts should support Path MTU Discovery. Hosts without Path MTU Discovery often use 536 as the MSS,
which wastes bandwidth and processing time. Use the -m option to display what MSS is being used, and
see if this matches what you expect. Often it is around 1460 bytes for ethernet.
node3>iperfsm
[4]MSSsize1448bytes(MTU1500bytes,ethernet)
[4]Readlengthsoccurringinmorethan5%ofreads:
[4]952bytesread219times(16.2%)
Here is a host that doesn't support Path MTU Discovery. It will only send and receive small 576 byte
packets.
node4>iperfsm
10/15
14/10/2015
[4]0.02.3sec632KBytes2.1Mbits/sec
WARNING:PathMTUDiscoverymaynotbeenabled.
[4]MSSsize536bytes(MTU576bytes,minimum)
[4]Readlengthsoccurringinmorethan5%ofreads:
iPerf supports other tuning options, which were added for exceptional network situations like HIPPI-toHIPPI over ATM.
Tuning a UDP connection

iPerf creates a constant bit rate UDP stream. This is a very artificial stream, similar to voice
communication but not much else.
You will want to adjust the datagram size (-l) to the size your application uses.
The server detects UDP datagram loss by ID numbers in the datagrams. Usually a UDP datagram becomes
several IP packets. Losing a single IP packet will lose the entire datagram. To measure packet loss instead
of datagram loss, make the datagrams small enough to fit into a single packet, using the -l option. The
default size of 1470 bytes works for ethernet. Out-of-order packets are also detected. (Out-of-order
packets cause some ambiguity in the lost packet count; iPerf assumes they are not duplicate packets, so
they are excluded from the lost packet count.) Since TCP does not report loss to the user, I find UDP tests
helpful to see packet loss along a path.
Jitter calculations are continuously computed by the server, as specified by RTP in RFC 1889. The client
records a 64 bit second/microsecond timestamp in the packet. The server computes the relative transit
time as (server's receive time - client's send time). The client's and server's clocks do not need to be
synchronized; any difference is subtracted out in the jitter calculation. Jitter is the smoothed mean of
differences between consecutive transit times.
node2>iperfsui1
ServerlisteningonUDPport5001
Receiving1470bytedatagrams
UDPbuffersize:60.0KByte(default)
[ID]IntervalTransferBandwidthJitterLost/TotalDatagrams
[4]0.01.0sec1.3MBytes10.0Mbits/sec0.209ms1/894(0.11%)
[4]1.02.0sec1.3MBytes10.0Mbits/sec0.221ms0/892(0%)
11/15
14/10/2015
node1>iperfcnode2ub10m
Clientconnectingtonode2,UDPport5001
Sending1470bytedatagrams
[3]Sent8922datagrams
Notice the higher jitter due to datagram reassembly when using larger 32 KB datagrams, each split into 23
packets of 1500 bytes. The higher datagram loss seen here may be due to the burstiness of the traffic,
which is 23 back-to-back packets and then a long pause, rather than evenly spaced individual packets.
node2>iperfsul32kw128ki1
UDPbuffersize:128KByte
node1>iperfcnode2b10ml32kw128k
Clientconnectingtonode2,UDPport5001
UDPbuffersize:128KByte
[3]Sent401datagrams
Multicast
12/15
14/10/2015
To test multicast, run several servers with the bind option (-B, --bind) set to the multicast group address.
Run the client, connecting to the multicast group address and setting the TTL (-T, --ttl) as needed. Unlike
normal TCP and UDP tests, multicast servers may be started after the client. In that case, datagrams sent
before the server started show up as losses in the first periodic report (61 datagrams on arno below).
node5>iperfc224.0.67.67uttl5t5
Clientconnectingto224.0.67.67,UDPport5001
SettingmulticastTTLto5
[3]local<IPAddrnode5>port1025connectedwith224.0.67.67port5001
[3]0.05.0sec642KBytes1.0Mbits/sec
[3]Sent447datagrams
node5>iperfsuB224.0.67.67i1
Bindingtolocaladdress224.0.67.67
Joiningmulticastgroup224.0.67.67
[3]local224.0.67.67port5001connectedwith<IPAddrnode5>port1025
[3]0.01.0sec131KBytes1.0Mbits/sec0.007ms0/91(0%)
node6>iperfsuB224.0.67.67i1
Bindingtolocaladdress224.0.67.67
Joiningmulticastgroup224.0.67.67
[3]local224.0.67.67port5001connectedwith<IPAddrnode5>port1025
Start multiple clients or servers as explained above, sending data to the same multicast server. (If you have
multiple servers listening on the multicast address, each of the servers will be getting the data)
13/15
14/10/2015
IPv6 Mode
Get the IPv6 address of the node using the 'ifconfig' command.
Use the -V option to indicate that you are using an IPv6 address Please note that we need to
explicitly bind the server address also.
Server side:
$ iperf -s -V
Client side:
$ iperf -c <Server IPv6 Address> -V>
Note: iPerf version 1.6.2 and eariler require a IPv6 address to be explicitly bound with the -B option
for the server.
Using Representative Streams to measure bandwidth

Use the -F or -I option. If you want to test how your network performs with compressed /
uncompressed streams, just create representative streams and use the -F option to test it. This is
usually due to the link layer compressing data.
The -F option is for file input.
The -I option is for input from stdin.
E.g.
Client: $ iperf -c <server address> -F <file-name>
Client: $ iperf -c <server address> -I
Running the server as a daemon

Use the -D command line option to run the server as a daemon. Redirect the output to a file.
E.g. iperf -s -D > iperflog. This will have the iPerf Server running as a daemon and the server
messages will be logged in the file iperfLog.
Using iPerf as a Service under Win32

There are three options for Win32:
-o outputfilename
output the messages into the specified file
14/15
14/10/2015
-s -D
-s -R
install iPerf as a service and run it

uninstall the iPerf service
Examples:
iperf -s -D -o iperflog.txt
will install the iPerf service and run it. Messages will be reported into
"%windir%\system32\iperflog.txt"
iperf -s -R
will uninstall the iPerf service if it is installed.
Note: If you stop want to restart the iPerf service after having killed it with the Microsoft
Management Console or the Windows Task Manager, make sure to use the proper OPTION in the
service properties dialog.
Adaptive window sizes (under development)

Use the -W option on the client to run the client with the adaptive window size. Ensure that the
server window size is fairly big for this option.
E.g.. If the server TCP window size is 8KB, it does not help having a client TCP window size of 256KB.
256KB Server TCP Window Size should suffice for most high bandwidth networks.
Client changes the TCP window size using a binary exponential algorithm. This means that you may
notice that TCP window size suggested may vary according to the traffic in the network, iPerf will
suggest the best window size for the current network scenario.
Compiling
Once you have the distribution, on UNIX, unpack it using gzip and tar. That will create a new directory
'iperf-<version#>' with the source files and documentation.
iPerf compiles cleanly on many systems including Linux, SGI IRIX, HP-UX, Solaris, AIX, and Cray UNICOS.
Use 'make' to configure for your OS and compile the source code.
gunzipciperf<version>.tar.gz|tarxvf
cdiperf<version>
./configure
make
To install iPerf, use 'make install', which will ask you where to install it. To recompile, the easiest way is to
start over. Do 'make distclean' then './configure; make'. See the Makefile for more options.
15/15

IPerf - IPerf3 and IPerf2 User Documentation

Uploaded by

Copyright:

Available Formats

IPerf - IPerf3 and IPerf2 User Documentation

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IPerf - IPerf3 and IPerf2 User Documentation

Uploaded by

Copyright:

Available Formats

14/10/2015

iPerf - The network bandwidth measurement tool

Download iPerf binaries

Public iPerf3 servers

iPerf user docs

French iPerf forum

Change between iPerf 2.0, iPerf 3.0 and iPerf 3.1

-R, Reverse test mode Server sends, client receives

iPerf 3 user documentation

The adaptive formats choose between kilo- and mega- as appropriate.

Set the IPv6 flow label (currently only supported on Linux).

See also https://github.com/esnet/iperf

iPerf 2 user documentation

Tuning a TCP connection

-i, --interval # $IPERF_INTERVAL

-l, --len #[KM] $IPERF_LEN

The adaptive formats choose between kilo- and mega- as

-N, --nodelay $IPERF_NODELAY

Command Environment variable

Run iPerf in client mode, connecting to an iPerf server running on

Default is 1. Requires thread support on both the client and server.

The time-to-live for outgoing multicast packets. This is essentially

Tuning a TCP connection

Tuning a UDP connection

Using Representative Streams to measure bandwidth

Running the server as a daemon

Using iPerf as a Service under Win32

install iPerf as a service and run it

Adaptive window sizes (under development)

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.