typesense / typesense/typesense
Performance problem (facets)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 973
- Avg merge
- 18h 45m
- Merged PRs (30d)
- 4
Description
Hello, what is the slow generation of "facets" and returning results - with the amount of all 100+ (10-30 returned) and the amount of 100000+ results in the database.
I specifically tested meilisearch, and typesense and meilisearch handle it much, much better. At times it is a reprint 5-10 times. (If we return facets all available)
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 facet-generation and result-returning slowdown with more than 100,000 database results and 100+ facets, measuring cases that return 10–30 facets. Compare the timings with the reported Meilisearch and Typesense behavior; done means the performance gap and repeated 5–10 second delays are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- search
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100