From: Jari Tenhunen <jari.tenhunen@iki.fi>
To: wireguard@lists.zx2c4.com
Subject: Very modest performance observed on macOS
Date: Thu, 18 Apr 2019 13:20:14 +0300 [thread overview]
Message-ID: <CAFC8xAL5U0enO9+-rKGz4xhXnNLsr1rkQ_Z+fFSWMp=4=gtNGA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 738 bytes --]
Hi,
I experimented with WireGuard on a 13" MacBook Pro (2018, core i5) and was
surprised to see that all implementations running on macOS (WireGuard app
from App Store, Boringtun, and WireGuard-go) achieved a max throughput of
only 80-100 Mbit/s. And what is even more strange, when running these same
implementations in a Linux container on Docker (on the same machine,
against the same peer), the performance is clearly better, close to 150
Mbit/s. In the latter case, it is probably limited by the peer HW
performance (Raspberry Pi 3B), so it could be even higher. I got these
throughput numbers by running iperf inside the tunnel.
Do you have any idea what is limiting the performance on macOS? Inefficient
utun driver?
BR,
Jari
[-- Attachment #1.2: Type: text/html, Size: 883 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-05-06 20:28 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='CAFC8xAL5U0enO9+-rKGz4xhXnNLsr1rkQ_Z+fFSWMp=4=gtNGA@mail.gmail.com' \
--to=jari.tenhunen@iki.fi \
--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).