wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Илья Шипицин" <chipitsine@gmail.com>
To: Lev Stipakov <lstipakov@gmail.com>
Cc: openvpn-devel <openvpn-devel@lists.sourceforge.net>,
	wireguard@lists.zx2c4.com
Subject: Re: [Openvpn-devel] Wintun performance results
Date: Wed, 15 May 2019 19:49:39 +0500	[thread overview]
Message-ID: <CAFHpkQFVpN-+Uoc6QsLmD8hjwEC7Ba1Q2SP4SuS_EMu_PT=3nw@mail.gmail.com> (raw)
In-Reply-To: <CAGyAFMV=HvOYDRSB7eRpBDp-47wX2vie8JPgp48in1fH+eXn=A@mail.gmail.com>


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

it will most probably get lost in mailing list.
can we add it to https://openvpn.net website ? something like "performance
testing" with full configs provided ?

ср, 15 мая 2019 г. в 18:49, Lev Stipakov <lstipakov@gmail.com>:

> Hi guys,
>
> I made openvpn3 (required changes will be incorporated into main branch at
> some point) work with wintun and did performance testing in AWS.
>
> Client:    c5.xlarge, Windows Server 2016, patched openvpn3 test client
> and OpenVPN Connect 2.7.1.103 (uses tap-windows6, based on openvpn3).
>
> Server:  c5.xlarge, Ubuntu 18.04, openvpn 2.4.4
>
> Client and server instances are in the same VPC and placement group.
>
> iPerf3 running on server:
>
> > iperf3 -s -B 0.0.0.0 -V
>
> iPerf3 running on client:
>
> > iperf3 -c 10.8.0.1 -V (server VPN address)
> > iperf3 -c 10.0.0.18 -V (server VPC address)
>
> Results:
>
> - no vpn
>
> [ ID] Interval           Transfer     Bandwidth
> [  4]   0.00-10.00  sec  8.67 GBytes  7.45
> Gbits/sec                  sender
> [  4]   0.00-10.00  sec  8.67 GBytes  7.45
> Gbits/sec                  receiver
> CPU Utilization: local/sender 61.4% (5.6%u/55.8%s), remote/receiver 33.9%
> (1.7%u/32.2%s)
>
> - tap-windows6
>
> [ ID] Interval           Transfer     Bandwidth
> [  4]   0.00-10.00  sec   404 MBytes   339
> Mbits/sec                  sender
> [  4]   0.00-10.00  sec   404 MBytes   339
> Mbits/sec                  receiver
> CPU Utilization: local/sender 4.6% (0.3%u/4.3%s), remote/receiver 21.4%
> (2.2%u/19.2%s)
>
> - wintun
>
> [ ID] Interval           Transfer     Bandwidth
> [  4]   0.00-10.00  sec   536 MBytes   449
> Mbits/sec                  sender
> [  4]   0.00-10.00  sec   536 MBytes   449
> Mbits/sec                  receiver
> CPU Utilization: local/sender 2.9% (0.1%u/2.8%s), remote/receiver 10.1%
> (0.7%u/9.3%s)
>
> As you see, wintun performs 30% better comparison to tap-windows6 and
> incurs significantly less CPU usage.
>
> --
> -Lev
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>

[-- Attachment #1.2: Type: text/html, Size: 3433 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:[~2019-05-18 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 13:48 Wintun performance results Lev Stipakov
2019-05-15 14:49 ` Илья Шипицин [this message]
2019-05-15 15:31   ` [Openvpn-devel] " Lev Stipakov
2019-05-15 17:32   ` David Sommerseth
2019-05-16 10:14     ` Jan Just Keijser
2019-05-16 11:59       ` Lev Stipakov
2019-05-20 12:03         ` Lev Stipakov
2019-06-03 18:04           ` Lev Stipakov
2019-06-14 15:56             ` Lev Stipakov
2019-05-16 11:44 ` Jason A. Donenfeld

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='CAFHpkQFVpN-+Uoc6QsLmD8hjwEC7Ba1Q2SP4SuS_EMu_PT=3nw@mail.gmail.com' \
    --to=chipitsine@gmail.com \
    --cc=lstipakov@gmail.com \
    --cc=openvpn-devel@lists.sourceforge.net \
    --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).