From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] impressed with my starlink today
Date: Mon, 18 Sep 2023 12:37:55 -0700 (PDT) [thread overview]
Message-ID: <23p3762o-798o-rs8q-686r-s05nr7o6s826@ynat.uz> (raw)
In-Reply-To: <CAA93jw7Nu03s1M_4Fg4Pu0LDA9ZxFjvRK_mmdQ+nq9uXyK3WAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
I work remotely and routinely use Starlink for video calls while doing other
uploads/downloads. As do several others at my company. Some of us are in rural
areas, I'm in Southern California, but in a place that doesn't have fiber
available (predicted to arrive at my address sometime next year)
Starlink occasionally has hiccups, but not significantly more so than other
people's network connections.
David Lang
On Fri, 15 Sep 2023, Dave Taht via Starlink wrote:
> I just did a bunch of videoconferences all morning without many glitches.
> (2 hours, only one download glitch, not recording so I do not know how good
> the up was) Admittedly, I was
> using galene.org rather than zoom, but I did do a couple up and downloads
> while talking and they seemed to work pretty well.
>
> I ran a few tests afterwards, to observe my overall bandwidth up was way
> up, and tcp congestion controls pretty smoothly adapting to physical
> changes in RTT and bandwidth for a change. I sat there and admired the
> T+120 smoothnesss in this transition, in particular.
>
> Anyone else seeing progress in long term behaviors? I think in part it was
> just galene doing better, or perhaps it was because my baseline bandwidth
> stayed above galene´s base.
>
>
>
prev parent reply other threads:[~2023-09-18 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 22:44 Dave Taht
2023-09-18 13:18 ` Livingood, Jason
2023-09-18 14:13 ` Dave Taht
2023-09-18 16:25 ` Juliusz Chroboczek
2023-09-18 18:40 ` Michael Richardson
2023-09-18 19:44 ` Frantisek Borsik
2023-09-18 19:57 ` Juliusz Chroboczek
2023-09-18 20:18 ` Frantisek Borsik
2023-09-18 19:48 ` Juliusz Chroboczek
2023-09-18 19:37 ` David Lang [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/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=23p3762o-798o-rs8q-686r-s05nr7o6s826@ynat.uz \
--to=david@lang.hm \
--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