-
Notifications
You must be signed in to change notification settings - Fork 32
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
After login, Nextcloud hangs, browsers report long-running script #119
Comments
Sorry for the late response. Your user base is really large, maybe too large for a contact list. Do you have any plans to reduce this number? I think it's not that helpful for your users, but we should fix this issue anyway. Can you try to reproduce this in our upcoming JSXC 4.0 release? https://www.jsxc.org/blog/2018/09/26/v4.0.0-first-alpha-released.html |
Hey, thanks for the reply. I'm sorry to say that we will not be able to reduce the number of users as our Nextcloud instance is rather tightly coupled to our LDAP server and we do rather rely on the fliesharing capabilities as this enables easy access to files from outside the campus - something that's a strict requirement by our state for some educational curricula. |
I meant it's unlikely that everyone wants to chat with everyone on the campus. Therefore I suggest that you use an external XMPP server, so that every user can manage his contact list by it's own. Most XMPP servers also have an option or plugin to map ldap groups to the contact list. Hope this helps. Nonetheless the insertion should be improved. Thanks for the hint. |
We currently have a huge user pool (1700+) with your chat module enabled. Upon login any user will encounter a freezing browser with the usual browser message that a long-running script is blocking everything. After stopping this script, Nextcloud will work as usual.
From profiling the browser performance after login, it seems to be the case that there are two forEach loops running and I'm guessing that it's thus looping twice (i.e. O(n²)) over all the users. Looks like this:
You can easily see where the script is engaging / blocking @ 12800 ms.
Currently we don't have a stand-alone XMPP server behind our NextCloud instance.
Basically: What can we do to have a XMPP chat without this blocking issue?
The text was updated successfully, but these errors were encountered: