From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] a puzzling starlink uplink trace
Date: Thu, 31 Aug 2023 10:56:48 +0200 [thread overview]
Message-ID: <22b7ab5d-1dba-0d4b-eb9d-83e2e9ab57ea@gmail.com> (raw)
In-Reply-To: <CAA93jw46xmXX48bBWe0Rq3EBHRr6XtAEo==obsvFazdPQCmh6A@mail.gmail.com>
Le 30/08/2023 à 20:07, Dave Taht via Starlink a écrit :
> In the attached 5 minute plot from a few days ago (I can supply the
> flent.gz files if anyone wants them), I see a puzzling spike at T+155s
> to nearly 90ms of baseline latency, then down to 20ms.
20ms?
A latency of 20ms might come if these low altitude starlink sats (70km
or so) pass by there?
Or maybe I dont see quite well these sat altitudes.
Alex
> No degree of
> orbital mechanics can apply to this change, even factoring in an over
> the horizon connection, routing packets on the ground through LA to
> seattle, and back, or using a couple ISLs, can make this add up for
> me. A combination of all that, kind of does make sense.
>
> The trace otherwise shows the sawtooth pattern of a single tcp flow ,
> a loss (sometimes catastrophic) at every downward bandwidth change.
>
> An assumption I have long been making is the latency staircase effect
> (see T+170) forward is achieving the best encoding rate at the
> distance then seen, the distance growing and the encoding rate falling
> in distinct steps, with a fixed amount of buffering, until finally
> that sat starts falling out of range, and it choses another at T+240s.
>
> But jeeze, a 70ms baseline latency swing? What gives? I imagine
> somehow correlating this with a mpls enabled traceroute might begin to
> make some sense of it, correlated by orbital positions....
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-08-31 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 18:07 Dave Taht
2023-08-30 19:43 ` Sebastian Moeller
2023-08-31 13:42 ` Dave Taht
2023-08-31 14:31 ` Sebastian Moeller
2023-08-31 8:56 ` Alexandre Petrescu [this message]
2023-08-31 9:13 ` Alexandre Petrescu
2023-08-31 11:43 ` David Lang
2023-08-31 13:36 ` Dave Taht
2023-08-31 13:54 ` David Lang
2023-09-15 11:17 ` Alexandre Petrescu
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=22b7ab5d-1dba-0d4b-eb9d-83e2e9ab57ea@gmail.com \
--to=alexandre.petrescu@gmail.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