Increased loading time when the ‘Rich workspace’ option is activated.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
Describe the bug
I have 5000 group folders configured with tag and ACL, when the ‘Rich workspaces’ option is activated it takes about 3 minutes to load the file app. Once the option is deactivated ( occ config:app:set text workspace_available --value=0 ) it takes 14 seconds.
Server details:
- Nextcloud version: 29.0.5
- PHP Version: 8.3
- Database: Postgres 16
Client details:
- OS: Windows / Ubuntu
- Browser: Firefox Chrome
After further research, the Webdav response contains a ‘ <nc:rich-workspace /> <nc:rich-workspace-file /> ’ field for each sub-folder which is not necessary.
Maybe linked to https://github.com/nextcloud/text/pull/5963
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the file app load with 5,000 group folders and the Rich workspaces option enabled and disabled. Inspect the WebDAV response and review nextcloud/text PR 5963, focusing on the per-sub-folder rich-workspace fields. Done means the unnecessary fields no longer cause the reported slowdown while Rich workspaces remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100