From: Sergey <me@prok.pw>
To: wireguard@lists.zx2c4.com
Subject: WireGuard network perfomance
Date: Tue, 20 Dec 2016 04:48:51 +0700 [thread overview]
Message-ID: <1482184131.1467.9@mail.aur.rocks> (raw)
Hello guys.
First of all thanks for the WireGuard project: it really simple &
powerful and no more headaches with openvpn :)
My question about network perfomance, I tested network speed with
iperf3 and got these results:
Raw test (no WireGuard):
$ iperf3 -c PUBLIC_IP
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 98.1 MBytes 82.3 Mbits/sec 25
sender
[ 4] 0.00-10.00 sec 93.6 MBytes 78.5 Mbits/sec
receiver
So I got ~80 Mbits/sec
And WireGuard test:
$ iperf3 -c PRIVATE_IP
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 53.2 MBytes 44.7 Mbits/sec 1863
sender
[ 4] 0.00-10.00 sec 46.1 MBytes 38.7 Mbits/sec
receiver
And there is ~40 Mbits/sec, so half of original.
I missed something? Probably I need to configure something /etc?
btw what is "Retr" column in iperf? Why it so big with WireGuard?
Anyway that's good result for me, as openvpn can only give me something
~15 Mbits/sec.
Best regards, Sergey.
next reply other threads:[~2016-12-19 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 21:48 Sergey [this message]
2016-12-19 22:09 ` Jason A. Donenfeld
2016-12-19 22:11 ` Sergey
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=1482184131.1467.9@mail.aur.rocks \
--to=me@prok.pw \
--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).