From: Antonio Quartulli <a@unstable.cc>
To: Germano Massullo <germano.massullo@gmail.com>,
Max Schulze <max.schulze@online.de>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Mini PCIE HW accelerator for ChaCha20
Date: Mon, 17 Jun 2024 11:45:46 +0200 [thread overview]
Message-ID: <ce8cd757-3df9-4a71-818e-ae2eda6c9690@unstable.cc> (raw)
In-Reply-To: <cd332c8e-96c7-49e7-9632-066327a009af@gmail.com>
On 17/06/2024 11:21, Germano Massullo wrote:
> Il 16/06/24 21:00, Max Schulze ha scritto:
>> Ok then I think you really max out the cpu. I have not heard of any
>> acceleration card. Overall I think it's not too bad.
>
> The problem is that is far under my internet connection capabilities (1
> Gbit/s upload)
>
>> Are you running iperf3 with --bidir?
>
> Such flag halves the throughput, I am getting ~280 Mbit/s compared to
> the previous value I got by using
> iperf3 -c 10.0.50.1 -P 4 -Z bbr
> (using the Ryzen as client)
>> Keep in mind that iperf3 itself uses some cpu.
>> You could test serving a static file and transfer via http.
>
> The iperf3 CPU usage is not so high, it wouldn't change much to use the
> http transfer
Have you tried running the test between a client, behind the omnia
turris and the wg server?
I am asking because such embedded devices are not necessarily fast in
generating the traffic that iperf requires, therefore using a different
client may give you a better estimate.
Regards,
--
Antonio Quartulli
next prev parent reply other threads:[~2024-06-17 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 14:11 Mini PCIE HW accelerator for ChaCha20 Germano Massullo
2024-06-16 13:47 ` Max Schulze
2024-06-16 14:59 ` Germano Massullo
2024-06-16 19:00 ` Max Schulze
2024-06-17 9:21 ` Germano Massullo
2024-06-17 9:45 ` Antonio Quartulli [this message]
2024-06-17 11:08 ` Germano Massullo
2024-06-17 11:42 ` Antonio Quartulli
2024-06-17 12:32 ` Germano Massullo
2024-06-17 12:41 ` Roman Mamedov
2024-06-17 14:31 ` Germano Massullo
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=ce8cd757-3df9-4a71-818e-ae2eda6c9690@unstable.cc \
--to=a@unstable.cc \
--cc=germano.massullo@gmail.com \
--cc=max.schulze@online.de \
--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