From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Dave Taht <dave.taht@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] impressed with my starlink today
Date: Mon, 18 Sep 2023 13:18:50 +0000 [thread overview]
Message-ID: <8AED1E59-907D-4639-B4EE-B88DEF84A0ED@cable.comcast.com> (raw)
In-Reply-To: <CAA93jw7Nu03s1M_4Fg4Pu0LDA9ZxFjvRK_mmdQ+nq9uXyK3WAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
IMO I don’t think you can judge that by using Galene – you need to use the large market-share platforms. Also, given the density issues facing LEO services, a single sample can’t be taken as particularly representative – you’d need more users across a broader range of density/terrain types.
JL
From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Reply-To: Dave Taht <dave.taht@gmail.com>
Date: Friday, September 15, 2023 at 18:45
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] impressed with my starlink today
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<https://urldefense.com/v3/__http:/galene.org__;!!CQl3mcHX2A!AwJw0pjxf076FkQM4rXF8f3rISzxQCURREhzLa7IZFgxvmgtQP16gVm8yjle-XsLqPa92ijxNko7aWsEdoQbf9jW__cpI23ESQ$> 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.
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html<https://urldefense.com/v3/__https:/netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html__;!!CQl3mcHX2A!AwJw0pjxf076FkQM4rXF8f3rISzxQCURREhzLa7IZFgxvmgtQP16gVm8yjle-XsLqPa92ijxNko7aWsEdoQbf9jW__eDsNR67A$>
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 4667 bytes --]
next prev parent reply other threads:[~2023-09-18 13:19 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 [this message]
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
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=8AED1E59-907D-4639-B4EE-B88DEF84A0ED@cable.comcast.com \
--to=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