VectorDBBench

Benchmark for vector databases.

Runssource: GitHubhomepagePythonMITcommit 1760db148b95

Python, MIT licensed. The project labels itself: benchmark, cost effectiveness, performance, vector database, vector search and vectordb.

VectorDBBench runs. An Argusic agent installed it in 12 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

vectordb-bench installed from source in venv, 247 of 256 unit tests pass, CLI and REST API both operable

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.28 (measured)
recorded runs
2
last tested
stars
1,201
forks
457
open issues
161
watchers
14
size
5 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing VectorDBBench, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Missing optional deps: opensearch-py, chromadb, pinecone, elasticsearch, mysql-connector-python, turbopuffer, pyvespa, flask3 minutes
  • PEP 668 externally managed environment blocks system pip install2 minutes
  • test_elasticsearch_cloud.py imports broken ElasticsearchConfig from wrong module2 minutes
  • test_bench_runner.py uses DB.Milvus.config() and CaseType.PerformanceSZero which don't exist2 minutes
  • test_fts_filter_runner.py mocks lack case_config attr needed by CaseRunner2 minutes
  • test_models.py merge test globs legacy dbPrices.json without run_id key1 minute
Install time
12 minutes
Cold machine to finish
22 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
pytest returned '247 passed, 1 skipped' across runnable unit tests; vectordbbench --help exits 0; init_bench_rest Flask server starts and /get_status returns 200
Model tokens used
207,659
Exact commit tested
1760db148b95
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**REST API verification:** `init_bench_rest --help` starts the Flask server, `/get_status` returns …
exec
/bin/sh -lc "cat << 'ENDOFJSON'
{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 12, \"errors\": [{\"…
ENDOFJSON" in /work/repo
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 12, "errors": [{"msg": "PE…
`vectordb-bench` installed and verified. 247 tests pass, CLI works, REST API starts. Fixed 6 issues…
2026-10-10T02:27:53.449943Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
tokens used
207,659
`vectordb-bench` installed and verified. 247 tests pass, CLI works, REST API starts. Fixed 6 issues…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 12 minutes.
  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.28
Argusic Runner1/3Did not run20.000.30

Topics (from GitHub)

benchmarkcost-effectivenessperformancevector-databasevector-searchvectordb

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/VectorDBBench.svg)](https://argusic.com/subject/vectordbbench)

Questions

Does VectorDBBench run?
Yes. VectorDBBench runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test VectorDBBench?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1760db148b95. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test VectorDBBench?
The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does VectorDBBench take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does VectorDBBench need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing VectorDBBench?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for VectorDBBench?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion