I'm experimenting with Jitsi Videobridge. I use it as a standalone external XMPP component. It seems to work just fine.
Out of curiosity, I wanted to see the CPU/memory consumption of the bridge. So, I attached to it using VisualVM.
Based on my observation, I can report the following:
- Memory consumption does not seem to be an issue with the video bridge. E.g. for a video-conference with 3 participants, it is roughly 15-20 MB in total, which is very good
- CPU load for the same conference seem to be about 5-10% on my Mac Book Air.
- But the number of live threads is rather significant. Without any ongoing conferences, the bridge uses about 35 threads. And based on my experiments, it seems that Jitsi Videobridge (or the Jitsi library used by it) allocates about 30 threads per new participant. For me it looks a bit excessive. In principle, it is not a big issue, but I'd like to check with you if this is the expected number of threads and it is supposed to be like this per design. Is there any reason to have so many threads per participant?