General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Matt Mathis <mattmathis@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] starlink bloat in review
Date: Sat, 15 May 2021 15:59:58 -0700	[thread overview]
Message-ID: <CAH56bmCLiwDYZqYm0dm31NtqAKXGhh8w43hunpXFssqQyCd1og@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6-R-tQrBeXDjEr-OO+E6NNLK4yB1n5DXhiHZauf-zaMQ@mail.gmail.com>

I don't understand: starlink doesn't terminate the TCP connection,
does it?   Or are you referring to YT's BBR adequately addressing
Starlinks variable RTT?   "Adequately" is probably the operative word.
It is not too hard to imagine what goes wrong with BBR if the actual
path length varies, and on an underloaded network, you may not be able
to even detect the symptoms.

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

We must not tolerate intolerance;
       however our response must be carefully measured:
            too strong would be hypocritical and risks spiraling out of control;
            too weak risks being mistaken for tacit approval.

On Sat, May 15, 2021 at 3:08 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> "In my week of testing, Starlink was perfectly fine for anything that
> buffers — I was able to stream Netflix and Disney Plus in 4K and jump
> around YouTube videos without significant issues — but doing something
> faster-paced, like quickly scrolling through TikTok videos, would run
> into delays."
>
> https://www.theverge.com/22435030/starlink-satellite-internet-spacex-review
>
> To me that "jump around youtube" is telling me that BBR is working on starlink.
>
> Also of interest in this article was links to their open source
> copyrights, which confirm linux 4.9 is in use.
>
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

  reply	other threads:[~2021-05-15 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 22:07 Dave Taht
2021-05-15 22:59 ` Matt Mathis [this message]
2021-05-17 15:08   ` Neal Cardwell
2021-05-17 15:46     ` Jim Gettys
2021-05-17 15:49     ` [Bloat] [Starlink] " Nathan Owens

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

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

  git send-email \
    --in-reply-to=CAH56bmCLiwDYZqYm0dm31NtqAKXGhh8w43hunpXFssqQyCd1og@mail.gmail.com \
    --to=mattmathis@google.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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