Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'Dave Taht'" <dave.taht@gmail.com>,
	"'libreqos'" <libreqos@lists.bufferbloat.net>,
	"'Rpm'" <rpm@lists.bufferbloat.net>
Cc: "'Sam Crawford'" <sam@samknows.com>
Subject: Re: [LibreQoS] [Starlink] NZ latest latency report
Date: Wed, 5 Jul 2023 17:17:12 -0700	[thread overview]
Message-ID: <6C0AE2724B354B1E87B55C42C159CC27@SRA6> (raw)
In-Reply-To: <CAA93jw6A9g4F8z5dUTnv_4oj2wRNWmEmxeRPX=DfDGaCF3jSwg@mail.gmail.com>

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

I’m not the expert in the room, however I find the report lacking in one
very important area.  All these results on latencies, speed, etc., are
categorized based on users “first mile access” technology, leqding the
reader to believe the sole source of these numbrs is the “first mile” which
of course it is not.  They do not address the as important issues of the
rest of what’s between “end-2-end”.  Take a look at the gaming latency
results, and you see games hosted in America have very high latencies for
users in New Zealand … duhhhhhh!  This can’t be news.  

 

While not trivial by any means, what could/should be done to make these data
more useful for consumers is to figure out the effect of everything past the
“first mile/first hop” and break it out separately.  That way, a (moderately
intelligent) user could make a reasonably informed cost-benefit analysis on
which combination of first mile technology and back-end service provider to
choose, assuming there were service providers that offered a choice of
“first-mile’ access, or backhaul providers that served a variety of “first
mile” providers.  Guess we’re a few years away from that :-)

 

RR

 

-----Original Message-----
From: Starlink [mailto:starlink-bounces@lists.bufferbloat.net] On Behalf Of
Dave Taht via Starlink
Sent: Wednesday, July 5, 2023 6:08 AM
To: libreqos; Rpm; Dave Taht via Starlink
Cc: Sam Crawford
Subject: [Starlink] NZ latest latency report

 

I do wish that it broke it out by provider, and recommended somehow to

those suffering still, install a better device... VDSL can be made

vastly more tolerable. Otherwise pretty good, and brings in

starlink...

 

https://comcom.govt.nz/__data/assets/pdf_file/0016/320326/MBNZ-Autumn-Report
-28-June-2023.pdf

 

To pick on samknows a little bit, I think the test does not run long

enough, and should be pulling from higher than what appears to be the

75th percentile.

 

 

 

-- 

Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/

Dave Täht CSO, LibreQos

_______________________________________________

Starlink mailing list

Starlink@lists.bufferbloat.net

https://lists.bufferbloat.net/listinfo/starlink


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

  parent reply	other threads:[~2023-07-06  0:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 13:08 [LibreQoS] " Dave Taht
2023-07-05 21:17 ` [LibreQoS] [Starlink] " Ulrich Speidel
2023-07-06  0:17 ` Dick Roy [this message]
2023-08-17 15:29   ` dan

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

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

  git send-email \
    --in-reply-to=6C0AE2724B354B1E87B55C42C159CC27@SRA6 \
    --to=dickroy@alum.mit.edu \
    --cc=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=rpm@lists.bufferbloat.net \
    --cc=sam@samknows.com \
    /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