iPerf Test

iPerf is a network performance test used to measure the data transfer capacity between two endpoints over a computer network. iPerf is an open-source software that operates on a client-server architecture. This test measures the real-time bandwidth data transfer rate latency packet loss and connection stability.

The iPerf tool typically operates over TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) and provides users with the ability to define various parameters for evaluating network performance.

The iPerf3 version is a modern rewritten version of the software and is not backward compatible with the previous version iPerf2. This version supports unidirectional and bidirectional tests IPv4 and IPv6 support multiple parallel stream measurements QoS class markers and export of results in JSON format.

iPerf operates at the 4th layer of the OSI model (Transport Layer) testing delay and data transmission at the protocol level. Unlike ICMP-based tools such as ping or traceroute it performs measurements over actual TCP sessions or UDP streams.

Working Principle

The iPerf test is conducted between two endpoint devices:

• Server: The receiving side of the test that listens for incoming data and generates measurement results.
• Client: The transmitting side that determines the direction of the test.

The client sends data to the server for a specified duration and at the end of this period the system calculates metrics such as transfer rate total data volume and packet statistics. This structure enables performance testing across the entire connection path between two endpoints not just a single network segment.

When an iPerf test is initiated the client-side parameters are defined such as duration port number protocol type and number of parallel connections. On the server side the program is run in listening mode (iperf3 -s). Upon completion the client reports metrics including average bandwidth throughput jitter packet loss rate RTT Round Trip Time and transfer times.

iPerf tests execute by writing data flows to a buffer and sending packets at specified MTU Maximum Transmission Unit sizes. In TCP tests flow control window size and retransmission mechanisms are active while in UDP tests since packet order is not preserved the measurement directly represents the raw capacity of the network.

Use Cases

iPerf is used by network administrators system engineers and data center operators in various scenarios:

• Server-to-server connection tests: Verifying the connection speed between two physical or virtual servers in a data center.
• Switch-end device performance checks: Evaluating the capacity of network switches routers or wireless access points.
• Service provider validation: Measuring the bandwidth promised by an Internet service provider.
• Post-network-change tests: Observing the performance impact of new VLANs cabling or configuration changes.
• VPN and WAN link optimization: Conducting long-distance measurements to assess the impact of encryption tunneling or QoS classes.

These tests are commonly applied in LAN (Local Area Network) WAN (Wide Area Network) VPN wireless connections (Wi-Fi WLAN) and high-speed data centers (10G/40G/100G Ethernet) environments.

Basic Commands and Parameters

iPerf is executed from the command line and can be customized with numerous parameters. Some commonly used options in iPerf3 include:

• iperf3 -s: Starts the server in listening mode.
• iperf3 -c [IP-address]: Starts the client and sends a test to the specified IP address.
• -p [port number]: Enables testing over a different port.
• -t [duration]: Sets the test duration in seconds.
• -u: Performs the test using UDP instead of TCP.
• -b [rate]: Sets a bandwidth limit for UDP tests.
• -P [number of streams]: Creates multiple parallel connections for realistic performance testing on multi-core processors.
• --reverse: Tests the data flow in the reverse direction from server to client.
• --bidir: Performs simultaneous bidirectional data flow testing.
• --zerocopy: Reduces memory copying to minimize CPU load.
• --json: Outputs results in JSON format for integration with monitoring systems.

iPerf also displays RTT Round Trip Time calculations TCP window sizes (-w parameter) and buffer optimizations during the test.

Test Types and Measurement Criteria

iPerf tests measure performance based on different protocols:

• TCP test: Measures the total bandwidth and connection stability of the network. Since TCP is connection-based it performs retransmissions in case of packet loss representing the most realistic scenario for actual user traffic.
• UDP test: Evaluates packet loss jitter and performance in real-time applications. UDP tests are particularly used to determine the suitability of latency-sensitive services such as voice VoIP and video streaming.
• Bidirectional test: Measures data flow simultaneously in both client-to-server and server-to-client directions.
• Parallel test: Performs concurrent measurements over multiple TCP or UDP streams enabling testing of the network’s multi-connection capacity buffer performance and QoS policy effects.

The primary measurement values obtained are:

• Throughput (bandwidth): Amount of data transferred per second Mbps Gbps.
• Jitter: Variation in packet arrival times ms.
• Packet loss: Ratio of lost packets relative to the total number sent.
• Retransmissions: TCP retransmission rate.
• RTT and CWND: Average round-trip time and window size in the TCP session.

Example Test Scenario

In a typical iPerf3 test the following command is executed on the server side:

On the client side the test command is executed as follows:

This command initiates a TCP test to the server at 192.168.1.10 using four parallel streams for 30 seconds.

Upon completion the output includes the following information:

• Amount of data transferred per stream
• Average bandwidth e.g. 8.72 Gbps
• Latency
• Packet loss in UDP tests.

When analyzing these values it is important to consider that system CPU usage network interface card drivers IRQ distribution and MTU size directly affect test results. Especially at speeds above 10 Gbps single-core bottlenecks or NIC driver limitations can reduce measurements.

Interpreting Results and Optimization

iPerf test results reveal the efficiency of the network infrastructure bottleneck points and hardware limitations.

• High bandwidth and low jitter indicate stable network operation.
• High packet loss or low throughput values may indicate issues with line quality buffering cabling or network interface problems.
• Unidirectional low speeds may result from directional QoS firewall policies or asymmetric routing.

iPerf outputs can be saved in JSON format and integrated into automation systems network monitoring software such as Grafana Zabbix PRTG or NetAlly Link-Live and CI/CD network test pipelines.

In large-scale networks tests are scheduled using cron PowerShell or Ansible and statistical averages are calculated for capacity planning.

Hardware and Security Factors

iPerf measurements depend not only on the network but also on the hardware limitations of the systems being tested.

• CPU load: Packet processing speed and core count affect throughput.
• NIC features: Hardware offloading jumbo frames and IRQ balancing improve performance.
• MTU settings: If Ethernet MTU e.g. 9000-byte jumbo frames is not optimized segmentation may occur during testing.
• Firewalls and IDS/IPS systems: Packet inspection can limit test results.

Therefore iPerf tests are typically conducted in isolated network segments or test VLANs.

iPerf is a tool that objectively evaluates network connection performance by conducting protocol-level measurements. Its client-server architecture support for TCP/UDP and bidirectional and parallel test modes provide network administrators with comprehensive analysis capabilities. iPerf is a fundamental measurement method used in numerous scenarios from bandwidth validation to QoS analysis for network infrastructure capacity planning and fault detection.