||This article includes a list of references, but its sources remain unclear because it has insufficient inline citations. (January 2012)|
|Developer(s)||The Iperf team|
|Stable release||2.0.5 / July 9, 2010|
|Stable release||3.0.3 / March 26, 2014|
Iperf is a commonly used network testing tool that can create Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) data streams and measure the throughput of a network that is carrying them. Iperf is a tool for network performance measurement written in C. Iperf was developed by the Distributed Applications Support Team (DAST) at the National Laboratory for Applied Network Research (NLANR), a research lab that merged with the University of California San Diego's Cooperative Association for Internet Data Analysis (CAIDA) group, but which was shut down on December 31, 2006, due to termination of funding by the United States' National Science Foundation.
Iperf allows the user to set various parameters that can be used for testing a network, or alternatively for optimizing or tuning a network. Iperf has a client and server functionality, and can measure the throughput between the two ends, either unidirectionally or bi-directionally. It is open-source software and runs on various platforms including Linux, Unix and Windows (either natively or inside Cygwin).
- UDP: When used for testing UDP capacity, Iperf allows the user to specify the datagram size and provides results for the datagram throughput and the packet loss.
- TCP: When used for testing TCP capacity, Iperf measures the throughput of the payload. Iperf uses 1024 × 1024 for megabytes and 1000 × 1000 for megabits.
Typical Iperf output contains a time-stamped report of the amount of data transferred and the throughput measured.
Iperf is significant as it is a cross-platform tool that can be run over any network and output standardized performance measurements. Thus it can be used for comparison of both wired and wireless networking equipment and technologies. Since it is also open source, the measurement methodology can be scrutinized by the user as well.
Graphical user interface
A rewrite of Iperf from scratch, with the goal of a smaller, simpler code base and a library version of the functionality that can be used in other programs, called iperf3, was started in 2009. The first iperf3 release was made in January 2014. The website states: "iperf3 is not backwards compatible with iperf2.x".
Public iperf servers
- iperf.eltel.net (works with v2 checked on 20140317)
- iperf.scottlinux.com (connect failed: Network is unreachable on 20140317)(works with v2 checked on 20140419 from Kolkata,India)
- mptcp.info.ucl.ac.be (works with v2 checked on 20140317)
- iperf.saratov.ertelecom.ru (works with v2 checked on 20140317)
- st2.nn.ertelecom.ru (works with v2 checked on 20140317)
- iperf.belltec.com (works with v2 checked on 20140320)
- Ttcp, bwping, Flowgrind: tools of a similar nature.
- Measuring network throughput
- Packet generation model
Public test servers
- http://acd.net ACD.net: iperf.acd.net
- http://sct.gob.mx SCT: 184.108.40.206 -p 8001 TCP & -p 8002 UDP
- Measure Network Performance with iperf (Part 1), (Part 2), article published by Enterprise Networking Planet
- Long Distance WiFi Trial, iperf used to measure 70 km Wi-Fi link
- Measuring end-to-end bandwidth with Iperf using Web100, whitepaper on modifications to Iperf to be less intrusive