Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] impressed with my starlink today
Date: Mon, 18 Sep 2023 21:48:06 +0200	[thread overview]
Message-ID: <87bkdzqn49.wl-jch@irif.fr> (raw)
In-Reply-To: <8658.1695062436@localhost>

> If I understand correctly, galene would support p2p media streams?

No, Galene only does client-server media.  Before I wrote Galene,
I experimented with peer-to-peer WebRTC, and it worked beautifully in
small groups, but collapsed somewhere around 4 to 5 participants.

The problem is not the amount of data (Galene uses at most 700kbit per
flow in the default configuration), but the fact that current WebRTC
implementations require you to encode the video separately for each peer.

> It seems to me that if you have multiple outgoing streams, that if there are
> problems with any of them, a sender-driven system allows for better use of
> what is typically a smaller uplink.

In the sender-driven approach, the receiver gives very detailed feedback
to the sender (lost packets, packet arrival timestamps), who runs the
congestion control algorithm.  In the receiver-driven approach, the
receiver runs the congestion control algorithm, and sends a single integer
to the sender, the maximum allowed rate.  There's nothing that prevents
the sender from reducing the rate below what the receiver requested even
in the receiver-driven algorithm.

Does one of the approaches give more flexibility to the sender?  I'm
frankly not convinced, but perhaps I'll change my mind once I've
implemented it.

-- Juliusz

  parent reply	other threads:[~2023-09-18 19:48 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 [this message]
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=87bkdzqn49.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=mcr@sandelman.ca \
    --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