Why the JVB pressure calculation formula is totalPacketRate/ Load-threshold?

[chenyurou]

Why the JVB pressure calculation formula is totalPacketRate/ Load-threshold? and the Load-threshold default is 50000

[manikandan.j.knl]

@damencho Can you please share the details on where i can refer to understand the load-threshold that we shall consider , is it based on cpu/memory/network?
Is there any formula that we shall use based on the instance type we select?

[shawn]

Loadbalancing between JVBs with weighting coefficients

Hey mstran, We have the bridge communicate to jicofo two values: stress_level: indicates the current load on the machine, with 1.0 corresponding to the maximum load it can handle without affecting call quality. average_participant_stress: a pre-configured value for the estimated stress that one endpoint contributes (i.e. the 1/max-participants). This is just an estimation. Jicofo uses those two values to calculate the stress of a bridge as follows: stress = stress_level + average_participan…

Autoscaling of Jitsi-Videobridges

@damencho is correct here, we use the JVB stress level metric, as reported via the colibri stats interface. this is used to make autoscaling decisions. This is tuned based on a threshold which is configurable on the JVB. We have currently tuned our JVBs with 4 CPUs and 8GB/RAM to 81250 (up from the default of 50000). This value is set in the configuration at: videobridge { load-management { load-measurements { packet-rate { # The packet rate at which we'll consider the b…

In simple terms, load-threshold is something you would tweak through observation based on your setup and would probably be the point where you start to see packet loss. By using that as a basis for calculating stress level, it can be used to make sure JVB is not stressed to the point that it starts to drop packets.