From: James Wynn <jameswynn23@proton.me>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Throughput significantly lower than expected, possible regression?
Date: Mon, 30 Jan 2023 12:26:51 +0000 [thread overview]
Message-ID: <6bLjfHXI_ooAaDHnWuIx4oVWGCoSbAfYtUxpL4bakYfOSb0nQnfD3viB1b_xFhtpVmpF_OQbFTJza15Ea65FJMwAQ0Avq4raIwVBDFl8L-w=@proton.me> (raw)
Hi.
I noticed a massive performance regression for WireGuard on Ubuntu 20.04, Ubuntu 22.04 and Fedora 37. I reported in Ubuntu and Fedora users mailing list and was advised to post here.
It's possible I did something wrong(?), but 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 between two droplets (over VPC) with `iperf3 -c XXX -P 5`:
- DigitalOcean's VPC = ~2Gbps
- WireGuard Ubuntu 18.04 = ~1.3Gbps
- WireGuard Ubuntu 20.04 = ~400Mbps
- WireGuard Ubuntu 22.04 = ~400Mbps
- WireGuard Fedora 37 = ~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 OS 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_FRONTEND=noninteractive apt-get dist-upgrade -y && reboot`
3. `apt-get install -y wireguard iperf3`
4. On test01, create `/etc/wireguard/test.conf` with these contents. Replace `YYY` with the IP address of the eth1 interface (VPC) on test02.
--------------------
[Interface]
PrivateKey = wOEa8/RS2v065wgYGQn5k7FqOXuZJ9aC/6NDW569c3g=
Address = 192.168.200.10/24
ListenPort = 51820
SaveConfig = false
[Peer]
PublicKey = wdXOzBptLD/QMZjhG475GErrz95Vpj4S7JPEwzcDMV8=
PresharedKey = j5Oeyhu/qDag2LunpVlFqKycp/9CH+Izjza5aq2cYss=
Endpoint = YYY:51820
AllowedIPs = 192.168.200.20/32
--------------------
5. On test02, create `/etc/wireguard/test.conf` with these contents. Replace `XXX` with the IP address of the eth1 interface (VPC) on test01.
--------------------
[Interface]
PrivateKey = kCJ/4rVDTy86HxP9N5wUmgMF1Esqjc051jQPGhrQIGw=
Address = 192.168.200.20/24
ListenPort = 51820
SaveConfig = false
[Peer]
PublicKey = s/GtXkHOtPsqcNDy0BSRoMuxXYb4hK18dsQdkZk20yQ=
PresharedKey = j5Oeyhu/qDag2LunpVlFqKycp/9CH+Izjza5aq2cYss=
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` and observe ~400Mbps.
In steps 7 and 8, replace XXX with the IP address of the eth1 interface on test01.
reply other threads:[~2023-02-07 4:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='6bLjfHXI_ooAaDHnWuIx4oVWGCoSbAfYtUxpL4bakYfOSb0nQnfD3viB1b_xFhtpVmpF_OQbFTJza15Ea65FJMwAQ0Avq4raIwVBDFl8L-w=@proton.me' \
--to=jameswynn23@proton.me \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).