Now we have all Jitsi-meet components in docker containers in single CentOS7 VM with
- 12 core CPU (Intel® Xeon® Gold 6132 CPU @ 2.60GHz),
- 16Gb of RAM and
- 10Gbit Network card.
We have a lot of such log entry’s
WARNING: Negative rtt value: -1.0003660000000991 ms, remote processing delay was PT3.541000366S (232063), srSentTime was 2020-06-05T09:06:07.890Z, received time was 2020-06-05T09:06:11.430Z WARNING: Suspiciously high rtt value: 15643.804688 ms, remote processing delay was PT0.450195312S (29504), srSentTime was 2020-06-05T09:06:15.158Z, received time was 2020-06-05T09:06:31.252Z WARNING: RTT suspiciously high (1459ms), capping to 1000ms.
It’s only Warnings but tons of them!
So my questions is:
- What could the cause of negative RTT?
- What could the cause of such high RTT? (10000 and even more)
- What can we do to minimize amount of that lot events?
Here is a conferences graph of that week for our deployment.
And CPU graph
PS. Multiple JVB with OCTO in plans for now.