CPU usage spikes are to be expected as various things execute periodically (like health checks, garbage collection, etc) but an average of 65% sounds like a lot to me, especially for a single audio only call... It would be interesting to run some monitoring system (like datadog, zabbix, influxdb, nagios) and look at some graphs.
About the error message that you got, it’d be good to know your stack versions (JVB, Jicofo, Jitsi Meet) and have some logs. Obviously it should not happen, but it’s hard to tell why it happened without more information.
I hope this helps.
On May 17, 2017, at 4:53 AM, firstname.lastname@example.org wrote:
I just ran an audio conference in Jitsi Meet on an mac mini Intel I5.
We had 30-31 persons attending.
Average cpu load for JVB was 60-70%, but sometimes the cpu load
rached 99% or maybe more…
Memory was around 15% all time.
Five times during our 1.5 h conference
I got ‘Unfortunately, something went wrong. We’re trying to fix this…’
But could not reconnect without rebooting jvb and nginx.
Why does JVB sometimes increase cpu load?
users mailing list
Unsubscribe instructions and other list options: