I have a gigabit network set up in my house and a few Ubuntu based boxes. Out of complete curiosity I would like to check the speed between the two boxes.
I am not having any problems with speed or anything, it really is just the geek in me that is curious. Plus maybe the results will let me know if there is room for improvement, or that I have something configured wrongly.
So how does one properly test the network speed between Ubuntu boxes?
I use iperf. It's a client server arrangement in that you run it in server mode at one end and connect to it from another computer on the other side of the network.
One both machines run:
sudo apt-get install iperf
We'll start an iperf server on one of the machines:
iperf -s
And then on the other computer, tell iperf to connect as a client:
iperf -c <address of other computer>
On the client machine, you'll see something like this:
oli@bert:~$ iperf -c tim
------------------------------------------------------------
Client connecting to tim, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.0.4 port 37248 connected with 192.168.0.5 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.04 GBytes 893 Mbits/sec
Of course, if you're running a firewall on the server machine, you'll need to allow connections on port 5001 or change the port with the -p flag.
You can do pretty much the same thing with plain old nc (netcat) if you're that way inclined. On the server machine:
nc -vvlnp 12345 >/dev/null
And the client can pipe a gigabyte of zeros through dd over the nc tunnel.
dd if=/dev/zero bs=1M count=1K | nc -vvn 10.10.0.2 12345
As a demonstration:
$ dd if=/dev/zero bs=1M count=1K | nc -vvn 10.10.0.2 12345
Connection to 10.10.0.2 12345 port [tcp/*] succeeded!
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 9.11995 s, 118 MB/s
The timing there is given by dd but it should be accurate enough as it can only output as fast as the pipe will take it. If you're unhappy with that you could wrap the whole thing up in a time call.
Remember that the result is in megabytes so multiply it by 8 to get a megabits-per-second speed. The demo above is running at 944mbps.
The command below does not require additional packages but SSH access:
ssh username@myserver.example.com 'dd if=/dev/zero bs=1GB count=3 2>/dev/null' | dd of=/dev/null status=progress
Example output:
2992238080 bytes (3.0 GB) copied, 27.010250 s, 111 MB/s
5859375+0 records in
5859375+0 records out
3000000000 bytes (3.0 GB) copied, 27.1943 s, 110 MB/s
The command prints a 3GB (1000^3 bytes) dummy file full of zeros to stdout on the remote server, which is printed (transferred) via SSH to stdout of the local server and then locally piped to /dev/null (i.e. ignored). You can even see the progress of the test while executing it.
Certainly not as precise as other tools but my use case was to debug a backup process where I wanted to test if network speed was the issue without installing additional packages.
Same as Oli's recommendation for iperf. Just want to add several points:
-t <seconds> changes the test length. -P <n> changes the number of simultaneous connections. For example, iperf -c [target IP] -P 10 -t 30 tests 10 connections together for 30 seconds and gives aggregated results along with 10 separate connection speeds.wget, make it executable with chmod, and you can directly run the binary. It works perfectly.I found that, using default settings, the single connection speed fluctuates quite a bit. However, with 3+ parallel connections, the results are more consistent on my gigabyte switch. (consistently @ 910-920Mbps)
Using this script you can easily test connection speed between your machine and some remote host. Example of using:
$ scp-speed-test.sh user@remote_host 80000
user@remote_host is your destination host (you must have ssh-access
to this host)80000 is the approximate size of test file (in kbs), which will be
received to the remote host. It is not mandatory argument.
If you want to test your Ethernet LAN at a lower level you can use Etherate which is a free Linux CLI Ethernet testing tool:
https://github.com/jwbensley/Etherate
Throwing it in the mix as tools like iPerf (which are very good!) operate over IP and TCP or UDP. Etherate tests directly over Ethernet / OSI layer 2.
There are also some other nice command-line tools for bandwidth benchmarking between two hosts:
server$ nuttcp -S
client$ nuttcp -v -v -i1 1.1.1.1 ;# 1.1.1.1 is server's address
server$ nepim
client$ nepim -d -c 1.1.1.1 ;# 1.1.1.1 is server's address
server$ goben
client$ goben -hosts 1.1.1.1 ;# 1.1.1.1 is server's address
as I pointed out in my comment at best answer, that solution is not good enough be cause client/server is not optimized to ... squeeze every bit of speed
my solution:
make a ramdisk on both sides (therefore, you aren't limited by storage speed and I suggest you made them with ramfs not tmpfs, so they won't go in swap ... just be careful not to leave at least 512M free memory for system, this is REQUIRED if you have giga ethernet, at that speed even SSDs may slow things down)
install apache on server, then create a link to ramdisk, create few large files on ramdisk (100M-1G, you can create them with dd from /dev/random or copy if you have some at hand)
then go client side and download them (also on that side's ramdisk) with an advanced download program, I used lftp
oh well, difference was major, from 75mbps reported by iperf and 9.5M/s netcat
to 11.18M/s with my solution:
1591129421 bytes transferred in 136 seconds (11.18M/s)
It's easy plug your computer on the first box, plug the other box to the first box. Then from your computer ping the first box save the result, ping the other box and do the substraction.
