Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dave Taht <>
To: Juliusz Chroboczek <>
Subject: [Galene] Re: we broke galene head pretty badly today
Date: Mon, 5 Jul 2021 17:41:35 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

yes a codel-ly approach would be helpful, but what stage of the
pipeline is costing the most cpu?

What I saw in another set of tests was context switching cost a lot
and that perhaps recvmmsg and sendmmsg would help there.

Still, when you run out of cpu, dropping whole frames would be good.
you could interleave dropping a frame per sender perhaps?

do we know what other sfus do?

On Mon, Jul 5, 2021 at 2:01 PM Juliusz Chroboczek <> wrote:
> > Galčne currently reacts badly to being out of CPU.  I've tried to design
> > it so it would drop frames and keep the audio going, but I've failed.
> Just to be clear, I'm not looking at the load average or CPU utilisation,
> since these measures are typically unreliable on modern CPUs (which vary
> their speed dynamically) let alone on VMs.  I need a quick way to answer
> the following question: I've got this packet that I can drop without
> corrupting the video, should I drop it or not.
> Timestamp the packets at ingress time and drop anything droppable that's
> too old?  Any other ideas?
> -- Julius

Latest Podcast:

Dave Täht CTO, TekLibre, LLC

  reply	other threads:[~2021-07-06  0:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  4:39 [Galene] " Dave Taht
2021-06-02 10:48 ` [Galene] " Juliusz Chroboczek
2021-06-02 11:06   ` Dave Taht
2021-07-05 20:46 ` Juliusz Chroboczek
2021-07-05 21:01   ` Juliusz Chroboczek
2021-07-06  0:41     ` Dave Taht [this message]
2021-07-06 10:52       ` Juliusz Chroboczek
2021-07-06 13:44         ` Dave Taht
2021-07-06 13:47           ` Dave Taht
2021-07-06 15:56             ` 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='[Galene] Re: we broke galene head pretty badly today' \

* 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