Skip to content

Why is there an option for stress testing Elastic Search on the vectordbbench page, but not in the command-line tool? #640

@midonKing

Description

@midonKing

[root@vectordb-test1 ~]# vectordbbench --help
Usage: vectordbbench [OPTIONS] COMMAND [ARGS]...

Options:
--help Show this message and exit.

Commands:
alloydbscann
awsopensearch
batchcli
clickhouse
hologreshgraph
lancedb
lancedbautoindex
lancedbhnsw
lancedbivfpq
mariadbhnsw
memorydb
milvusautoindex
milvusdiskann
milvusflat
milvusgpubruteforce
milvusgpucagra
milvusgpuivfflat
milvusgpuivfpq
milvushnsw
milvushnswpq
milvushnswprq
milvushnswsq
milvusivfflat
milvusivfrabitq
milvusivfsq8
oceanbasehnsw
oceanbaseivf
ossopensearch
pgdiskann
pgvectorhnsw
pgvectorivfflat
pgvectorscalediskann
pgvectorsflat
pgvectorshnsw
pgvectorsivfflat
qdrantcloud
qdrantlocal
redis
s3vectors
test
tidb
vespa
weaviate
zillizautoindex

I hope to conduct performance tests on Elasticsearch flexibly through the command line, but I found that on the command line interface, there seem to be no options for Elasticsearch.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions