From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] starlink upload behavior
Date: Wed, 31 Aug 2022 08:22:29 -0700 [thread overview]
Message-ID: <CAA93jw5YrcpR5YOYz+v+iTv9Ct893iak8psPJ+OFDzsd1yzH=g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4MyyR3SGaUHg7HVaVn97CQJjQPByoiR8EvdaWe5mafjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
I have just been leaving cake at 6Mbit on the upload and that fq and
control make it much
more tolerable for my mix of videoconferencing and uploads. That said,
I hadn't looked
at the native performance in a while which is markedly better than it
was a few months ago, at least for this quick test run.
If anyone can make sense of these... for the first 1/3 of the trace
throughput is low and RTTs are *NICE*,
the second looks like a sat switch - still nice... then another sat
switch where I get full upload throughput
and the latency grows significantly.
If anyone is into packet captures:
http://www.taht.net/~d/starlink-1-auto.cap # starlink through their wifi
http://www.taht.net/~d/starlink-1-cake6.cap # starlink through their
wifi, with cake bandwidth 6mbit on mine
Graphs produced with xplot.
[-- Attachment #2: starlink-up-acks.png --]
[-- Type: image/png, Size: 9898 bytes --]
[-- Attachment #3: starlink-up-rtt.png --]
[-- Type: image/png, Size: 9919 bytes --]
[-- Attachment #4: starlink-up-tput.png --]
[-- Type: image/png, Size: 8332 bytes --]
[-- Attachment #5: starlink-zoomed.png --]
[-- Type: image/png, Size: 19365 bytes --]
[-- Attachment #6: starlink-cake6-rtt.png --]
[-- Type: image/png, Size: 9320 bytes --]
next prev parent reply other threads:[~2022-08-31 15:22 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1661875202.32670.starlink@lists.bufferbloat.net>
2022-08-30 16:53 ` [Starlink] Starlink "beam spread" David P. Reed
2022-08-30 17:32 ` Doc Searls
2022-08-30 20:09 ` Mike Puchol
2022-08-30 20:35 ` Daniel AJ Sokolov
2022-08-30 20:40 ` Mike Puchol
2022-08-30 21:09 ` David Lang
2022-08-30 21:01 ` David Lang
2022-08-30 22:07 ` Brandon Butterworth
2022-08-30 22:21 ` David Lang
2022-08-30 22:37 ` Brandon Butterworth
2022-08-30 23:07 ` David Lang
2022-08-30 23:45 ` Brandon Butterworth
2022-08-30 23:28 ` David P. Reed
2022-08-31 0:12 ` David Lang
2022-08-31 0:31 ` Dave Taht
2022-08-31 0:32 ` David P. Reed
2022-08-31 10:29 ` Dave Collier-Brown
2022-08-31 18:51 ` David Lang
2022-08-31 19:04 ` Dave Taht
2022-08-30 22:50 ` Ulrich Speidel
2022-08-30 23:13 ` David Lang
2022-08-31 0:46 ` tom
2022-08-31 0:58 ` Dave Taht
2022-08-31 7:36 ` Mike Puchol
2022-08-31 6:26 ` Sebastian Moeller
2022-08-31 7:25 ` Ulrich Speidel
2022-08-31 7:31 ` Hayden Simon
2022-08-31 7:33 ` David Lang
2022-08-31 9:59 ` Mike Puchol
2022-08-31 10:06 ` David Lang
2022-08-31 10:12 ` Mike Puchol
2022-08-31 17:52 ` Dick Roy
2022-08-31 13:41 ` Ulrich Speidel
2022-08-31 14:30 ` Mike Puchol
2022-08-31 21:44 ` Ulrich Speidel
2022-09-01 7:58 ` Sebastian Moeller
2022-09-01 11:38 ` Ulrich Speidel
2022-09-01 19:54 ` Michael Richardson
2022-09-01 21:08 ` tom
2022-09-02 7:52 ` Sebastian Moeller
2022-09-02 12:29 ` tom
2022-08-31 7:49 ` Sebastian Moeller
2022-08-31 9:25 ` Brandon Butterworth
2022-08-31 9:34 ` David Lang
2022-09-01 9:12 ` Brandon Butterworth
2022-08-31 14:52 ` Dave Taht
2022-08-31 15:22 ` Dave Taht [this message]
2022-09-01 19:24 ` [Starlink] starlink upload behavior Luis A. Cornejo
2022-09-01 19:50 ` Dave Taht
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='CAA93jw5YrcpR5YOYz+v+iTv9Ct893iak8psPJ+OFDzsd1yzH=g@mail.gmail.com' \
--to=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