zilliztech / zilliztech/VectorDBBench
vectordbbench should detect the index mis-match
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 438
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 1
Description
Reproduce steps:
- create HNSW-SQ index with following command:
vectordbbench milvushnswsq --uri "http://10.220.56.72:19530" --case-type Performance1024D10M --drop-old --m 16 --ef-construction 128 --ef-search 100 --refine false --refine-type fp32 --refine-k 100 --sq-type sq8
- retest QPS as HNSW index type with following command:
vectordbbench milvushnsw --uri "http://10.220.56.72:19530" --case-type Performance1024D10M --skip-drop-old --skip-load --m 16 --ef-construction 128 --ef-search 100
vectordbbench should report index type mis-match, but not
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
Begin by running the two provided vectordbbench commands in sequence against the same URI and case, confirming that the second run reuses the existing index. Trace the benchmark path that handles the HNSW-SQ and HNSW cases; done means the second command reports the index type mismatch instead of proceeding silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases, performance, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100