Initial VectorDB Benchmark for MLPerf Storage V3 #220
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit is for VectorDB Benchmark implementation that allows you to benchmark and compare the performance of vector databases with current support for Milvus, DiskANN and HNSW indexing support and others planned.
The benchmark process consists of three main steps:
Detailed steps for setup and running benchmark are present in the README here: https://github.com/mlcommons/storage/pull/220/files#diff-c554ca2de4b3b7db86d7eb2b9c840e51edc6be7afe49bafe52dc95ce71969933
The PR also integrates unit test suite for the vdb_benchmakr vector database benchmarking tool.
It provides coverage for all components of vdb-bench, including:
Steps for running tests are present in the README here: https://github.com/mlcommons/storage/pull/220/files#diff-81f21bcb7d8cc604d135ef7b76a21e6aea402ee31251c6cccf5b3665bc8320de