From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] some sqm and cpu performance numbers for a variety of devices
Date: Sat, 28 Mar 2020 15:05:26 -0700 [thread overview]
Message-ID: <CALQXh-Pje=4fitrW489t62ppPgB9Jzd6d2Nx9PraW32N2s4NuQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4sBvvHuOO_UKhXOxuRvQqaEA-Dbn8f4-2Fac7ppB2ypQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
Thanks for the H/T, Dave!
I keep seeing bufferbloat in userspace proxies and tunnels, and think that
the world would benefit greatly from aqm library for applications to use in
order to keep latency under control. Especially if work like encryption is
being done and the results thrown away due to massive tail drops and the
like (or "real-time" video streams that need to throw away a bunch of
received packets in order to catch back up the proper e2e latency.
(no I'm not volunteering at this time, nor am I obliquely asking anyone
else to...)
On Sat, Mar 28, 2020 at 10:40 AM Dave Taht <dave.taht@gmail.com> wrote:
>
> 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
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2122 bytes --]
prev parent reply other threads:[~2020-03-28 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 17:39 [Cerowrt-devel] " Dave Taht
2020-03-28 22:05 ` Aaron Wood [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
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='CALQXh-Pje=4fitrW489t62ppPgB9Jzd6d2Nx9PraW32N2s4NuQ@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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