Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: we broke galene head pretty badly today
Date: Tue, 6 Jul 2021 06:44:48 -0700	[thread overview]
Message-ID: <CAA93jw6fe11j4aLCoy5TvspDVm+HvJO=vxWN=071UH3kDXVfzg@mail.gmail.com> (raw)
In-Reply-To: <87a6mzpvdb.wl-jch@irif.fr>

On Tue, Jul 6, 2021 at 3:52 AM Juliusz Chroboczek <jch@irif.fr> wrote:
>
> > yes a codel-ly approach would be helpful, but what stage of the
> > pipeline is costing the most cpu?
>
> Galčne is fairly well optimised, on a machine with hardware crypto, most
> of the time is spent in the write system call.  I'll post a profile when
> I'm next at the lab.

What hardware is the weakest and when does it start to fail?

I can also start setting up simple videoconferences. It would be
really good to have a tool
that could create virtual sessions to load things up. I got tired of
bigbuckbunny a long time ago
but I've often thought it would be amusing to try and sync up a 4+ piece band.

>
> > Still, when you run out of cpu, dropping whole frames would be good.
> > you could interleave dropping a frame per sender perhaps?
>
> I can drop every second frame without causing video corruption, and I can
> put backpressure on the sender, the code is already there.  The only
> difficulty is how to determine that I'm under load.

timestamp a packet or frame on entry (as early as possible), check
time again on exit (after the write). If the delta is greater than the
framerate, start dropping frames.

st

>
> -- Juliusz



-- 
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/

Dave Täht CTO, TekLibre, LLC

  reply	other threads:[~2021-07-06 13:45 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
2021-07-06 10:52       ` Juliusz Chroboczek
2021-07-06 13:44         ` Dave Taht [this message]
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:
  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='CAA93jw6fe11j4aLCoy5TvspDVm+HvJO=vxWN=071UH3kDXVfzg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    --subject='[Galene] Re: we broke galene head pretty badly today' \
    /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