revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net, Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] It's still the latency, starlink!
Date: Sat, 16 Jul 2022 21:23:06 -0700	[thread overview]
Message-ID: <CAA93jw4xOnrFu0qBRWq9Sfq8OqsQVgmxrCNsi+SM1qiH_OEt=A@mail.gmail.com> (raw)

there's three "lovely" new speedtest results here, showing nearly 5sec
of uplink latency under load.

If only more folk would realize it's not the bandwidth, but the working latency.

https://www.pcmag.com/news/starlinks-massive-growth-results-in-congestion-slow-speeds-for-some-users

-- 
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC

             reply	other threads:[~2022-07-17  4:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17  4:23 Dave Taht [this message]
2022-07-17  6:17 ` [Rpm] [Starlink] " Jeremy Austin
2022-07-17  7:31   ` Frantisek Borsik
2022-07-18 12:54     ` Mike Conlow

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

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

  git send-email \
    --in-reply-to='CAA93jw4xOnrFu0qBRWq9Sfq8OqsQVgmxrCNsi+SM1qiH_OEt=A@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=rpm@lists.bufferbloat.net \
    --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