From: Tim Panton <tim@pi.pe>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Total bandwidth limit?
Date: Wed, 22 Nov 2023 22:42:45 +0000 [thread overview]
Message-ID: <A2420B23-6032-46CD-8F58-D3E332B36C18@pi.pe> (raw)
In-Reply-To: <874jhdwtes.wl-jch@irif.fr>
> On 22 Nov 2023, at 18:10, Juliusz Chroboczek <jch@irif.fr> wrote:
>
>> So I’m wondering - would it be possible to tell Galene what the total
>> uplink available is and have it throttle back the senders to stay within
>> that? Or is this such an edge case that no-one else would be as foolish
>> as me?
>
> This should happen automatically : congestion control should kick in, and
> Galene should either peel SVC layers or throttle the sender (depending on
> your codec) until the traffic fits within the link's limitations.
I was thinking the fact that the limitation is shared across all 7 remote users
(I was local on the same lan as the Galene server)
may have confused the situation - along with the fact that it is a massively asymmetric link.
>
> Obviously, that didn't work in your case. What codec were you using, and
> what web browser was the sender using? Were the receivers connecting
> directly to Galene, or were they going over TURN ?
VP9 and no TURN - I’m old/lucky enough to have a /24 routed to my house :-)
I think I was using chrome, but it may have been safari on Mac - at least 2 of the others were safari on iPad.
I’d guess the rest were chrome on windows.
Tim.
>
> -- Juliusz
next prev parent reply other threads:[~2023-11-22 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 8:06 [Galene] " Tim Panton
2023-11-22 18:10 ` [Galene] " Juliusz Chroboczek
2023-11-22 22:42 ` Tim Panton [this message]
2023-11-22 22:58 ` Juliusz Chroboczek
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.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A2420B23-6032-46CD-8F58-D3E332B36C18@pi.pe \
--to=tim@pi.pe \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
/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