Typically, your user sends network throughput problems reports as they see problem with their applications such as:
[a] FTP Transfer
[b] NFS Performance
[c] HTTP / SMTP / POP3 etc
As a sys admin you should able confirm the throughput problem. iperf is the tool you are looking to find out:
a) Network throughput problem
b) Packet loss problem
c) Datagram loss
d) Delay jitter
From the man page:
iperf is a tool to measure maximum TCP bandwidth, allowing the tuning of various parameters and UDP characteristics.
iperf works on client / server model. You need to install iperf on both client computer and server computer to measure network performance between two nodes.
So by comparing the reported applications throughput with the measured TCP throughput and the measured available bandwidth, it is possible:
a) To Find out applications problems
b) TCP stack problems
c) Network issues
d) Bandwidth bottleneck problems etc
There is also ttcp program, which is a benchmarking tool for determining TCP and UDP performance between 2 systems.
Taks: Install iperf
If you are using Debian / Ubuntu Linux, enter:
$ sudo apt-get install iperf
If you are using FreeBSD, enter:
# cd /usr/ports/benchmarks/iperf
# make install clean
Source code installation for RHEL / CentOS:
# gunzip -c iperf-
# cd iperf-
# make; make install
You can also use the yum command as follows with EPEL repo:
# yum install iperf
Start iperf on server
To start iperf on server, type the following command:
root@freebsd42 # /usr/local/bin/iperf -s
Output:
------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------
Test iperf from client
Try to connect to your FreeBSD server called freebsd42 using Linux client located in other data center, enter:
$ iperf -c freebsd42
Output (note my freebsd42 server is on slow internet link):
------------------------------------------------------------
Client connecting to freebsdbox, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.106 port 40256 connected with 71.zzz.xxx.yyy port 5001
[ 3] 0.0-10.7 sec 624 KBytes 480 Kbits/secThe last line (the red numbers) specifies the speed.
Use UDP rather than TCP
The -u option force to use UDP. The following example run udp test and bandwidth to send at in bits/sec is specified using the -b option:
$ iperf -c rhelbox -u -l 512 -b 10m
Further readings:
- iperf project home page
- iperf man page
Other Recommended Bandwidth Measurement Tools
Apart from iperf, you can also use following tools to evaluate the bandwidth between two points in the network:
- Bandwidth Test Controller (BWCTL)
- ndt (Network Diagnostic Tool)
- Netperf (network performance benchmark)
- Thrulay (Improved version)
You should follow me on twitter here or grab rss feed to keep track of new changes.
Featured Articles:
- 30 Handy Bash Shell Aliases For Linux / Unix / Mac OS X
- Top 30 Nmap Command Examples For Sys/Network Admins
- 25 PHP Security Best Practices For Sys Admins
- 20 Linux System Monitoring Tools Every SysAdmin Should Know
- 20 Linux Server Hardening Security Tips
- Linux: 20 Iptables Examples For New SysAdmins
- Top 20 OpenSSH Server Best Security Practices
- Top 20 Nginx WebServer Best Security Practices
- 20 Examples: Make Sure Unix / Linux Configuration Files Are Free From Syntax Errors
- 15 Greatest Open Source Terminal Applications Of 2012

- My 10 UNIX Command Line Mistakes
- Top 10 Open Source Web-Based Project Management Software
- Top 5 Email Client For Linux, Mac OS X, and Windows Users
- The Novice Guide To Buying A Linux Laptop











{ 4 comments… read them below or add one }
Thanks for such good info sharing
Very concise and useful intro. Thanks a lot.
Thanks a lot
How to compare our test results? I mean what is the standard values for bandwidth,data gram loss, etc….How do i know my test is giving efficient results?