Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Understanding metric value signaling_mcu_backend_load #786

Open
pmarini-nc opened this issue Jul 30, 2024 · 2 comments
Open

Understanding metric value signaling_mcu_backend_load #786

pmarini-nc opened this issue Jul 30, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@pmarini-nc
Copy link

Is it correct to say that signaling_mcu_backend_load is the maximum load sent to a MCU node, expressed in Kibibit/sec?

It seems that this value is a calculated as (m*maxstreambitrate + n*maxscreenbitrate)/1024.

@fancycode
Copy link
Member

It's an (arbitrary) value that represents how "loaded" a signaling proxy server is, so the signaling server can decide which proxy to use when a new publishing request is received.

For now it's the maximum possible bandwidth for the allocated streams (both incoming and outgoing). So yes, for now it's (m*maxstreambitrate + n*maxscreenbitrate)/1024, but that might change in the future.

I'm planing to add metrics to get the current incoming / outgoing bandwidth of proxies if this is what you are looking for.

@fancycode fancycode added the enhancement New feature or request label Jul 31, 2024
@pmarini-nc
Copy link
Author

OK, thanks for the explanation and looking forward to have the current incoming /outgoing bandwidth as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants