WireGuard performance with a Pi 3 A+
Posted May 21, 2019
3 minute read
As with the other test, my client was a VM running Debian with 2 CPU cores and 2GB of RAM as to not be a bottleneck in this test.
My Raspberry Pi 3A+ is running Raspbian Lite (April 2019 version) rather than something like DietPi or Armbian.
Note: in the Asciicasts below, some have two panes split horizontally. This is me using tmux to access the Debian VM on top and the Pi Zero on bottom to keep an eye on CPU utilization while performing these tests.
The tests 🔗
To start, here is a baseline of running iperf from my Debian VM to the Pi Zero without WireGuard:
This speed is pretty much wire speed for a 100mb USB NIC.
I’ll now turn on WireGuard and try iperf again:
It looks like the results are still near wire speed, and the CPU utilization is fairly even across all four CPU cores when running WireGuard.
I’ll now run the same speedtest-cli tests that I did in the Pi Zero benchmark, testing first from the Pi to the internet:
Again, near wire speed in this test.
Now I’ll paste the Asciicast from the other test, just because I don’t feel a need to replicate the test 🙃:
And now a few tests from the Debian VM running over WireGuard (while setting all IPv4 traffic to flow over WireGuard):
As you can see, the speeds vary from 46 to 80 mbps download, and 20 to 60 mbps upload. Either way, this Pi is definitely more capable than the Pi Zero to handle WireGuard traffic. With the extra headroom, you could even run other services such as an Nginx reverse proxy or other similar services if you decide to run this at the DMZ edge of your home network, or as a simple server in any other type of network.