From: Tiago Condeixa <tcondeixa@veniamworks.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Wireguard performance
Date: Mon, 26 Jun 2017 13:30:35 +0100 [thread overview]
Message-ID: <CCB871CE-1067-41E6-BE5F-837362773C7D@veniamworks.com> (raw)
Hi,
I have been doing more experiments with heterogenous technologies and =
connections and there is a scenario where I believe that something =
strange is happening with wireguard.
When my board is using a 100 Mbps ethernet connection in a local network =
the iperf3 TCP is able to reach 95Mbps with the direct IP route, but =
when using wireguard the throughput reduces to 65/70 Mbps.=20
It=E2=80=99s not a bad result at all, but I noticed that with wireguard =
the iperf3 CPU consumption goes from 10% to 70% when comparing with =
direct IP route. Do you have any idea why is this happening? ...the =
overall system CPU can slightly increase but I do not expect that happen =
with iperf3.
In other scenarios with other technologies and networks wireguard =
usually reduce 5% of the throughput but in this case it goes beyond 25%.
Thanks a lot,
Tiago=
next reply other threads:[~2017-06-26 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 12:30 Tiago Condeixa [this message]
2022-04-04 21:34 wireguard performance Devanath S
2022-04-04 22:56 ` Joe Doss
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=CCB871CE-1067-41E6-BE5F-837362773C7D@veniamworks.com \
--to=tcondeixa@veniamworks.com \
--cc=Jason@zx2c4.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).