nextcloud / nextcloud/groupfolders

After upgrading to NC29(30), creating a folder or file in a group folder (for ldap group 1000+ users) has noticeably slowed down

Open
#3,574 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
PHP
Stars
343
Forks
106
Avg merge
2d 3h
Merged PRs (30d)
34

Description

Steps to reproduce
  1. Create a group folder.
  2. Set access to it for ldap group of users more than 1000.
  3. Create a "new folder" in the group folder.
  4. Delete the "new folder".
Expected behaviour

The folder will appear almost instantly. And will disappear after deletion in the same amount of time.

Actual behaviour

The folder will appear in 4 seconds. It takes the same amount of time to remove it.

Server configuration

Debian 12
Nginx 1.22.1
Postgresql 14
PHP 8.3
NC30
Group folders 18.0.9
Updated from an older Nextcloud/ownCloud
NC installed on KVM with nfs mount for "data" folder.
External storage: local, smb
encryption: no
External user-backend: LDAP

Client configuration

Chrome browser
Debian 12

If you enable the activity option 'activity_use_cached_mountpoints' => true, then you have to wait 3 minutes or refresh the page. However, the flag for notifying changes in the group folder is not checked by default for most users.

Folders and files should be created as quickly as in the root directory.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing creation and deletion in a group folder shared with an LDAP group of more than 1,000 users, and compare the timing with the root directory. Investigate the group-folder handling around mountpoint changes and the activity_use_cached_mountpoints setting. Done means both operations complete with root-directory-like responsiveness without requiring a refresh or waiting several minutes.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, postgresql
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.