wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Scott Lipcon <slipcon@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: performance query
Date: Tue, 26 Feb 2019 15:53:22 -0500	[thread overview]
Message-ID: <CAJwvAosHFogtuPL09C9ek4bz6A7vW76mzKymL11iWs+9F7Ep_Q@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1291 bytes --]

I've been experimenting a bit with Wireguard on several ubuntu systems, and
am not seeing the performance I'd expect based on the numbers at
https://www.wireguard.com/performance/

I'm wondering if there is a configuration setting i'm missing or any better
way to debug this.

Testing between two locations - both have nominally 1Gbit internet
connections from the same provider.

At location A:
1) Ubuntu 18.04 "server" - i7-4790K CPU @ 4.00GHz
2) Ubuntu 16.04 client - i5-3470 CPU @ 3.20GHz

At location B:
3) Ubuntu 18.04 client - Celeron N2808  @ 1.58GHz
4) Ubuntu 18.04 client - Virtual Machine - Xeon(R) Gold 6126 CPU @ 2.60GHz


Using iperf3 for all tests, with 8 threads, but that doesn't seem to matter
significantly.

Between 1 & 2, via gigabit LAN - 940 Mbit/sec.
Between 1 & 2, via WireGuard - 585 Mbit/sec
- I might have expected a bit higher, but this is certainly acceptable.

Between 3 and 1, direct iperf3 - 580 Mbit/sec
Between 3 and 1, WireGuard - 73 Mbit/sec

At this point I was guessing WireGuard was CPU limited on this little
Celeron, so I set up the Xeon VM (#4):

Between 4 and 1, direct iperf3 - ~600 Mbit/sec
Between 4 and 1, WireGuard - 80 Mbit/sec

In other words, the much faster VM is only a tiny bit faster that the
celeron.

Any suggestions?

Thanks,
Scott

[-- Attachment #1.2: Type: text/html, Size: 4601 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2019-03-01 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 20:53 Scott Lipcon [this message]
2019-03-01 10:18 ` performance query Kalin KOZHUHAROV
2019-03-02  4:08   ` Scott Lipcon
2019-03-08 16:45     ` Christopher Bachner
2019-03-11 16:23     ` Scott Lipcon

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=CAJwvAosHFogtuPL09C9ek4bz6A7vW76mzKymL11iWs+9F7Ep_Q@mail.gmail.com \
    --to=slipcon@gmail.com \
    --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).