Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sascha Meinrath <meinrath@gmail.com>
To: Hesham ElBakoury <helbakoury@gmail.com>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	5grm-satellite@ieee.org
Subject: Re: [Starlink] Starlink in Northern Europe: A New Look at Stationary and In-motion Performance
Date: Thu, 27 Feb 2025 14:18:53 -0000	[thread overview]
Message-ID: <32b6f637-8793-417b-b8b9-a52b5da09dfd@thexlab.org> (raw)
In-Reply-To: <CAFvDQ9r323VwjjEb0Z7zoRKLF6g3p7fVBXw2HdpRWnvZ3uz2qA@mail.gmail.com>

Hi Hesham,

I've downloaded your paper to read when I get a moment; but could you provide 
the topline results for those of us who are interested to hear what you found?

--Sascha

On 2/27/25 00:00, Hesham ElBakoury via Starlink wrote:
> This paper [1] This paper evaluates the Flat High Performance (FHP) terminal's 
> performance in Finland, Northern Europe.
> 
> *_Abstract_*
> "Starlink has introduced the Flat High Performance (FHP) terminal, specifically 
> designed to support the vehicles and the vessels in motion as well as the high- 
> demand stationary users. The research on FHP terminal throughput analysis 
> remains limited, only a few existing studies evaluate FHP, focusing on the 
> limited parameters and scenarios. This paper evaluates the FHP terminal's 
> performance in Finland, Northern Europe. We examine round-trip time (RTT), 
> uplink, and downlink throughput for both stationary and in-motion use. We 
> measure network efficiency across six geographically diverse servers and get 
> insights of network routing strategies. Our results show that Starlink provides 
> high-speed, low-RTT connectivity, however, the throughput experiences 
> fluctuations with slight degradation when in motion. Additionally, we compare 
> Starlink and terrestrial network RTT and possible routing paths."
> 
> Hesham
> [1] https://arxiv.org/abs/2502.15552 <https://arxiv.org/abs/2502.15552>
> 
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

-- 
Sascha Meinrath
Director, X-Lab
Palmer Chair in Telecommunications
Penn State University

  reply	other threads:[~2025-02-27 14:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27  5:00 Hesham ElBakoury
2025-02-27 14:18 ` Sascha Meinrath [this message]
2025-02-27 14:36 ` Craig Polk
2025-02-27 15:04   ` Hesham ElBakoury
2025-02-27 21:02     ` Ulrich Speidel
2025-02-28  3:40       ` Daniel AJ Sokolov
2025-02-28  4:22         ` Ulrich Speidel
2025-02-28  4:57           ` Daniel AJ Sokolov

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=32b6f637-8793-417b-b8b9-a52b5da09dfd@thexlab.org \
    --to=meinrath@gmail.com \
    --cc=5grm-satellite@ieee.org \
    --cc=helbakoury@gmail.com \
    --cc=sascha@thexlab.org \
    --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