Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nitinder Mohan <mohan@in.tum.de>
To: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Comprehensive Measurement Study on Starlink Performance Published
Date: Mon, 26 Feb 2024 18:12:53 +0000	[thread overview]
Message-ID: <etPan.65dcd4b4.593a6eed.2c4@in.tum.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]

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/

[-- Attachment #2: Type: text/html, Size: 3397 bytes --]

             reply	other threads:[~2024-02-26 18:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 18:12 Nitinder Mohan [this message]
2024-02-26 19:49 ` J Pan
2024-02-26 19:53 ` Dave Taht
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=etPan.65dcd4b4.593a6eed.2c4@in.tum.de \
    --to=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