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: Mon, 5 Jul 2021 17:41:35 -0700 [thread overview]
Message-ID: <CAA93jw60VySmTHrBpDVkL2y-WCFYuT=KitDWrzqHpnA8mmV-8w@mail.gmail.com> (raw)
In-Reply-To: <87wnq4wk3v.wl-jch@irif.fr>
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 <jch@irif.fr> 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:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
Dave Täht CTO, TekLibre, LLC
next prev parent 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:
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='CAA93jw60VySmTHrBpDVkL2y-WCFYuT=KitDWrzqHpnA8mmV-8w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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