From: <tom@evslin.com>
To: "'Nathan Owens'" <nathan@nathan.io>, "'David Lang'" <david@lang.hm>
Cc: <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] recent starlink rrul test result
Date: Thu, 3 Mar 2022 12:42:54 -0500 [thread overview]
Message-ID: <23e201d82f26$1d938720$58ba9560$@evslin.com> (raw)
In-Reply-To: <CALjsLJs9BkpYRvmcM7OzmxgDxxZODGjj9=R8EKjc_OAtQ9mK9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3403 bytes --]
I’ve also stayed with my Starlink connection for teleconferencing altho we now have fiber available. My connection is not usually the worst on the call but not perfect either. If I were a job seeker or being paid to present AND I had a choice, I wouldn’t use Starlink when critical
From: Starlink <starlink-bounces@lists.bufferbloat.net> On Behalf Of Nathan Owens
Sent: Thursday, March 3, 2022 12:16 PM
To: David Lang <david@lang.hm>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] recent starlink rrul test result
Same here, Google Meet / Zoom / Teams / FaceTime are great.
Dave, can you post the commands to run those flent measurements? I also finally recreated that irtt-based scatterplot, attached.
On Thu, Mar 3, 2022 at 7:15 AM David Lang <david@lang.hm <mailto:david@lang.hm> > wrote:
That said, I've been using starlink for work zoom calls for a while with no
significant issues (nothing I can pin on my side vs the other participants)
David Lang
On Thu, 3 Mar 2022, Dave Taht wrote:
> 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 <mailto: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 <mailto:starlink-bounces@lists.bufferbloat.net> on behalf of dave.taht@gmail.com <mailto: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$ <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$ <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 <mailto:Starlink@lists.bufferbloat.net>
>> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/starlink__;!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj_SP7yVhg$ <https://urldefense.com/v3/__https:/lists.bufferbloat.net/listinfo/starlink__;!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj_SP7yVhg$>
>>
>
>
>_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 6304 bytes --]
next prev parent reply other threads:[~2022-03-03 17:42 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
2022-03-03 15:15 ` David Lang
2022-03-03 17:16 ` Nathan Owens
2022-03-03 17:42 ` tom [this message]
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='23e201d82f26$1d938720$58ba9560$@evslin.com' \
--to=tom@evslin.com \
--cc=david@lang.hm \
--cc=nathan@nathan.io \
--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