Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Daryl Richards <>
Subject: Re: absolutely terrible wireguard performance on a 4ghz box - need tuning help
Date: Fri, 4 Nov 2022 16:10:31 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022-10-25 2:58 a.m., Kyle Sanderson wrote:
> hi wireguard,
> APU2C4 - AMD Embedded G series GX-412TC, 1 GHz quad Jaguar core with
> 64 bit and AES-NI support
> There has to be a way to improve this. I'm getting 20-40MB/s (causing
> a system load of 6 on this poor box) where SSHFS in comparison is
> still able to fly. Traffic not traversing the tunnel is also,
> strangely, impacted as well. I have the Intel i210AT controller, which
> doesn't appear to have any offloading to it when wireguard is present.
> ksoftirqd/0 spins at around 50%, ksoftirqd/1 spins around 20%, and the
> other 12(!) wg-crypt threads hover around 20% respectively.
> If I disable wg I'm able to get line-rate through acceleration.
> The other 2 ksoftirqds sit around 5% respectively. kworker events
> jumping between 10-25%.
> Regrettably openwrt doesn't appear to have perf available...

Perhaps this is an OpenWRT issue? I have a number of these APUs with 
astlinux installed, doing wireguard, and can easily do 300-400mbps, and 
that's across the internet so perhaps faster if on a test bench.

The APU isn't the problem..

  reply	other threads:[~2022-11-04 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  6:58 Kyle Sanderson
2022-11-04 20:10 ` Daryl Richards [this message]
2022-11-04 20:55 ` Metin Evrim Ulu

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).