Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] [Bloat] "New analysis of Cloudflare Aggregated Internet Measurement (AIM) data from NetForecast, leveraging open Measurement Lab backend"
Date: Fri, 24 May 2024 14:22:41 +0200	[thread overview]
Message-ID: <80A2E78D-1E4B-4CCA-9759-9E2273257DD1@gmx.de> (raw)
In-Reply-To: <CAJUtOOjw93CcTQiDDz2iQ90zu48=TkYVLQ9L9=aq_2k-1Y9b_g@mail.gmail.com>

Figure 17 illustrates starlinks latency reduction effort pretty well.

I guess folks on this list already know, but still this implies that there might have been two stages in latency reduction so far (or I might be massively overinterpret the plotted curve ;) )

Regards & Thanks Jason & Frantisek
	Sebastian



> On 24. May 2024, at 13:41, Frantisek Borsik via Bloat <bloat@lists.bufferbloat.net> wrote:
> 
> https://www.netforecast.com/wp-content/uploads/NFR5150_NetForecast-ISP-Performance-Report-2024.pdf
> 
> Originally shared by Jason Livingood on Twitter/X:
> https://x.com/jlivingood/status/1793664523557286216
> His thread contains some additional reading.
> 
> All the best,
> 
> FrankFrantisek (Frank) Borsik
>  https://www.linkedin.com/in/frantisekborsik
> Signal, Telegram, WhatsApp: +421919416714 
> iMessage, mobile: +420775230885
> Skype: casioa5302ca
> frantisek.borsik@gmail.com
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


           reply	other threads:[~2024-05-24 12:22 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAJUtOOjw93CcTQiDDz2iQ90zu48=TkYVLQ9L9=aq_2k-1Y9b_g@mail.gmail.com>]

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=80A2E78D-1E4B-4CCA-9759-9E2273257DD1@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=frantisek.borsik@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