From: Dave Taht <dave.taht@gmail.com>
To: Nils Andreas Svee <me@lochnair.net>
Cc: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
"Toke Høiland-Jørgensen via Cake" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Fwd: [Galene] Dave on bufferbloat and jitter at 8pm CET Tuesday 23
Date: Tue, 23 Feb 2021 17:14:31 -0800 [thread overview]
Message-ID: <CAA93jw4-wspLUfL_ZJW1BN0uWaEqZGMOVnD3Z1jgrKOJ_r8xLw@mail.gmail.com> (raw)
In-Reply-To: <1e41ddf7-cd08-4fec-b31a-3021f8111dc6@www.fastmail.com>
wow, that is (predictably) miserable, even with cake. The only
solution that is going to
work is to somehow actively monitor your link quality and adjust cake
to suit. Or we can start trying to use kathie's passive ping tools.
On Tue, Feb 23, 2021 at 1:30 PM Nils Andreas Svee <me@lochnair.net> wrote:
>
> Thanks for the talk Dave and it was nice meeting you all!
>
> Never really did much in the way of Flent tests after moving from ADSL to Telenor's "wireless broadband" aka. 4G. So I ran some after leaving the meeting, with CAKE on or off, and let me tell you - it's terrifying, 4G sucks indeed., not as bad as DSL without SQM mind, but still
>
> Avg. latency without SQM at some points close to 800 ms or above. Had to sacrifice a lot of bandwidth to get it to sane levels when doing RRUL tests.
>
> Dumped all the files over here: https://dl.lochnair.net/Bufferbloat/Tests/
> Oh btw I promise I'll try to not break things when you need to access something on that box again Dave...
>
> Best Regards
> Nils
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next prev parent reply other threads:[~2021-02-24 1:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874ki24ref.wl-jch@irif.fr>
2021-02-23 17:46 ` Dave Taht
2021-02-23 21:30 ` Nils Andreas Svee
2021-02-24 1:14 ` Dave Taht [this message]
2021-02-24 1:29 ` [Cake] [Bloat] " Stephen Hemminger
2021-02-24 10:51 ` Toke Høiland-Jørgensen
2021-02-24 22:49 ` Nils Andreas Svee
2021-02-24 23:27 ` Toke Høiland-Jørgensen
2021-02-24 23:35 ` Nils Andreas Svee
2021-02-25 10:30 ` Toke Høiland-Jørgensen
2021-02-26 0:32 ` Nils Andreas Svee
2021-02-26 11:47 ` Toke Høiland-Jørgensen
2021-02-26 15:27 ` Nils Andreas Svee
2021-02-26 16:59 ` Bless, Roland (TM)
2021-02-26 17:14 ` Sebastian Moeller
2021-02-26 17:50 ` Bless, Roland (TM)
2021-02-24 15:19 ` Taraldsen Erik
2021-02-24 16:11 ` Toke Høiland-Jørgensen
2021-02-24 18:43 ` [Cake] [Make-wifi-fast] " Jonathan Morton
2021-02-24 23:27 ` [Cake] " Nils Andreas Svee
2021-02-25 8:18 ` Taraldsen Erik
2021-02-26 0:19 ` Nils Andreas Svee
2021-02-26 7:26 ` Taraldsen Erik
2021-02-26 12:26 ` Toke Høiland-Jørgensen
2021-02-26 14:25 ` Nils Andreas Svee
2021-02-26 15:08 ` Taraldsen Erik
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4-wspLUfL_ZJW1BN0uWaEqZGMOVnD3Z1jgrKOJ_r8xLw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=me@lochnair.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