Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>
Cc: Stuart Cheshire <cheshire@apple.com>,
	starlink@lists.bufferbloat.net,
	 "David P. Reed" <dpreed@deepplum.com>
Subject: Re: [Starlink] FQ_Codel
Date: Wed, 8 Jun 2022 18:11:14 -0700	[thread overview]
Message-ID: <CAA93jw55mkFC9p0StxnjKomWp=W5=tOpx8Vtn3Vuu2eVYZ_CKA@mail.gmail.com> (raw)
In-Reply-To: <60o9p77-4q39-nnr8-0n6-72q11s84444n@ynat.uz>

On Wed, Jun 8, 2022 at 5:21 PM David Lang <david@lang.hm> wrote:
>
> multiple access points, good. Mesh can make the problem worse.
>
> The combination of hidden transmitters (station in the middle can hear stations
> on both ends, but they can't hear each other and so step on each other) and just
> more airtime needed ro relay the messages as there are more hops can make the
> congestion worse (however, it is possible that higher data rates could make the
> transmissions shorter, but since the inter-aggregate gaps and per-aggregate
> headers are fixed at a low data rate, I doubt that it works that way in
> practice)
>
> but get a few additional APs hooked together via wires, and you have a clear win
> that scales very well. It's what we do at the Scale conf with 100+ APs to
> support 3k+ geeks.

Is there a physical scale conference this year? (It's in LA and a lot
of space/film folk go there)

For those that don't know, david lang has been putting together the
fq_codeled APs there for what? 8 years now? Conference feedback on the
wifi has generally been uniformly positive.

What APs do you use now?

> David Lang
>
> On Wed, 8 Jun 2022, Stuart Cheshire wrote:
>
> > On 8 Jun 2022, at 12:12, warren ponder <wponder11@gmail.com> wrote:
> >
> >> So this is really helpful. Is it fair to say then that end users with SQM and fq_codel on a Starlink connection should essentially not turn on SQM.and.just leave it off?
> >
> > My advice is that people should have SQM (e.g., fq_codel) enabled anywhere it is available. For devices that aren’t the bottleneck hop on a path it won’t make any difference, but it won’t hurt. And if the network topology is such that it does become the bottleneck hop, even briefly, SQM will avoid having a big queue build up there.
> >
> > One example is Wi-Fi. If you have 50Mb/s Internet service and 802.11ac Wi-Fi in the house, your Wi-Fi is unlikely to be the bottleneck. But if you walk out to the garden and the Wi-Fi rate drops to 40Mb/s, then suddenly bufferbloat in the AP can bite you, leading to bi-modal network usability, that abruptly falls off a cliff the moment your Wi-Fi rate drops below your Internet service rate. I think this is a large part of the reason behind the enthusiasm these days for “mesh” Wi-Fi systems -- you need to blanket your home with sufficient density of Wi-Fi access points to ensure that they never become the bottleneck hop and expose their incompetent queue management. If you get 11Mb/s in the garden that should be plenty to stream music, but throw in some egregious bufferbloat and a perfectly good 11Mb/s rate becomes unusably bad. Ironically, if you pay more for faster Internet service then the problem gets worse, not better, because the effective usable range of your bufferbloate
>  d Wi-Fi access points shrinks as the rate coming into the house goes up.
> >
> > Stuart Cheshire
> >
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/starlink_______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink



-- 
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC

  reply	other threads:[~2022-06-09  1:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.63.1654706837.1281.starlink@lists.bufferbloat.net>
2022-06-08 18:47 ` David P. Reed
2022-06-08 19:12   ` warren ponder
2022-06-08 20:49     ` David P. Reed
2022-06-08 21:30       ` Dave Taht
2022-06-09  8:58       ` Sebastian Moeller
2022-06-09  0:12     ` Stuart Cheshire
2022-06-09  0:21       ` David Lang
2022-06-09  1:11         ` Dave Taht [this message]
2022-06-09  2:01           ` David Lang
2022-06-09  8:50   ` Sebastian Moeller
2022-06-06 16:20 Warren Ponder
2022-06-08 16:47 ` Dave Taht

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/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw55mkFC9p0StxnjKomWp=W5=tOpx8Vtn3Vuu2eVYZ_CKA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cheshire@apple.com \
    --cc=david@lang.hm \
    --cc=dpreed@deepplum.com \
    --cc=starlink@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