From: Roman Mamedov <rm@romanrm.net>
To: Christopher Bachner <hello@chrisbox.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Speed on Raspberry Pi 4
Date: Thu, 18 Jul 2019 01:50:27 +0500 [thread overview]
Message-ID: <20190718015027.00e6010f@natsu> (raw)
In-Reply-To: <CAKJniYRn7ZkV9tGOpK=mZoDb24TfMyq44zgE0c5uPo+Ac-sZsA@mail.gmail.com>
On Sat, 29 Jun 2019 12:38:01 +0200
Christopher Bachner <hello@chrisbox.org> wrote:
> In htop I can see that one of the 4 cores is running at 99%. So I assume
> that is the bottleneck.
>
> Is there a way to improve this? I assume it does not matter which side is
> the server and which is the client?
You can see that the load from WireGuard encryption is about 42-43% per each
core. But the thing is, one of them (the 1st) also gets to process interrupt
load from the NIC, and that consumes the rest of it, causing the bottleneck. In
theory, if you could limit WG to run encryption on all cores EXCEPT the first
one, then maaaaybe...
Another way would be to use a NIC which is capable of splitting interrupt load
across multiple CPU cores. But I believe the RPi one can't do that, and no USB
NICs can.
--
With respect,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-07-17 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 10:38 Christopher Bachner
2019-07-17 20:50 ` Roman Mamedov [this message]
2019-07-18 6:38 ` Janne Johansson
2019-07-18 6:56 ` Roman Mamedov
2019-07-18 8:01 ` Janne Johansson
2019-07-18 8:15 ` Matthias Urlichs
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=20190718015027.00e6010f@natsu \
--to=rm@romanrm.net \
--cc=hello@chrisbox.org \
--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).