Skip to content

docs(vdb): update command examples for current CLI#588

Draft
idevasena wants to merge 4 commits into
mainfrom
docs/vdb-command-examples-current
Draft

docs(vdb): update command examples for current CLI#588
idevasena wants to merge 4 commits into
mainfrom
docs/vdb-command-examples-current

Conversation

@idevasena

@idevasena idevasena commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR follows up on the VectorDB documentation review from #452 and updates the command examples to match the current mlpstorage CLI.

The change is intentionally narrow: it updates stale command syntax in vdb_benchmark/README.md and aligns the directly related VectorDB result-path / parameter wording in Rules.md. It does not rewrite the README structure or change unrelated sections such as Prerequisites, Deploy Milvus, Direct Scripts, Metrics, or Troubleshooting.

Motivation

The current VectorDB README still contains older mlpstorage command forms, including examples such as:

./mlpstorage vectordb ...
datagen --file
run --file
--open
--what-if
--mode timed

The current CLI uses a mode-first structure and positional storage type:

./mlpstorage <closed|open|whatif> vectordb <datasize|datagen|run> ...

Updates to Rules.md

Updated only the directly related VectorDB CLI / result identity wording.

Key updates:

Updated VectorDB result path wording from:

vector_database/<index>/...

to:

vector_database/<vdb_engine>/<vdb_index>/...

Clarified the distinction between:

--vdb-engine
--vdb-index
--index-type

where --vdb-engine and --vdb-index identify the benchmark result path / reporting identity, while --index-type remains the concrete Milvus build argument used by datasize and datagen.

Corrected the HNSW parameter row:

index.M

from the stale DiskANN-style flag:

--max-degree

to the HNSW-specific flag:

--M
Corrected the HNSW implementation fallback from 64 to 16.

Updated the run-mode row from:

run.mode / --mode

to:

run.benchmark_mode / --benchmark-mode

Renamed the VectorDB table column from Default to Implementation fallback to avoid implying that parser fallbacks are finalized CLOSED-profile requirements.

Signed-off-by: Devasena Inupakutika <devasena.i@samsung.com>
Signed-off-by: Devasena Inupakutika <devasena.i@samsung.com>
@idevasena idevasena requested a review from a team June 29, 2026 23:53
@github-actions

Copy link
Copy Markdown

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

@FileSystemGuy FileSystemGuy marked this pull request as draft June 30, 2026 00:03
@FileSystemGuy

Copy link
Copy Markdown
Contributor

@idevasena I converted this to DRAFT so that I could figure out what needs to change (and what doesn't) in the --results-dir generation and validation code without worry that a wild @russfellows would merge it in! :-)

@russfellows

Copy link
Copy Markdown
Contributor

Perfect. I'm done merging for the day. I'll await further instructions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants