qdrant / qdrant/vector-db-benchmark
Add support to wait for server to start in all the engines
Open
Nobody has claimed this yet.
enhancement
nice-to-have
- Dominant language
- Python
- Stars
- 371
- Forks
- 155
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
Some engines like ElasticSearch and OpenSearch take relatively longer to boot. It would be nice to have the wait feature in-built in the benchmarking script.
Note: It's a low priority task.
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 the benchmarking script and the startup paths for each supported engine, especially Elasticsearch and OpenSearch. Trace how readiness is currently handled, then verify that every engine waits for its server before benchmarking begins and that the behavior works for the slower engines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100