Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: UDP muxing: a completely unscientific benchmark
Date: Sat, 22 Mar 2025 21:36:47 +0100	[thread overview]
Message-ID: <25DD360D-2A18-411B-A50B-F82670B6A562@webweaving.org> (raw)
In-Reply-To: <87sen4onf7.wl-jch@irif.fr>


On 22 Mar 2025, at 20:50, Juliusz Chroboczek <jch@irif.fr> wrote:

> I think we may conclude that the overhead of UDP muxing is negligible.

Same here - I tried a standard 1 minute 256 streams x 10 tests against it - and could (on a low end VPS) not measure the difference. 

This is with Galene `behind’ an apache reverse proxy and package in a FreeBSD jail; and comparing all CPU taken by that jail. Where the latter is either configured to take it through NAT with the -udp mux option; or `normal’ with its IP directly exposed.

Dw.

      reply	other threads:[~2025-03-22 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 19:50 [Galene] " Juliusz Chroboczek
2025-03-22 20:36 ` Dirk-Willem van Gulik [this message]

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=25DD360D-2A18-411B-A50B-F82670B6A562@webweaving.org \
    --to=dirkx@webweaving.org \
    --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