Development discussion of WireGuard
 help / color / mirror / Atom feed
From: James Sinton <james.sinton@ims-evolve.com>
To: wireguard@lists.zx2c4.com
Subject: Throughput with Wireguard
Date: Mon, 4 May 2020 14:46:55 +0100	[thread overview]
Message-ID: <CA+cnKDFc2D2qJXsvonUS4sKUvvw8At-Mob-h5WBdN4LZvAFfQQ@mail.gmail.com> (raw)

Hi,

I was wondering whether anyone has any experience with Wireguard from
a performance point of view.  I'm looking at experimenting with a
solution to connect anything up to 10000 remote devices, to a cluster
of Wireguard endpoints.  These devices will be connected all of the
time sending data.  Probably terminating at AWS, Azure or GCP
endpoints.

I was wondering whether anyone had experience with Wireguard's
throughput capabilities against the resources needed.

Are there any inherent limitations to be aware of?
For example, is there a limit to the size of config that can be loaded?

Regards,

James Sinton
Technology Platform Manager
IMS Evolve | Better Choices Made Possible


The content of this message is confidential. If you have received it
by mistake, please inform us by an email reply and then delete the
message. It is forbidden to copy, forward, or in any way reveal the
contents of this message to anyone. The integrity and security of this
email cannot be guaranteed over the Internet. Therefore, the sender
will not be held liable for any damage caused by the message.
Intelligent Maintenance Systems Ltd is registered in England. Company
No. 04079715 Registered Address: 1st Floor, Matrix House, North Fourth
Street, Milton Keynes, MK9 1NJ

-- 
This e-mail, including any attachments, is intended for the above named 
recipient(s) only and may be confidential and the subject of legal 
professional privilege. 

Any disclosure, use, storage or copying of this 
email without the consent of the sender is strictly prohibited. Please 
notify the sender immediately if you are not the intended recipient and 
then delete the email from your inbox and do not disclose the contents to 
another person, use, copy or store the information in any medium.

                 reply	other threads:[~2020-05-06 10:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CA+cnKDFc2D2qJXsvonUS4sKUvvw8At-Mob-h5WBdN4LZvAFfQQ@mail.gmail.com \
    --to=james.sinton@ims-evolve.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).