Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
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 18:25:44 +0200	[thread overview]
Message-ID: <87msxjqwhj.wl-jch@irif.fr> (raw)
In-Reply-To: <CAA93jw7Nu03s1M_4Fg4Pu0LDA9ZxFjvRK_mmdQ+nq9uXyK3WAA@mail.gmail.com>

> Admittedly, I was using galene.org

Full credit where credit is due: the congestion controller in the
downstream direction lives in the browser, so full credit to the folks
behind libwebrtc.  As to the upstream direction, we're using our homebrew
code, which is not very good.

We're currently using receiver-driven congestion control, which is
deprecated in WebRTC.  The plan is to switch to sender-driven congestion
control at some point (I'm no big fan, but that's what everyone is
implementing, and we better be compatible with the rest of the universe).
That will mean using Pion's congestion controller in the downstream
direction, and libwebrtc's one in the upstream.  And I'm told Pion's
congestion controller is not very good.

(I could in principle use receiver-driven for the downstream and
sender-driven for the upstream, thus using libwebrtc's excellent
controllers in both directions, but it really feels like a hack.  I'd
much rather not negociate receiver-driven at all.)

-- Juliusz

  parent reply	other threads:[~2023-09-18 16:25 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 [this message]
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=87msxjqwhj.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --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