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
share a board to a large group causes Nextcloud unusable #2015
Comments
Please fill out the complete issue template, as it is very hard to tell if that is not an issue with a to slow system. A board shared with 400 people might cause quite some activity entries being created, that could be quite a bottleneck. |
The Nextcloud deployment is designed to share files for a 500 people group with suitable cpu/memory/storage/redid/postgresql in a public cloud. |
I'd like to report that the problem remains the same after upgrading to Nextcloud 18.0.6 and Deck 1.0.3. |
Still need to know what specification, OS, etc. the server is. AFAIK there are no guidelines for sizing an NC server based on usage patterns of a particular app i.e. Deck. |
I can reproduce this now, so it is mainly caused by deck fetching all users that could have access to the board. Ideally we need another endpoint where the list of available users can be obtained from in pages. |
I'm not sure if this is a limitation or a bug, as I'm new to Nextcloud and this plugin.
If I create and share a board to a large group, for example a group of about 400 persons, any action causes Nextcloud unusable.
The actions include adding a list, view the board from others.
The problem comes immediately after the action, as the status check(e.g. visit /status.php) starts to fail even with 30 seconds timeout.
The CPU usage surges as the problem comes.
The only way to recover is to restart and delete the shared board.
Nextcloud 18.0.4
Deck 1.0.2
The text was updated successfully, but these errors were encountered: