From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] A Transport Protocol's View of Starlink
Date: Wed, 22 May 2024 11:55:41 -0700 [thread overview]
Message-ID: <258721b6-efdc-472c-b606-3192b2551bc3@sewingwitch.com> (raw)
In-Reply-To: <4223FB1D3EC8265F9E30D997@[192.168.11.128]>
The Register came out with this summary today:
https://www.theregister.com/2024/05/22/starlink_tcp_performance_evaluation/
Excerpt:
> Using PING, he found "minimum latency changes regularly every 15
> seconds" and surmised "It appears that this change correlates to the
> Starlink user's terminal being assigned to a different satellite. That
> implies that the user equipment 'tracks' each satellite for a
> 15-second interval, which corresponds to a tracking angle of 11
> degrees of arc."
>
> During those handovers, Huston observed some packet loss – and a
> significant increase in latency. "The worst case in this data set is a
> shift from 30ms to 80ms," he wrote. Further: "Within each 15-second
> satellite tracking interval, the latency variation is relatively high.
> The average variation of jitter between successive RTT intervals is
> 6.7ms. The latency spikes at handover impose an additional 30ms to
> 50ms indicating the presence of deep buffers in the system to
> accommodate the transient issues associated with satellite handover."
>
> Overall, Huston believes Starlink has "a very high jitter rate, a
> packet drop rate of around one percent to two percent that is
> unrelated to network congestion, and a latency profile that jumps
> regularly every 15 seconds."
[No need to cc me in replies, I'll read them on the mailiing list.]
prev parent reply other threads:[~2024-05-22 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 13:16 Kenneth Porter
2024-05-22 15:59 ` Stephen Hemminger
2024-05-22 16:03 ` Sebastian Moeller
2024-05-22 18:55 ` Kenneth Porter [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/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=258721b6-efdc-472c-b606-3192b2551bc3@sewingwitch.com \
--to=shiva@sewingwitch.com \
--cc=bloat@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