wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Christophe Vanlancker <carroarmato0@inuits.eu>
To: Fierascu Vlad <mythnick@gmail.com>
Cc: wireguard <wireguard@lists.zx2c4.com>
Subject: Re: Limited speed 100Mbps Down 200Mbps UP
Date: Tue, 11 Feb 2020 15:29:40 +0100 (CET)	[thread overview]
Message-ID: <1374975524.57662.1581431380684.JavaMail.zimbra@inuits.eu> (raw)
In-Reply-To: <CAHyK+75Q7fOvnKjDNvJOZBjDWD+MzrBWGxM-a6L51c4LMbPf-g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2341 bytes --]

I have been running benchmarks on DigitalOcean with different droplets in different locations 
When using encryption it's expected to generally have a reduction in throughput. 

image="centos-7-x64" size="s-1vcpu-1gb" region="ams3" 
image="centos-7-x64" size="s-1vcpu-1gb" region="fra1" 

iperf direct-test: 
[ ID] Interval Transfer Bandwidth Retr 
[ 4] 0.00-10.00 sec 959 MBytes 805 Mbits/sec 637 sender 
[ 4] 0.00-10.00 sec 957 MBytes 803 Mbits/sec receiver 

iperf IPSec-test: 
[ ID] Interval Transfer Bandwidth Retr 
[ 4] 0.00-10.00 sec 206 MBytes 173 Mbits/sec 15 sender 
[ 4] 0.00-10.00 sec 206 MBytes 172 Mbits/sec receiver 

iperf WireGuard-test: 
[ ID] Interval Transfer Bandwidth Retr 
[ 4] 0.00-10.00 sec 481 MBytes 404 Mbits/sec 46 sender 
[ 4] 0.00-10.00 sec 478 MBytes 401 Mbits/sec receiver 


Many things can come into play, optimizations, maybe crypto acceleration etc, but that's beyond my expertise. 


From: "Fierascu Vlad" <mythnick@gmail.com> 
To: "cristian c" <cristian.c@istream.today> 
Cc: "wireguard" <wireguard@lists.zx2c4.com> 
Sent: Wednesday, 11 December, 2019 11:09:07 
Subject: Re: Limited speed 100Mbps Down 200Mbps UP 

more info about the server location, client location.... 

Peering might be the answer ! 

regards, 
************************************************ 
Fierascu Vlad 
[ mailto:mythnick@gmail.com | mythnick@gmail.com ] 
[ http://www.mythnick.com/ | www.mythnick.com ] 


În mie., 11 dec. 2019 la 09:15, <cristian.c@istream.today> a scris: 





Hello, 



I have installed Wireguard on multiple location, servers, on each of this server I have 1Gbps link, my problem is that I’m not able to get more that ~100-120Mbps for download and ~200Mbps Upload, any idea why? 



As a server I use CentOS 7 as for “client” I use Windows 10 with latest Wireguard client.. 



Thank you in advance, 

Cristian 


_______________________________________________ 
WireGuard mailing list 
[ mailto:WireGuard@lists.zx2c4.com | WireGuard@lists.zx2c4.com ] 
[ https://lists.zx2c4.com/mailman/listinfo/wireguard | https://lists.zx2c4.com/mailman/listinfo/wireguard ] 




_______________________________________________ 
WireGuard mailing list 
WireGuard@lists.zx2c4.com 
https://lists.zx2c4.com/mailman/listinfo/wireguard 

[-- Attachment #1.2: Type: text/html, Size: 4649 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2020-02-11 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11  7:14 Limited speed 100Mbps Down 200Mbps UP cristian.c
2019-12-11 10:09 ` Fierascu Vlad
2020-02-11 14:29   ` Christophe Vanlancker [this message]

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=1374975524.57662.1581431380684.JavaMail.zimbra@inuits.eu \
    --to=carroarmato0@inuits.eu \
    --cc=mythnick@gmail.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).