qdrant / qdrant/vector-db-benchmark
Coordinated omission
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 371
- Forks
- 155
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
Glancing at the code looks like this project makes no effort to measure service and wait time, rather just measuring service time - suffering from Coordinated omission.
I'd suggest authors look at tools such Rally which measure this carefully.
While i dont think qdrant will be impacted as much by this, its more of a concern where systems can stall e.g. JVM based technologies.
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
The issue names no files, tests, or entry points. Start by locating how this benchmark records service time, then compare its approach with Rally's coordinated-omission guidance. Done means the benchmark measures service and wait time rather than service time alone, with the behavior documented and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100