nextcloud / nextcloud/richdocuments
Analyse document loading time
Open
Nobody has claimed this yet.
1. to develop
high
performance 🚀
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
We should analyse and improve where feasible
- Loading time when opening a link to a document (loading with files app from scratch)
- Frontend profiling, possibly optimize viewer and files app loading to be deferred
- Loading time when having the files list open and clicking on a file in the file list
- Frontend profiling for files app, viewer, richdocuments
- Time of requests that happen from Collabora to Nextcloud
- Profile requests and see what happens in them in the backend and if things can be improved
- See if requests can be saved with the new settings endpoints being fetched
- iframe load until document rendering within Collabora
- Can we do any smart pre-loading, like when hovering elements
- Within Collabora
- Within Nextcloud
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
Begin with frontend profiling for the files app, viewer, and richdocuments across the two document-opening flows. Then profile Collabora-to-Nextcloud requests and iframe loading through document rendering. Done would require measured bottlenecks, feasible improvements, and evidence of their impact, but the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, frontend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100