From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: maximilian.pudelko@tum.de
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Poor performance under high load
Date: Tue, 26 Jun 2018 19:57:39 +0200 [thread overview]
Message-ID: <CAHmME9rKJQGJND76mFSFMdKJ+gf_kKQxOyd_rAnrVVUJkEZp5g@mail.gmail.com> (raw)
In-Reply-To: <CAJ5iZ8_X4Wk1BeLxdkWYViZRN+biJ--AA2w9CojJcciW_RmrZw@mail.gmail.com>
Hi Max,
Thanks for doing this test; that's super useful. What you're
describing is definitely not expected behavior. Think you could try
the same test with 0.0.20180620 and 0.0.20180625? In particular, I'm
interested to know whether a performance _regression_ introduced in
0.0.20180620 actually results in the correct behavior.
Meanwhile, we (CC'd) have been working on implementing a lockfree
queue structure, but we haven't seen any configurations yet where this
actually results in a performance improvement.
Care to share your benchmark scripts? Sounds like this could be really
useful for directing our optimizations.
Jason
next prev parent reply other threads:[~2018-06-26 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 7:49 Maximilian Pudelko
2018-06-26 17:57 ` Jason A. Donenfeld [this message]
2018-07-02 12:22 ` Maximilian Pudelko
2018-07-09 19:23 ` Jason A. Donenfeld
2018-07-09 20:53 ` logcabin
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=CAHmME9rKJQGJND76mFSFMdKJ+gf_kKQxOyd_rAnrVVUJkEZp5g@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=maximilian.pudelko@tum.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;
as well as URLs for NNTP newsgroup(s).