Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard Snapshot `0.0.20180620` Available
Date: Wed, 20 Jun 2018 15:11:13 -0500	[thread overview]
Message-ID: <8B706799-0A06-449B-960B-08C017C58412@lonnie.abelbeck.com> (raw)
In-Reply-To: <b9a4b41fbe912803@frisell.zx2c4.com>


> On Jun 20, 2018, at 2:19 PM, Jason A. Donenfeld <Jason@zx2c4.com> =
wrote:
>=20
> A new snapshot, `0.0.20180620`, has been tagged in the git repository.

I find 0.0.20180620 much slower than previous version 0.0.20180531

All things being equal, only WireGuard version changes.

Both boxes:
# uname -a
Linux pbx 3.16.54-astlinux #1 SMP PREEMPT Mon Jun 11 09:17:57 CDT 2018 =
x86_64 GNU/Linux


Test: 0.0.20180531
--
Qotom Q190G4N-S07 NIC x4
# iperf3 -s

Jetway NF9HG-2930 NIC x4
# iperf3 -c 10.4.0.10 -t30 -P2

[SUM]   0.00-30.00  sec  2.65 GBytes   758 Mbits/sec  571             =
sender
[SUM]   0.00-30.02  sec  2.64 GBytes   756 Mbits/sec                  =
receiver
--

Test: 0.0.20180620
--
Qotom Q190G4N-S07 NIC x4
# iperf3 -s

Jetway NF9HG-2930 NIC x4
# iperf3 -c 10.4.0.10 -t30 -P2

[SUM]   0.00-30.00  sec  1.50 GBytes   430 Mbits/sec   96             =
sender
[SUM]   0.00-30.02  sec  1.50 GBytes   428 Mbits/sec                  =
receiver
--

Interesting note, using -P1 the difference is not as pronounced, but =
still slower.

Any ideas ?

Lonnie

  reply	other threads:[~2018-06-20 20:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 19:19 Jason A. Donenfeld
2018-06-20 20:11 ` Lonnie Abelbeck [this message]
2018-06-20 20:33   ` Matthias Urlichs
2018-06-20 21:24   ` Jason A. Donenfeld
2018-06-20 22:37     ` Lonnie Abelbeck
2018-06-20 23:47       ` Jason A. Donenfeld
2018-06-21  0:22         ` Lonnie Abelbeck
2018-06-21 13:51           ` Lonnie Abelbeck

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=8B706799-0A06-449B-960B-08C017C58412@lonnie.abelbeck.com \
    --to=lists@lonnie.abelbeck.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).