Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Luki Goldschmidt <lugo@uw.edu>
To: wireguard@lists.zx2c4.com
Subject: Performance on 10G / 1500 MTU link
Date: Mon, 14 Mar 2022 10:16:28 -0700	[thread overview]
Message-ID: <506c5c38-8451-7982-f2fe-d9a489e71752@ipd.uw.edu> (raw)

Hi,

Has anyone succeeded in saturating a 10Gb link with a MTU 1500 using
WireGuard?

On a LAN with 10Gb or 40Gb links, I'm getting 5-6 Gbps throughput with
WireGuard (tunnel MTU 1420). Without WireGuard, I have no problem
pushing 9.8 and 35 Gbps, respectively. When I increase the tunnel MTU to
8920, I can easily push 9.3 Gbps through Wireguard.

I'm testing testing with iperf using a single or multiple parallel
transfers. I tried kernels 5.14 and 5.15, and a range of CPUs like Intel
E5-2680v4, E3-1270v6, Xeon Silver 4114. The bottleneck seems to linked
to packets per second.

I can't use jumbo frames over the WAN connection so MTU 1500 (link) will
have to be it, but I'd love to get the most out of the 10 Gbps
connection. The WAN link latency is only ~1 ms so it ought to be doable.

Any tuning tips are appreciated.

Luki


                 reply	other threads:[~2022-03-21 19:34 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=506c5c38-8451-7982-f2fe-d9a489e71752@ipd.uw.edu \
    --to=lugo@uw.edu \
    --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).