Massive (3x) performance regression for WireGuard in Ubuntu 20.04 and 22.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wireguard (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have fully reproducible steps to demonstrate this issue on a vanilla DigitalOcean droplet, minimal WireGuard configuration and no firewall rules. I've also seen this issue on other hosting providers.
Testing with `iperf3 -c XXX -P 5`:
- Unencrypted traffic on DigitalOcean's VPC = ~2Gbps
- WireGuard Ubuntu 18.04 = ~1.3Gbps
- WireGuard Ubuntu 20.04 = ~400Mbps
- WireGuard Ubuntu 22.04 = ~400Mbps
htop reported only 20-30% load on the vCPU core so it isn't CPU-bound.
After doing these tests, I did them all again on a different day to rule out temporary network congestion.
Steps to reproduce below. Repeat with each Ubuntu version.
0. Create a DigitalOcean account.
1. Create two $6 droplets (eg, LON1 region) with Regular CPU & 1GB RAM each, called test01 & test02.
2. `apt-get update && DEBIAN_
3. `apt-get install -y wireguard iperf3`
4. On test01, create `/etc/wireguard
-------
[Interface]
PrivateKey = wOEa8/RS2v065wg
Address = 192.168.200.10/24
ListenPort = 51820
SaveConfig = false
[Peer]
PublicKey = wdXOzBptLD/
PresharedKey = j5Oeyhu/
Endpoint = YYY:51820
AllowedIPs = 192.168.200.20/32
-------
5. On test02, create `/etc/wireguard
-------
[Interface]
PrivateKey = kCJ/4rVDTy86HxP
Address = 192.168.200.20/24
ListenPort = 51820
SaveConfig = false
[Peer]
PublicKey = s/GtXkHOtPsqcND
PresharedKey = j5Oeyhu/
Endpoint = XXX:51820
AllowedIPs = 192.168.200.10/32
-------
6. On both droplets, run `systemctl start wg-quick@test`
7. On test01, run `iperf3 -s -B XXX`.
8. On test02, run `iperf3 -c XXX -P 5 -t 30` and observe ~2Gbps.
9. On test01, run `iperf3 -s -B 192.168.200.10`
10. On test02, run `iperf3 -c 192.168.200.10 -P 5 -t 30`
In steps 7 and 8, replace XXX with the IP address of the eth1 interface on test01.
description: | updated |
description: | updated |
Are these droplets running an ubuntu kernel, or a Digital Ocean kernel? The type of interface (virtio) also matters.