Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Nitinder Mohan <mohan@in.tum.de>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Comprehensive Measurement Study on Starlink Performance Published
Date: Mon, 26 Feb 2024 14:53:37 -0500	[thread overview]
Message-ID: <CAA93jw6va_hKHe8nHfqK5KkJUOCe8C50rGT__ArB5Ek-Wtqtcw@mail.gmail.com> (raw)
In-Reply-To: <etPan.65dcd4b4.593a6eed.2c4@in.tum.de>

While nobody reads footnotes much, and I would really like you to cite
this as the instigator of a lot of research into this area, also:

https://www.youtube.com/watch?v=c9gLo6Xrwgw

because of all that rage and frustration is what keyed off 3 years of
effort. Think of it as newton noticed an apple, falling from a tree.

This is also a good cite, in terms of flavoring your methods to a
level that I can tolerate.

https://conferences.sigcomm.org/sigcomm/2014/doc/slides/137.pdf

I will go through more of the footnotes when I have time, starting
with the first.

It is also plausible that Starlink employs active queue management (AQM)
techniques [1] to moderate uplink latencies under congestion.

Um... it does not look like it to my eye. Just a overly short packet
FIFO. I haven´t torn it apart lately however. You can easily tell the
difference in packet loss behaviors by tearing apart rrul packet
captures.

On Mon, Feb 26, 2024 at 1:13 PM Nitinder Mohan via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> Hi folks,
>
> Our comprehensive multifaceted measurement study looking at Starlink global and last-mile performance is now available online: https://arxiv.org/abs/2310.09242.
>
> TL;DR: See the summary in this nice teaser video we made: https://youtu.be/WtE3MoK8J80
>
> We looked at several third-party measurement sources (M-Lab, RIPE Atlas) and performed our own measurements over multiple Starlink dishes to uncover the following:
>
> 1. How different is Starlink network performance globally? How do ground station and PoP availability impact performance?
> 2. How much latency is consumed by the satellite part of the link?
> 3. Is Starlink connection affected by bufferbloat?
> 4. Are satellite handovers the root-cause of Starlink 15-sec reconfigurations?
> 5. How good is Starlink compared to terrestrial cellular networks for real-time applications, specifically Cloud Gaming and Zoom.
>
> The study has been accepted and will appear in ACM The Web Conference 2024 (WWW), which is a flagship venue that has historically housed several pioneering works central to Internet success.
>
> Feel free to let me know if you have any questions related to the work.
>
> P.S. We also thanked this mailing list in our paper for providing us several key insights and inquisitive discussions :)
>
> Thanks and Regards
>
> Nitinder Mohan
> Technical University Munich (TUM)
> https://www.nitindermohan.com/
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink



-- 
https://blog.cerowrt.org/post/2024_predictions/
Dave Täht CSO, LibreQos

  parent reply	other threads:[~2024-02-26 19:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 18:12 Nitinder Mohan
2024-02-26 19:49 ` J Pan
2024-02-26 19:53 ` Dave Taht [this message]
2024-02-26 22:19 ` Ulrich Speidel
2024-02-26 23:19   ` David Lang
2024-02-27  0:16     ` Ulrich Speidel
2024-02-27  1:13       ` David Lang
2024-02-27  2:33         ` Ulrich Speidel
2024-02-27  6:21           ` David Lang
2024-02-27  7:31             ` [Starlink] starlink business peering Dave Taht
2024-02-27  7:38               ` David Lang
2024-02-27  7:42               ` Dave Taht
2024-02-27  8:08                 ` David Lang
2024-02-27 11:15             ` [Starlink] Comprehensive Measurement Study on Starlink Performance Published Ulrich Speidel
2024-02-27 14:02               ` Nitinder Mohan

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=CAA93jw6va_hKHe8nHfqK5KkJUOCe8C50rGT__ArB5Ek-Wtqtcw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=mohan@in.tum.de \
    --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