On the jitsi call from February 10th there was some discussion around the memory usage of the JVB. It was mentioned that the JVB should be using only a few hundred MB of memory and upping the heap limit could cause longer pauses for garbage collection.
Last fall we were having JVBs run out of memory so we upped the heap limit and the container memory limit (and also the instance size as a precaution). We are running a quite old JVB (build 1109) but are working on upgrading to JVB 2. With our current production bridge (1109 build), the container memory usage is typically using about 500 MB after a deploy and rises up to 1 - 1.5 GB within the first day or two and ends up rising up to 2 - 3 GB in a stair step pattern and then hovering there for a while.
A couple questions:
- Is the memory footprint of the new JVB that much lower than the old JVB or is there possibly something else going on?
- We use the prometheus exporter (https://github.com/karrieretutor/jitsi-prom-exporter/) but it lacks the java metrics. Has there been any talk about having a prometheus metrics endpoint built into the bridge to get both application and java metrics? We might be able to add that if it would be a welcome change.