From: Joe Doss <joe@solidadmin.com>
To: wireguard@lists.zx2c4.com
Subject: Re: wireguard performance
Date: Mon, 4 Apr 2022 17:56:24 -0500 [thread overview]
Message-ID: <22f7069e-fac3-09e8-5f2e-2d3c93506352@solidadmin.com> (raw)
In-Reply-To: <CADjMg7VSw58f+2Pj9_aJOupVPcAneVA9DDbmVLGEVpZW_XY2nw@mail.gmail.com>
On 4/4/22 4:34 PM, Devanath S wrote:
> We were trying to test the performance of wireguard on GCP and found
> it around 1G for TCP and around 500-800 for UDP.
>
> Plz do let us know if there are any ways to UP this performance. Any
> suggestion is appreciated.
GCP network defaults to a lower MTU (1460). You might want to adjust
your WireGuard tunnel's MTUs and the default GCP VPC MTU. See:
https://cloud.google.com/network-connectivity/docs/vpn/concepts/mtu-considerations
Joe
--
Joe Doss
joe@solidadmin.com
next prev parent reply other threads:[~2022-04-04 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 21:34 Devanath S
2022-04-04 22:56 ` Joe Doss [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-26 12:30 Wireguard performance Tiago Condeixa
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=22f7069e-fac3-09e8-5f2e-2d3c93506352@solidadmin.com \
--to=joe@solidadmin.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).