From: Jeremy Austin <jeremy@aterlo.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] It's still the latency, starlink!
Date: Sat, 16 Jul 2022 22:17:04 -0800 [thread overview]
Message-ID: <CACw=56+Jzmew=-ym0soVOiW4uS6RMhKhQ6_yd_Ag3ES3r6S5Qw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4xOnrFu0qBRWq9Sfq8OqsQVgmxrCNsi+SM1qiH_OEt=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
We will keep preaching it.
This also feeds into the frustration around the manipulation of the US
(FCC) federal definition of broadband. I care little about a 1000/500
connection with 2000 ms of latency under load; I’d much rather have a
100/20 that never exceeds 100 ms!
<sigh>
Jeremy
On Sat, Jul 16, 2022 at 8:23 PM Dave Taht via Starlink <
starlink@lists.bufferbloat.net> wrote:
> 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
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
[image: Company logo]
*Jeremy Austin*
Sr. Product Manager
*Preseem | Aterlo Networks*
Book a call: https://app.hubspot.com/meetings/jeremy548
1-833-773-7336 ext 718 *|* 1-907-803-5422
jeremy@aterlo.com
www.preseem.com
[image: facebook icon] [image: twitter icon] [image: linkedin icon] [image:
youtube icon]
[image: Ask us about our new features today!]
<https://preseem.com/2021/10/news-preseem-wins-wispa-service-of-the-year-award-2021/>
[-- Attachment #2: Type: text/html, Size: 4815 bytes --]
prev parent reply other threads:[~2022-07-17 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 4:23 Dave Taht
2022-07-17 6:17 ` Jeremy Austin [this message]
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='CACw=56+Jzmew=-ym0soVOiW4uS6RMhKhQ6_yd_Ag3ES3r6S5Qw@mail.gmail.com' \
--to=jeremy@aterlo.com \
--cc=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