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
HTML Client loads really slow when entering a session with long duration #12619
Comments
What is the server specifications regarding cores, memory? when it happens does this happen to all new meetings that are started, or just the long running meeting? |
i do not thinkg CPU and RAM is an issue. We used to run the same scenarios for over a year without a single problem with 2.2 |
2.3 has node js, memory settings i believe that are looking for the min requires 16gb ram |
also think there is an issue with reading in all the past chat messages when i user joins, that was taking long to load... know that work was being done on this, but not sure where that improvement is. Do you have lots of messages in the chat in these long meetings? |
I have enough memory as suggested. I think you might be correct with Chat history and Shared Notes. I have lots of them after 7 hours meeting. Even Poll results. |
This will likely be improved significantly with #12271 Old chat re-synching was improved in 2.3 - you would not be grabbing all the data right away. But this is the first collection where we have logic similar to lazy loading. |
Ok. Hope it solves the issue. But until the release of 2.4 what is the proposed solution for cases such as the one i am experiencing? |
The server being used here is a baremetal and have the following specs: Intel Xeon-E 2136 - 6c/ 12t - 3.3GHz/ 4.5GHz |
We get the "Kill" or "Wait" message just yesterday. The session was about 90 minutes. there were about 200 participants. Sharing screen in active. Chats is active. BBB 2.3.4 |
1 session 250users above the recommended 150max in a class. Would be interested in any cpu/memory logs, and errors found in the bbb server logs during this meeting.. Was it the only meeting running at the time? Lots of full audio? Video? ScreenShare? |
Maybe @mabras is right. But in my case, as reported above, i have never experienced CPU or RAM issues during this issue. CPU < 35%, Net < 130Mbps and RAM < 16% |
Only one meeting. no video. screen share. ~3 full audio. |
Any news on this issue? |
I wonder if anyone has encountered this on 2.4-rc-*+ I am tagging this to 2.4 for the moment so we can check if more work is needed. |
Not entirely sure if this is connected but the effect is pretty similar. Our BBB server run on c5a.4xlarge with 50 GB of storage attached. The main effect we see is that the echo test takes way longer than usual to succeed. |
@jonnyfux Could you try this on 2.4-rc4 (soon to be rc5) and let us know if you encounter the same issue. |
Describe the bug
Running a long session, e.g. 9 hours with a lot of participants e.g. 100, the HTML Client is not functioning as expected if reconnected after 5 hours from the Meeting start.
It takes several seconds to respond and browser asks to "Wait" or "Kill" the page. If you click on "Wait" then the Browser responds and the AUDIO test starts.
To Reproduce
Steps to reproduce the behavior:
Although i am not sure, we have this experience after a meeting is open for 5 hours and user tries to connect
Expected behavior
Enter the room without delays
Actual behavior
It takes more than 30 secondes to connect. People think that the system craches and they refresh.
And that leads to longer delay.
Screenshots
If applicable, add screenshots to help explain your problem.
BBB version (optional):
2.3.4
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: