You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have set up a Jitsi server on a local environment, and the system works smoothly with less than 50 participants in a meeting. However, as the participant count exceeds 50, and especially when it reaches 200 or more, mobile clients (both Android and iOS) become unstable. The issues include:
. Audio and video stuttering
. Frequent app crashes and unexpected behavior
. During these occurrences, the server-side resource usage remains within normal ranges, suggesting that the problem might be . specific to the clients.
Our typical use case involves:
. A presenter sharing their screen and audio
. All other participants muted with their cameras turned off
In this scenario, the increase in participant numbers should not theoretically lead to continuous resource growth on the clients.
To address the issue, we have already tried the following optimizations:
. Disabling unnecessary listeners on the client side, such as volume changes and network status of other participants.
Despite these efforts, client instability persists when the number of participants exceeds 200.
Do you have any suggestions or optimizations we could implement to improve mobile client stability for large-scale meetings?
Platform
Chrome (or Chromium based)
Firefox
Safari
Other desktop browser
Android browser
iOS browser
Electron app
Android mobile app
iOS mobile app
Custom app using a mobile SDK
Browser / app / sdk version
newest rn sdk
Relevant log output
No response
Reproducibility
The problem is reproducible on meet.jit.si
More details?
No response
The text was updated successfully, but these errors were encountered:
What happened?
We have set up a Jitsi server on a local environment, and the system works smoothly with less than 50 participants in a meeting. However, as the participant count exceeds 50, and especially when it reaches 200 or more, mobile clients (both Android and iOS) become unstable. The issues include:
. Audio and video stuttering
. Frequent app crashes and unexpected behavior
. During these occurrences, the server-side resource usage remains within normal ranges, suggesting that the problem might be . specific to the clients.
Our typical use case involves:
. A presenter sharing their screen and audio
. All other participants muted with their cameras turned off
In this scenario, the increase in participant numbers should not theoretically lead to continuous resource growth on the clients.
To address the issue, we have already tried the following optimizations:
. Disabling unnecessary listeners on the client side, such as volume changes and network status of other participants.
Despite these efforts, client instability persists when the number of participants exceeds 200.
Do you have any suggestions or optimizations we could implement to improve mobile client stability for large-scale meetings?
Platform
Browser / app / sdk version
newest rn sdk
Relevant log output
No response
Reproducibility
More details?
No response
The text was updated successfully, but these errors were encountered: