qdrant / qdrant/vector-db-benchmark
Add recall metric
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Python
- Stars
- 371
- Forks
- 155
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
We calculate precision but for higher values of K, it's more valuable to optimize for recall. Therefore, we should measure it.
Contributor guide
No contributing guide indexed for this repository
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 where the benchmark currently calculates and reports precision, then trace how values of K and benchmark results are handled. Add recall measurement alongside precision and verify that benchmark output includes it for higher K values; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100