Tune network performance with iPerf3 on Arm Linux
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Confirm that the server prints output similar to
Server listening on 5201 (test #1). If the default port is busy, restart it on another port with the -p option.Verify network reachability and confirm that you used the correct IP address or hostname. Ensure that your cloud security group allows inbound TCP traffic to the selected iPerf3 port.
Start iPerf3 in server mode on the system designated as
SERVER. Run the test from the other system, which acts as the client.Run
ip addr show on the client to identify the active network interface. Use that interface name, such as ens5, when you apply delay or loss with tc.Rerun iPerf3 and compare its output with your instance-to-instance baseline. Use the measured throughput, jitter, and packet-loss values to see how the new network conditions affect performance.