nextcloud / nextcloud/bookmarks
Childorder query with a lot of bookmarks takes a long time
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 189
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 10
Description
35.91s in "childorder" with over 5000 bookmarks in root folder.
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 reproducing the reported "childorder" query with more than 5,000 bookmarks in the root folder and measure its runtime. Trace the query entry point and database work involved; done means the same workload completes substantially faster without changing the expected bookmark ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100