General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] FW: [Dewayne-Net] Ajit Pai caves to SpaceX but is still skeptical of Musk's latency claims
Date: Thu, 11 Jun 2020 19:14:57 +0300	[thread overview]
Message-ID: <A4FF6DF6-75AA-4D19-8C3C-F5AFC573B888@gmail.com> (raw)
In-Reply-To: <1591891396.41838464@apps.rackspace.com>

> On 11 Jun, 2020, at 7:03 pm, David P. Reed <dpreed@deepplum.com> wrote:
> 
> So, what do you think the latency (including bloat in the satellites) will be? My guess is > 2000 msec, based on the experience with Apple on ATT Wireless back when it was rolled out (at 10 am, in each of 5 cities I tested, repeatedly with smokeping, for 24 hour periods, the ATT Wireless access network experienced ping time grew to 2000 msec., and then to 4000 by mid day - true lag-under-load, with absolutely zero lost packets!)
>  
> I get that SpaceX is predicting low latency by estimating physical distance and perfect routing in their LEO constellation. Possibly it is feasible to achieve this if there is zero load over a fixed path. But networks aren't physical, though hardware designers seem to think they are.
>  
> Anyone know ANY reason to expect better from Musk's clown car parade?

Speaking strictly from a theoretical perspective, I don't see any reason why they shouldn't be able to offer latency that is "normally" below 100ms (to a regional PoP, not between two arbitrary points on the globe).  The satellites will be much closer to any given ground station than a GEO satellite, the latter typically adding 500ms to the path due mostly to physical distance.  All that is needed is to keep queue delays reasonably under control, and there's any number of AQMs that can help with that.  Clearly ATT Wireless did not perform any bufferbloat mitigation at all.

I have no insight or visibility into anything they're *actually* doing, though.  Can anyone dig up anything about that?

 - Jonathan Morton


  reply	other threads:[~2020-06-11 16:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 16:03 David P. Reed
2020-06-11 16:14 ` Jonathan Morton [this message]
2020-06-11 18:46   ` David P. Reed
2020-06-11 18:56     ` David Lang
2020-06-11 19:16       ` David P. Reed
2020-06-11 19:28         ` David Lang
2020-06-12 15:39           ` Michael Richardson
2020-06-13  5:43             ` David Lang
2020-06-13 18:41               ` David P. Reed
2020-06-14  0:03                 ` David Lang
2020-06-14  0:36               ` Michael Richardson
2020-06-14  1:17                 ` David Lang
2020-06-14 15:40                   ` David P. Reed
2020-06-14 15:57                     ` Michael Richardson
2020-06-14 21:04                       ` David P. Reed
2020-06-14 23:13                         ` Michael Richardson
2020-06-12 15:30     ` Michael Richardson
2020-06-12 19:50       ` David P. Reed
2020-06-13 21:15         ` Michael Richardson
2020-06-13 23:02           ` Jonathan Morton
2020-06-14  0:06           ` David Lang
2020-06-14 11:23   ` Roland Bless

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

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

  git send-email \
    --in-reply-to=A4FF6DF6-75AA-4D19-8C3C-F5AFC573B888@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=dpreed@deepplum.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