Loading thread info for search results is not performant
Open
Nobody has claimed this yet.
feature: api 🛠️
feature: search 🔎
feature: threads 🧵
performance 🚀
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
This does a query per search result.
Should be moved to a prepare step like we do in other places (same problem there is share loading)
Originally posted by @nickvergessen in #15858
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 tracing how thread information is loaded for search results and compare it with the existing prepare steps referenced in the issue. Check the related share-loading path as well; done means search results no longer trigger one query per result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100