From: Dave Taht <dave.taht@gmail.com>
To: tom@evslin.com
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
starlink@lists.bufferbloat.net
Subject: Re: [Starlink] recent starlink rrul test result
Date: Thu, 3 Mar 2022 10:03:51 -0500 [thread overview]
Message-ID: <CAA93jw4mvyFWTW_i8Sg4freBPLKzPCYRc4B+Mmj-PX5kHC9b2w@mail.gmail.com> (raw)
In-Reply-To: <234101d82f0d$56e94c80$04bbe580$@evslin.com>
There appears only to be variability in the baseline bandwidth of the
link on that 15sec interval. The rest is just the interactions between
our standard congestion control algorithms (cubic in this case), and a
fixed length per packet FIFO queue.
A debloated link would have 10-20ms of variability no matter the
observed bandwidth, in the third panel of this rrul plot.
The upload would have been much larger and flatter than it was in the
second panel, in part due to the fq - (and with sch_cake,
ack-filtering out much of the workload the download put on it) - see
https://blog.cerowrt.org/post/ack_filtering/
and the download bandwidth would have been about the same (across each
15s adjustment), and perhaps better as when we crack 250ms of delay in
either direction our protocols start to act up.
On Thu, Mar 3, 2022 at 9:45 AM <tom@evslin.com> wrote:
>
> Dave,
>
> How would you interpret from a bufferbloat PoV? Or is there too much other variability-induced noise to judge?
>
> Thankjs
>
> -----Original Message-----
> From: Starlink <starlink-bounces@lists.bufferbloat.net> On Behalf Of Dave Taht
> Sent: Thursday, March 3, 2022 9:36 AM
> To: Livingood, Jason <Jason_Livingood@comcast.com>
> Cc: starlink@lists.bufferbloat.net
> Subject: [Starlink] recent starlink rrul test result
>
> wildly variable bandwidth, adjusted at 15 sec intervals, induced latencies of 400ms, really terrible upload throughput relative to down.
>
> H/T David Lang for this data.
>
> On Thu, Mar 3, 2022 at 9:31 AM Livingood, Jason <Jason_Livingood@comcast.com> wrote:
> >
> > When folks experience sub-par video conferencing over Starlink, it'd be great to see working latency stats at that time - such as via the easy test at https://www.waveform.com/tools/bufferbloat.
> >
> > On 2/23/22, 09:38, "Starlink on behalf of Dave Taht" <starlink-bounces@lists.bufferbloat.net on behalf of dave.taht@gmail.com> wrote:
> >
> >
> > https://urldefense.com/v3/__https://blog.tomevslin.com/2022/02/starlin
> > ks-zoomready-rating-is-going-down.html__;!!CQl3mcHX2A!TjZjoTCGYO2gkt9x
> > YrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj8WTA26WA$
> >
> > --
> > I tried to build a better future, a few times:
> >
> > https://urldefense.com/v3/__https://wayforward.archive.org/?site=https
> > *3A*2F*2Fwww.icei.org__;JSUl!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHI
> > dNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj-yqmwsLA$
> >
> > Dave Täht CEO, TekLibre, LLC
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> >
> > https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/sta
> > rlink__;!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNN
> > y4u3_5CxlN2sj_SP7yVhg$
> >
>
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
>
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2022-03-03 15:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 14:37 [Starlink] zoomready result Dave Taht
2022-03-03 14:31 ` Livingood, Jason
2022-03-03 14:36 ` [Starlink] recent starlink rrul test result Dave Taht
2022-03-03 14:45 ` tom
2022-03-03 15:03 ` Dave Taht [this message]
2022-03-03 15:15 ` David Lang
2022-03-03 17:16 ` Nathan Owens
2022-03-03 17:42 ` tom
2022-03-03 20:36 ` David Lang
2022-03-03 20:37 ` David Lang
2022-03-09 14:23 ` [Starlink] zoomready result Nathan Owens
2022-03-09 14:57 ` Dave Taht
2022-03-09 15:17 ` Nathan Owens
2022-03-11 17:05 ` Luis A. Cornejo
2022-03-11 22:48 ` Nathan Owens
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=CAA93jw4mvyFWTW_i8Sg4freBPLKzPCYRc4B+Mmj-PX5kHC9b2w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=Jason_Livingood@comcast.com \
--cc=starlink@lists.bufferbloat.net \
--cc=tom@evslin.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