nextcloud / nextcloud/documentation
Improve "Performance" section
Open
Nobody has claimed this yet.
1. to develop
enhancement
manual: developer
overview
performance 🚀
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
- Add recommendations for bulk updating
- Mention limitations of
inqueries - How to use internal caching and best practices on cache invalidation
- Mention Profiler app and how to use it
- ... (tbd)
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
Start by locating the documentation's "Performance" section and review its existing content. Cover the listed topics—bulk updates, in query limitations, internal caching and invalidation, and the Profiler app—while clarifying the open-ended scope; done means the section contains actionable guidance for each agreed topic.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100