Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: fq-codel trashing
Date: Tue, 12 Jan 2021 22:02:33 +0100	[thread overview]
Message-ID: <87k0shq36e.wl-jch@irif.fr> (raw)
In-Reply-To: <CAA93jw7Tg+7_210BD4-gAAjuEw5kVt=axybA5M14EJk8qGOe1w@mail.gmail.com>

> please try cake.

Both my servers are used in production right now, so I'm not very keen on
experimenting.  I should have some funding for Galène soon.

> And collect a capture on the underlying hw if possible.

I don't have access to the underlying hardware, it's a cloud provider.

>> * I need to think of a better way of prioritising voice over video when
>> under load;

> I take it (I really didn't understand) that unbundling these two types
> is not currently feasible in the javascript or webbrowser.

[...]

> collisions in fq_codel start to occur as the sqrt(1024) so at 70 users
> the odds are 2-3 of your sessions were colliding.

I don't think the network is the problem.  The problem is that there's
a lot of buffering in Pion, and as I push packets down the layers, I have
no way of finding out the amount already queued -- so when we're short on
CPU, the video tends to crowd out the audio.

I'm not sure what the solution is.

>> Galène recovered after some people switched their cameras off, I didn't
>> need to restart anything.  At the highest point, Galène was at 270% CPU,
>> and the TURN server was using another 50%.  That's on a four-core VM.

> but it does sound like more virtual cores will help at this load?

According to profiling, 60% CPU time is spent in the write system call.

> you are context switching like crazy most likely also.

I'll measure next time, but I doubt it: Go's scheduler operates almost
entirely in userspace.

-- Juliusz

  parent reply	other threads:[~2021-01-12 21:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 13:46 [Galene] " Juliusz Chroboczek
2021-01-12 15:55 ` [Galene] " Toke Høiland-Jørgensen
2021-01-12 16:01   ` Dave Taht
2021-01-12 17:38   ` Juliusz Chroboczek
2021-01-12 17:42     ` Dave Taht
2021-01-12 18:10       ` Juliusz Chroboczek
2021-01-12 19:05         ` Dave Taht
2021-01-12 19:52           ` Michael Ströder
2021-01-12 21:02           ` Juliusz Chroboczek [this message]
2021-01-12 19:29         ` Michael Ströder
2021-01-12 21:22           ` Juliusz Chroboczek
2021-01-13 19:09             ` Michael Ströder
2021-01-14 12:59               ` Juliusz Chroboczek
2021-01-14 13:03                 ` Michael Ströder
2021-01-14 13:10                   ` Juliusz Chroboczek
2021-01-14 13:23                     ` Michael Ströder

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=87k0shq36e.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=dave.taht@gmail.com \
    --cc=galene@lists.galene.org \
    --subject='[Galene] Re: fq-codel trashing' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox