You can also add a ’/’ and a number to the bandwidth specifier. The bandwidth limit is applied separately to each stream. Set target bandwidth to n bits/sec (default 1 Mbit/sec for UDP, unlimited for TCP). Use SCTP rather than TCP (Linux, FreeBSD and Solaris). Run iPerf in client mode, connecting to an iPerf server running on host. Write a file with the process ID, most useful when running as a daemon. Run the server in background as a daemon. (This will only allow one iperf connection at a time) Primarily (perhaps exclusively) of use to developers. This is only useful on multihomed hosts, which have multiple To a single CPU (as opposed to a set containing potentialy multiple CPUs).īind to host, one of this machine's addresses. Note that when using this feature, a process will only be bound In addition, on the client side you can override the server’sĪffinity for just that one test, using the n,m form of argument. Using the n form of this argument (where n is a CPU number). On both the client and server you can set the local affinity by Set the CPU affinity, if possible (Linux and FreeBSD only). Server-side: read from the network and write to the file, instead of throwing the data away. If zero, no periodicĬlient-side: read from the file and write to the network, instead of using random data Seconds of the bandwidth since the last report. If non-zero, a report is made every interval Sets the interval time in seconds between periodic bandwidth, jitter,Īnd loss reports. The adaptive formats choose between kilo- and mega- as appropriate. (new in iPerf 3.1)Ī letter specifying the format to print bandwidth numbers in. This should be the same in both client and server. The server port for the server to listen on and the client to connect
IPerf 3 user documentation GENERAL OPTIONS Compatibility mode allows for use with older version of iPerf (-C).Report as a Comma-Separated Values (-y).Exclude C(connection) D(data) M(multicast) S(settings) V(server) reports (-x).iPerf2 Features Not Supported by iPerf3 :.-logfile file : send output to a log file.
-udp-counters-64bit : Support very long-running UDP tests, which could cause a counter to overflow.-sctp use SCTP rather than TCP (Linux, FreeBSD and Solaris).-cport : Specify the client-side port.-I, -pidfile file write a file with the process ID, most useful when running as a daemon.iPerf3 will only allow one iperf connection at a time. -s, -server : iPerf2 can handle multiple client requests.
0 kommentar(er)
