[FEA] DiskANN cuvs-bench Wrapper Tracking Issue
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
This issue keeps track of the remaining pieces of DiskANN that can be added to the cuvs-bench algos (diskann_memory, diskann_ssd, cuvs_vamana) after PR #260 is merged.
- Allow sharding with limits on build and search DRAM budgets for diskann_ssd indexes
- The ability to convert (serialize) a cuVS Vamana index to a DiskANN SSD index (waiting on quantization API to dump PQ quantized vectors / PQ centers that can be used by DiskANN during search)
- Reuse PQ pivots / quantized vectors for different SSD index builds.
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 reviewing PR #260 and the cuvs-bench implementations for diskann_memory, diskann_ssd, and cuvs_vamana. Work through the three checklist items, noting that SSD serialization depends on a quantization API for PQ vectors and centers; done means the listed sharding, conversion, and PQ-reuse capabilities are implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100