Traffic shaper benchmark

These are the results of a traffic shaper benchmark. This previous post describes the complete configuration and setup instructions on OpenWRT.

I’ll be running a simple ping while doing a speedtest on speedtest.net.

Benchmark without shaping

Ping results

Below you can find the ping response times. The destination is www.google.com.

$ ping www.google.com
PING www.google.com (173.194.66.105) 56(84) bytes of data.
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=1 ttl=47 time=24.9 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=2 ttl=47 time=18.9 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=3 ttl=47 time=19.6 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=4 ttl=47 time=52.7 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=5 ttl=47 time=134 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=6 ttl=47 time=89.8 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=7 ttl=47 time=177 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=8 ttl=47 time=246 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=9 ttl=47 time=250 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=10 ttl=47 time=210 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=11 ttl=47 time=368 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=12 ttl=47 time=307 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=13 ttl=47 time=391 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=14 ttl=47 time=21.2 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=15 ttl=47 time=63.1 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=16 ttl=47 time=300 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=17 ttl=47 time=366 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=18 ttl=47 time=190 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=19 ttl=47 time=412 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=20 ttl=47 time=464 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=21 ttl=47 time=148 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=22 ttl=47 time=499 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=23 ttl=47 time=658 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=24 ttl=47 time=507 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=25 ttl=47 time=485 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=26 ttl=47 time=734 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=27 ttl=47 time=704 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=28 ttl=47 time=52.2 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=29 ttl=47 time=893 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=30 ttl=47 time=885 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=31 ttl=47 time=298 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=32 ttl=47 time=18.5 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=33 ttl=47 time=20.5 ms
64 bytes from we-in-f105.1e100.net (173.194.66.105): icmp_req=34 ttl=47 time=18.1 ms
^C
--- www.google.com ping statistics ---
34 packets transmitted, 34 received, 0% packet loss, time 33036ms
rtt min/avg/max/mdev = 18.141/295.204/893.783/254.974 ms
$

Speedtest results

Without shaping

Traffic shaper benchmark without shaping

Benchmark with shaping

Ping results

$ ping www.google.com
PING www.google.com (173.194.67.106) 56(84) bytes of data.
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=1 ttl=47 time=19.1 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=2 ttl=47 time=18.4 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=3 ttl=47 time=18.2 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=4 ttl=47 time=18.9 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=5 ttl=47 time=24.4 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=6 ttl=47 time=28.7 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=7 ttl=47 time=25.6 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=8 ttl=47 time=25.6 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=9 ttl=47 time=30.8 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=10 ttl=47 time=22.7 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=11 ttl=47 time=24.2 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=12 ttl=47 time=24.8 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=13 ttl=47 time=22.7 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=14 ttl=47 time=24.5 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=15 ttl=47 time=22.1 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=16 ttl=47 time=20.1 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=17 ttl=47 time=19.7 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=18 ttl=47 time=20.8 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=19 ttl=47 time=21.1 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=20 ttl=47 time=17.5 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=21 ttl=47 time=21.9 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=22 ttl=47 time=17.8 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=23 ttl=47 time=19.9 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=24 ttl=47 time=21.2 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=25 ttl=47 time=18.0 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=26 ttl=47 time=22.6 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=27 ttl=47 time=20.8 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=28 ttl=47 time=20.0 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=29 ttl=47 time=18.6 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=30 ttl=47 time=17.3 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=31 ttl=47 time=20.3 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=32 ttl=47 time=18.8 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=33 ttl=47 time=17.5 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=34 ttl=47 time=18.1 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=35 ttl=47 time=18.5 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=36 ttl=47 time=19.2 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=37 ttl=47 time=18.2 ms
64 bytes from wi-in-f106.1e100.net (173.194.67.106): icmp_req=38 ttl=47 time=18.8 ms
^C
--- www.google.com ping statistics ---
38 packets transmitted, 38 received, 0% packet loss, time 37052ms
rtt min/avg/max/mdev = 17.320/21.026/30.842/3.183 ms
$

Speedtest results

shape

Traffic shaper benchmark with shaping

Differences

1. With shaping : lower download and upload speeds.
2. With shaping : speedtest has almost no impact on ping
3. Without shaping : speedtest is higher
4. Without shaping : ping response times increased a lot during the speedtest. Average is 15 times higher during speedtest.

Conclusion

1. The 2 speedtests show that the traffic shaper is limitting the amount of bandwidth that is used for upload and downloads from the internet. This seems to be a disadvantage.
2. The ping results show that the speedtest has a high impact on the response times. With traffic shaping enabled, this impact goes away. This is a clear advantage and the primary reason why I do traffic shaping on my network. The traffic of my voip phones are getting the same threatment as the ICMP packets. This results in better call quality.

1 thought on “Traffic shaper benchmark

  1. Pingback: Traffic shaping with OpenWRT | Thomas Elsen Security Blog

Leave a Reply

Your email address will not be published. Required fields are marked *