Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: "the keyboard of geoff goodfellow" <geoff@iconia.com>,
	Starlink <Starlink@lists.bufferbloat.net>,
	=?UTF-8?Q?Network_Neutrality_is_back=21_Let=C2=B4s_make_the_technical_aspect?=
	   =?UTF-8?Q?s_heard_this_time=21?=
	<nnagain@lists.bufferbloat.net>
Subject: Re: [Starlink] SpaceX: "IMPROVING STARLINK’S  LATENCY" (via Nathan Owens)
Date: Sun, 10 Mar 2024 13:41:19 -0400	[thread overview]
Message-ID: <14463.1710092479@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw7CLf9xvuKBjhaC12RzE_4iYGqpKrgJeaTdwDPXeQtU9w@mail.gmail.com>


Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
    > and for that matter, cable, and fiber, will also get on the stick,
    > finally. Maybe someone in the press will explain bufferbloat. Who
    > knows what the coming days hold!?

I am imaging a 2005-era Apple iPod shadow dancing ad... one with high
buffers (low RPM), and one with low (high RPM).

What do you think Stuart?


  parent reply	other threads:[~2024-03-10 17:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 19:40 the keyboard of geoff goodfellow
2024-03-08 19:50 ` J Pan
2024-03-08 20:09   ` the keyboard of geoff goodfellow
2024-03-08 20:25     ` Frantisek Borsik
2024-03-08 20:31     ` Dave Taht
2024-03-08 23:44       ` [Starlink] When Flows Collide? Jack Haverty
2024-03-09  2:57         ` [Starlink] [NNagain] " David Lang
2024-03-09 19:08           ` Jack Haverty
2024-03-09 19:45             ` rjmcmahon
2024-03-09 20:08             ` David Lang
2024-03-10 17:41       ` Michael Richardson [this message]
2024-03-08 20:30   ` [Starlink] [NNagain] SpaceX: "IMPROVING STARLINK’S LATENCY" (via Nathan Owens) rjmcmahon

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=14463.1710092479@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=Starlink@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=geoff@iconia.com \
    --cc=nnagain@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