From: Nathan Owens <nathan@nathan.io>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
"starlink@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] zoomready result
Date: Wed, 9 Mar 2022 07:17:58 -0800 [thread overview]
Message-ID: <CALjsLJt_CTpmP2MRZS6Xn-UF1jRD25KMiUUaXxgnBnbUi=-Xig@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5-vH2wJ8YVBbn3tmk-4gD2SPQgn44O9B=x_e8kexE99w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2742 bytes --]
Hmm, I’ll see if I can reproduce this, I don’t think I see the same
behavior.
On Wed, Mar 9, 2022 at 6:57 AM Dave Taht <dave.taht@gmail.com> wrote:
> None of these web based tests run long enough to show the degradation
> in starlink service that happens after a "speedtest" like interval. I
> note that conceptually I don't have much problem with the idea of an
> ISP throttling bandwidth for "hogs" after some interval, but I do have
> a problem with that cost also being vastly increased delays whilst the
> throttling happens. I talked to the attached plot in my recent talk
> here: https://www.youtube.com/watch?v=TWViGcBlnm0&t=29m45s
>
> When you are dependent on realtime comms, and sharing a link with
> potentially many others, keeping queuing delays short no matter the
> bandwidth, in a warzone, seems important.
>
> On Wed, Mar 9, 2022 at 9:24 AM Nathan Owens <nathan@nathan.io> wrote:
> >
> > Here's mine when I'm not having any issues, pretty decent IMO:
> >
> >
> https://www.waveform.com/tools/bufferbloat?test-id=5d18f5f3-74b8-4cad-b7bf-3f5230fb993a
> >
> > On Thu, Mar 3, 2022 at 6:32 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/starlinks-zoomready-rating-is-going-down.html__;!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_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!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj-yqmwsLA$
> >>
> >> Dave Täht CEO, TekLibre, LLC
> >> _______________________________________________
> >> Starlink mailing list
> >> Starlink@lists.bufferbloat.net
> >>
> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/starlink__;!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj_SP7yVhg$
> >>
> >> _______________________________________________
> >> Starlink mailing list
> >> Starlink@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/starlink
>
>
>
> --
> 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
>
[-- Attachment #2: Type: text/html, Size: 5000 bytes --]
next prev parent reply other threads:[~2022-03-09 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 14:37 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
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 [this message]
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='CALjsLJt_CTpmP2MRZS6Xn-UF1jRD25KMiUUaXxgnBnbUi=-Xig@mail.gmail.com' \
--to=nathan@nathan.io \
--cc=Jason_Livingood@comcast.com \
--cc=dave.taht@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