Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Collier-Brown <dave.collier-Brown@indexexchange.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Sidebar to It’s the Latency, FCC: Measure it?
Date: Sun, 17 Mar 2024 12:17:11 -0400	[thread overview]
Message-ID: <e0f9affe-f205-4f01-9ff5-3dc93abc31ca@indexexchange.com> (raw)
In-Reply-To: <MN2PR16MB33916D0DB2568CCCE602D1B0F12E2@MN2PR16MB3391.namprd16.prod.outlook.com>

On 2024-03-17 11:47, Colin_Higbie via Starlink wrote:

> Fortunately, in our case, even high latency shouldn't be too terrible, but as you rightly point out, if there are many iterations, 1s minimum latency could yield a several second lag, which would be poor UX for almost any application. Since we're no longer testing for that on the premise that 1s minimum latency is no longer a common real-world scenario, it's possible those painful lags could creep into our system without our knowledge.

Does that suggest that you should have an easy way to see if you're
unexpectedly delivering a slow service? A tool that reports your RTT to
customers and an alert on it being high for a significant period might
be something all ISPs want, even ones like mine, who just want it to be
able to tell a customer "you don't have a network problem" (;-))

And the FCC might find the data illuminating

--dave

--
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
dave.collier-brown@indexexchange.com |              -- Mark Twain


CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory.

  reply	other threads:[~2024-03-17 16:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.11.1710518402.17089.starlink@lists.bufferbloat.net>
2024-03-15 18:32 ` [Starlink] It’s the Latency, FCC Colin  Higbie
2024-03-15 18:41   ` Colin_Higbie
2024-03-15 19:53     ` Spencer Sevilla
2024-03-15 20:31       ` Colin_Higbie
2024-03-16 17:18         ` Alexandre Petrescu
2024-03-16 17:21           ` Alexandre Petrescu
2024-03-16 17:36           ` Sebastian Moeller
2024-03-16 22:51             ` David Lang
2024-03-15 23:07       ` David Lang
2024-03-16 18:45         ` [Starlink] Itʼs " Colin_Higbie
2024-03-16 19:09           ` Sebastian Moeller
2024-03-16 19:26             ` Colin_Higbie
2024-03-16 19:45               ` Sebastian Moeller
2024-03-16 23:05           ` David Lang
2024-03-17 15:47             ` [Starlink] It’s " Colin_Higbie
2024-03-17 16:17               ` Dave Collier-Brown [this message]
2024-03-16 18:51         ` [Starlink] It?s " Gert Doering
2024-03-16 23:08           ` David Lang
2024-04-30  0:39   ` [Starlink] It’s " David Lang
2024-04-30  1:30     ` [Starlink] Itʼs " Colin_Higbie
2024-04-30  2:16       ` David Lang
     [not found] <mailman.2503.1710703654.1074.starlink@lists.bufferbloat.net>
2024-03-18 16:41 ` [Starlink] Sidebar to It’s the Latency, FCC: Measure it? Colin_Higbie
2024-03-18 16:49   ` Dave Taht
2024-03-18 19:32   ` David Lang
2024-03-18 19:52     ` Sebastian Moeller
2024-03-18 20:00       ` David Lang
2024-03-19 16:06         ` David Lang

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=e0f9affe-f205-4f01-9ff5-3dc93abc31ca@indexexchange.com \
    --to=dave.collier-brown@indexexchange.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