Hello Team,
I am unable to see cpu in openvidu.pro.cluster.load-strategy dropdown on the config page of the inspector. Also, it is missing in the documentation under https://openvidu.io/docs/openvidu-pro/reference-docs/openvidu-server-pro-params/ (see openvidu.pro.cluster.load-strategy). The installation is on Digitalocean. Could you take a look, please? Thanks.
Hi,
CPU load strategy is not available yet. You may have seen it in previous releases, but it didn’t really take effect. But let me explain why the default value streams will behave in a similar way to cpu:
cpu load strategy would ideally track the cpu load of every Media Node of your OpenVidu Pro cluster and distribute the new sessions to the less loaded Media Nodes. But the ability to gather the cpu load from the Media Nodes is still in development. We will incorporate it soon to add automated elasticity to OpenVidu Pro, for which we do require knowing the exact value of the cpu load of all Media Nodes through time. This way we will be able to decide whether to automatically launch or drop Media Nodes to adapt the cluster size on demand.
Now, in terms of load strategy, streams is a good measure because it distributes load counting the number of media streams that are managed by each Media Node. If Media Node A has one publisher and 10 subscribers, it will have 11 media streams in total. Media Node B may have 2 publishers and 10 subscribers, summing up 12 streams. Next session being created would be initialized inside Media Node A, in this case. It is perfectly reasonable to consider that more number of streams means more cpu load, and the calculation is immediate because all the information is available in OpenVidu Server, without having to collect it from the Media Nodes.
To sum up, there will be little difference between using streams and cpu load strategies. cpu will be a measure very useful for other things, but not especially for session load distribution.
Regards.
Thanks for the update. In that case, it is a good idea to remove it from https://github.com/OpenVidu/openvidu-pro-clustering/blob/2.12.0-on-premise/group_vars/all#L121 too as it could confuse people.
You’re totally right. Already fixed
