From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: [Cerowrt-devel] some sqm and cpu performance numbers for a variety of devices
Date: Sat, 28 Mar 2020 10:39:54 -0700 [thread overview]
Message-ID: <CAA93jw4sBvvHuOO_UKhXOxuRvQqaEA-Dbn8f4-2Fac7ppB2ypQ@mail.gmail.com> (raw)
https://forum.openwrt.org/t/comparative-throughput-testing-including-nat-sqm-wireguard-and-openvpn/44724/44
(H/T to aaron wood)
The post persistently points out that openvpn tends to optimize for
one direction only. This is in part due to the large internal buffer
in it. I'd longed to fq it internally at one point. Similarly,
wireguard suffers, but not as bad. Fixing that is easier.
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next reply other threads:[~2020-03-28 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 17:39 Dave Taht [this message]
2020-03-28 22:05 ` [Cerowrt-devel] [Bloat] " Aaron Wood
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4sBvvHuOO_UKhXOxuRvQqaEA-Dbn8f4-2Fac7ppB2ypQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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