From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] UDP muxing: a completely unscientific benchmark
Date: Sat, 22 Mar 2025 20:50:04 +0100 [thread overview]
Message-ID: <87sen4onf7.wl-jch@irif.fr> (raw)
Hi,
70 seconds test, one sender, 10 receivers. The server is running on
a 4-core Cortex-A53 at 960MHz (an Allwinner A64 SoC). I didn't think
about generating a TLS certificate in advance, so the CPU time includes
roughly 2s spent generating an RSA key.
No UDP mux: user 20.15s, system 15.05s.
UDP mux: user 21.61s, system 19.05s.
I find the increase in system time suprising, but since I didn't repeat
the test, it might be an experimental error. I've generated a CPU
profile, and the time spent in the UDP mux is negligible, on the order of
a fraction of a percent.
I think we may conclude that the overhead of UDP muxing is negligible.
-- Juliusz
next reply other threads:[~2025-03-22 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 19:50 Juliusz Chroboczek [this message]
2025-03-22 20:36 ` [Galene] " Dirk-Willem van Gulik
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=87sen4onf7.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
/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