Consolidated benchmark

This report is kept as written. Statements the run pages mark as false, misleading or unbacked are printed here unmarked; the corrections are on those run pages and in the summary's list. Summary and all runs

Report text as it was written, kept for the record

item	value
created (UTC)	2026-10-05T11:41:53Z
command	`consolidate --targets sql,sql-diskann,qdrant,qdrant-hnsw,pgvector,mariadb,oracle,redis,mongodb,clickhouse,milvus,weaviate,chroma,elasticsearch,opensearch,typesense,vespa,duckdb,sqlitevec --runs ~/ForClaude/GenericVectorBuilder/bench-results/20261005-073329-eshoponweb,~/ForClaude/GenericVectorBuilder/bench-results/20261005-085448-eshoponweb,~/ForClaude/GenericVectorBuilder/bench-results/20261005-101815-eshoponweb --out ~/ForClaude/GenericVectorBuilder/bench-results/published-2026-10-05b`
targets	19
runs used	3
runs dropped	0
pipeline	eshoponweb
benchmark command (every run)	run-all
host	bench-host
rows x dimension	524 x 1024
queries	golden, 20
top	10
concurrency	1, 8
seconds per level	20
build configuration	Release
machine control	on
CPU governor	performance
CPU partition	client 0-1,4-5; engines 2-3,6-7
warm-up searches before each timed pass	20
exact mode seconds	60

Runs used

run	started (UTC)	runSeed	load average	targetOrder
20261005-073329-eshoponweb	2026-10-05T07:33:29Z	601	1.98 5.18 4.13	qdrant-hnsw, milvus, oracle, weaviate, clickhouse, sqlitevec, mongodb, sql, elasticsearch, duckdb, chroma, opensearch, vespa, typesense, qdrant, mariadb, redis, pgvector, sql-diskann
20261005-085448-eshoponweb	2026-10-05T08:54:48Z	602	3.32 2.91 3.31	sql, opensearch, pgvector, duckdb, milvus, sqlitevec, qdrant-hnsw, typesense, qdrant, oracle, weaviate, sql-diskann, chroma, redis, vespa, mariadb, elasticsearch, clickhouse, mongodb
20261005-101815-eshoponweb	2026-10-05T10:18:15Z	603	1.45 3.00 3.58	sql, opensearch, duckdb, mongodb, chroma, mariadb, qdrant-hnsw, typesense, clickhouse, qdrant, pgvector, vespa, sqlitevec, sql-diskann, milvus, elasticsearch, redis, weaviate, oracle

Runs dropped

(none)

Targets not in this report

(none)

Targets

target	hosting	engine	index	search settings
sql	compose	Microsoft SQL Server 2025 (RTM-CU9) (KB5122048) - 17.0.5005.3 (X64), Enterprise Developer Edition (64-bit), in container gvb-mssql (image mcr.microsoft.com/mssql/server:2025-CU9-ubuntu-24.04@sha256:2b5b581621126574f3d1f75e78d3eebe8d05aedb59ad0cfdf9aa42cb0634d726; cpuset 2-3,6-7 from its creation; SQL Server counts 4 CPU(s) and runs 4 visible scheduler(s), affinity AUTO)	exact VECTOR_DISTANCE cosine, no vector index (full scan)	description=exact VECTOR_DISTANCE cosine, no vector index (full scan)
sql-diskann	compose	Microsoft SQL Server 2025 (RTM-CU9) (KB5122048) - 17.0.5005.3 (X64), Enterprise Developer Edition (64-bit), in container gvb-mssql (image mcr.microsoft.com/mssql/server:2025-CU9-ubuntu-24.04@sha256:2b5b581621126574f3d1f75e78d3eebe8d05aedb59ad0cfdf9aa42cb0634d726; cpuset 2-3,6-7 from its creation; SQL Server counts 4 CPU(s) and runs 4 visible scheduler(s), affinity AUTO)	DiskANN (preview) via VECTOR_SEARCH, cosine, build {"StartId":"306", "L":"48", "M":"8", "R":"48"}; the exact mode scans the same table	L=48, M=8, R=48, StartId=306
qdrant	compose	Qdrant 1.17.0 in container gvb-qdrant (image qdrant/qdrant:v1.17.0@sha256:f1c7272cdac52b38c1a0e89313922d940ba50afd90d593a1605dbbc214e66ffb; cpuset 2-3,6-7 from its creation; 3 search thread(s))	exact scan: the builder's sink sends exact=true on every search, so no HNSW graph is used whether or not Qdrant has built one (see the index state)	exact=true
qdrant-hnsw	compose	Qdrant 1.17.0 in container gvb-qdrant (image qdrant/qdrant:v1.17.0@sha256:f1c7272cdac52b38c1a0e89313922d940ba50afd90d593a1605dbbc214e66ffb; cpuset 2-3,6-7 from its creation; 3 search thread(s))	HNSW m=16 ef_construct=100, hnsw_ef=server default, cosine; indexing_threshold_kb 1 and full_scan_threshold_kb 10 (server defaults are 10,000 each) so a small collection builds and walks its graph	ef_construct=100, hnsw_ef=server, m=16
pgvector	compose	PostgreSQL 17 + pgvector 0.8.7	HNSW vector_cosine_ops m=16 ef_construction=128, hnsw.ef_search=100 per query, float32 vector(n), cosine; exact mode = same query with index scans off (sequential scan)	ef_construction=128, hnsw.ef_search=100, m=16
mariadb	compose	MariaDB 11.8.9 (InnoDB + VECTOR INDEX)	VECTOR INDEX (HNSW variant) DISTANCE=cosine, M=16 (no ef_construction setting exists), mhnsw_ef_search=100 per statement (the ef 100 most engines here use, so the search effort matches; MariaDB's own default is 20; recall@10 at ef 100 falls as the set grows (random 1024-dimension vectors, measured 2026-10-04: 0.99 at 524, 0.89 to 0.92 at 2,000; an earlier run gave about 0.09 at 100,000)), mhnsw_max_cache_size 4G; exact mode = IGNORE INDEX full scan	DISTANCE=cosine, M=16, mhnsw_ef_search=100
oracle	compose	Oracle AI Database Free 23.26 (23ai line, VECTOR FLOAT32)	HNSW in-memory neighbor graph NEIGHBORS=16 EFCONSTRUCTION=128, EFSEARCH=100 per query, cosine; exact mode = FETCH EXACT FIRST (full scan); Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit)	EFCONSTRUCTION=128, EFSEARCH=100, NEIGHBORS=16
redis	compose	Redis 8.10.2 (query engine, HASH + vector index)	HNSW TYPE FLOAT32 M=16 EF_CONSTRUCTION=128, EF_RUNTIME=100 per query, cosine; exact mode = FLAT index built on first exact query	EF_CONSTRUCTION=128, EF_RUNTIME=100, M=16
mongodb	compose	MongoDB 8.0.32 Atlas Local (mongod + mongot Vector Search)	vectorSearch index, HNSW maxEdges=16 numEdgeCandidates=128, float32 binData, cosine, numCandidates=20x hits (min 100); exact mode = $vectorSearch exact:true	maxEdges=16, numCandidates=20x, numEdgeCandidates=128
clickhouse	compose	ClickHouse 26.3.39.7 (MergeTree + vector_similarity index)	vector_similarity HNSW cosineDistance, quantization bf16, M=16 ef_construction=128, hnsw_candidate_list_size_for_search=256, rescoring off; exact mode = full scan with skip indexes off	M=16, ef_construction=128, hnsw_candidate_list_size_for_search=256
milvus	compose	Milvus 2.6.25 (standalone, embedded etcd, local storage, REST API v2)	HNSW M=16 efConstruction=128, ef=100, metric COSINE, Strong consistency searches; approximate only (no exact mode)	M=16, ef=100, efConstruction=128
weaviate	compose	Weaviate 1.39.8 (single node, REST + GraphQL)	HNSW maxConnections(M)=16 efConstruction=128, ef=-1 (dynamic: limit x 8 clamped 100..500), cosine, no quantization; approximate only (no exact mode)	ef=-1, efConstruction=128
chroma	compose	Chroma 1.4.4 (single node, REST API v2)	HNSW M=16 ef_construction=128, ef_search=100 (Chroma default), cosine; approximate only (no exact mode)	M=16, ef_construction=128, ef_search=100
elasticsearch	compose	Elasticsearch 9.5.3 (dense_vector)	HNSW float32, no quantization, m=16, ef_construction=128, cosine; search k=top, num_candidates=100; 1 shard, 0 replicas; force-merged to one segment after the load (at 1,024 dimensions a segment under 1,043 vectors gets no graph)	ef_construction=128, k=top, m=16, num_candidates=100
opensearch	compose	OpenSearch 3.9.0 (k-NN plugin, faiss)	faiss HNSW float32, no compression, m=16, ef_construction=128, cosinesimil; search k=top, ef_search=100; 1 shard, 0 replicas; graph built at any segment size (approximate_threshold=0); force-merged to one segment after the load	approximate_threshold=0, ef_construction=128, ef_search=100, k=top, m=16
typesense	compose	Typesense 30.2 (vector search)	HNSW float32 (hnswlib), m=16, ef_construction=128, cosine; search k=top, ef=100; exact mode = filter ordinal:>=0 with flat_search_cutoff; index held in memory	ef=100, ef_construction=128, k=top, m=16
vespa	compose	Vespa 8.754.14 (tensor attribute + HNSW)	HNSW float32 tensor, prenormalized-angular (cosine), max-links-per-node=16, neighbors-to-explore-at-insert=128; search targetHits=top, ef=100 via exploreAdditionalHits; exact mode = approximate:false; vectors held in memory	ef=100, max-links-per-node=16, neighbors-to-explore-at-insert=128, targetHits=top
duckdb	embedded	DuckDB 1.5.6 + vss b833341 (HNSW, embedded, in process)	HNSW (vss extension) FLOAT[n] metric=cosine m=16 ef_construction=128, ef_search=100 per connection, persistent (hnsw_enable_experimental_persistence=true, checkpoint_threshold=256MB); exact mode = array_cosine_similarity sequential scan; score = 1 - cosine distance; searches run concurrently, one connection per searcher (opened as searchers arrive, at most 32), writes run one at a time and never overlap a search	checkpoint_threshold=256MB, ef_construction=128, ef_search=100, hnsw_enable_experimental_persistence=true, m=16, metric=cosine
sqlitevec	embedded	SQLite 3.53.3 + sqlite-vec 0.1.7-alpha.2.1 (vec0, embedded, in process)	vec0 brute-force scan, no ANN index (exact), float32, cosine distance, default chunk_size=1024; score = 1 - cosine distance; searches run concurrently, one WAL reader connection per searcher (opened as searchers arrive, at most 32), writes run one at a time and may overlap searches	chunk_size=1024

Request speed on a small collection (524 vectors)

Measured end to end through each engine's .NET client; at this size it reflects per-request cost including the client library, not index scaling.

Engines in different bands never overlap: every run of an engine in a faster band beat every run of an engine in a slower band, and the medians on either side of a band boundary are at least 3% apart. Engines in one band are linked by overlapping slowest-to-fastest ranges or by neighboring medians less than 3% apart (an engine varies about 2% from run to run), so these runs do not separate them cleanly. Inside a band they are listed by median, and that order is not a ranking.

p50 latency, one search at a time (lower is faster)

band	target	median [min, max]	client CPU ms/search	runs	engine notes
1	redis	0.37 [0.36, 0.37]	0.55 [0.54, 0.55]	3	-
2	mariadb	0.62 [0.62, 0.63]	0.49 [0.47, 0.49]	3	-
3	pgvector	0.85 [0.82, 0.85]	0.68 [0.66, 0.68]	3	-
4	qdrant	0.88 [0.88, 0.88]	0.74 [0.72, 0.74]	3	exact-by-design
4	oracle	0.89 [0.88, 0.90]	0.87 [0.85, 0.87]	3	cpu-cap
5	qdrant-hnsw	0.92 [0.90, 0.92]	0.73 [0.72, 0.73]	3	-
6	elasticsearch	1.31 [1.30, 1.31]	0.46 [0.45, 0.46]	3	scans-all-vectors
7	mongodb	1.39 [1.39, 1.41]	0.30 [0.30, 0.31]	3	-
8	sqlitevec	1.82 [1.81, 1.85]	1.93 [1.93, 1.97]	3	exact-by-design
8	vespa	1.85 [1.83, 1.86]	0.94 [0.92, 0.94]	3	-
9	opensearch	1.99 [1.96, 2.00]	0.46 [0.45, 0.46]	3	-
9	chroma	2.03 [2.02, 2.03]	0.46 [0.45, 0.47]	3	-
10	milvus	2.21 [2.16, 2.22]	0.55 [0.54, 0.55]	3	-
11	duckdb	3.52 [3.51, 3.53]	4.84 [4.84, 4.84]	3	-
11	sql-diskann	3.60 [3.56, 3.62]	1.01 [1.00, 1.03]	3	-
12	sql	3.89 [3.82, 3.89]	1.18 [1.18, 1.19]	3	exact-by-design
13	typesense	4.04 [4.03, 4.04]	0.51 [0.50, 0.52]	3	-
14	clickhouse	4.50 [4.50, 4.51]	0.82 [0.82, 0.83]	3	-
15	weaviate	5.19 [5.18, 5.19]	0.57 [0.57, 0.59]	3	-

QPS with 8 searchers at once (higher is faster)

band	target	median [min, max]	client CPU ms/search	runs	engine notes
1	mariadb	5940.1 [5930.1, 5944.2]	0.38 [0.38, 0.38]	3	-
2	redis	5074.5 [5039.1, 5132.7]	0.36 [0.36, 0.37]	3	-
3	pgvector	4050.0 [4007.6, 4142.5]	0.54 [0.53, 0.54]	3	-
4	qdrant-hnsw	3465.9 [3453.8, 3473.2]	0.52 [0.51, 0.52]	3	-
5	qdrant	3295.5 [3291.4, 3303.0]	0.53 [0.53, 0.53]	3	exact-by-design
6	oracle	2879.2 [2826.3, 2896.5]	0.64 [0.64, 0.65]	3	cpu-cap
7	elasticsearch	2706.6 [2697.5, 2713.2]	0.49 [0.49, 0.50]	3	scans-all-vectors
8	mongodb	2088.9 [2088.1, 2102.4]	0.29 [0.29, 0.29]	3	-
9	vespa	1560.0 [1539.8, 1595.2]	0.88 [0.86, 0.88]	3	-
9	opensearch	1528.2 [1511.9, 1539.4]	0.51 [0.49, 0.51]	3	-
10	milvus	1285.1 [1281.5, 1290.5]	0.63 [0.62, 0.63]	3	-
11	sqlitevec	1158.9 [1150.7, 1161.4]	3.45 [3.44, 3.47]	3	exact-by-design
12	chroma	806.9 [804.4, 807.5]	0.46 [0.45, 0.46]	3	-
13	sql-diskann	690.4 [690.4, 690.7]	1.09 [1.07, 1.10]	3	-
14	sql	613.9 [612.5, 621.4]	1.18 [1.18, 1.19]	3	exact-by-design
14	duckdb	598.5 [596.6, 601.9]	6.64 [6.61, 6.66]	3	-
14	typesense	591.3 [590.9, 593.7]	0.57 [0.56, 0.58]	3	-
15	clickhouse	492.8 [479.8, 495.8]	1.02 [1.02, 1.02]	3	-
16	weaviate	312.1 [312.1, 312.2]	0.60 [0.60, 0.60]	3	-

QPS with one searcher (higher is faster)

band	target	median [min, max]	client CPU ms/search	runs	engine notes
1	redis	2620.4 [2594.8, 2653.9]	0.55 [0.54, 0.55]	3	-
2	mariadb	1573.4 [1569.4, 1581.5]	0.49 [0.47, 0.49]	3	-
3	pgvector	1153.4 [1150.9, 1200.4]	0.68 [0.66, 0.68]	3	-
3	qdrant	1122.7 [1122.0, 1125.4]	0.74 [0.72, 0.74]	3	exact-by-design
3	oracle	1096.8 [1089.1, 1103.8]	0.87 [0.85, 0.87]	3	cpu-cap
3	qdrant-hnsw	1074.8 [1073.1, 1093.0]	0.73 [0.72, 0.73]	3	-
4	elasticsearch	751.0 [750.6, 754.5]	0.46 [0.45, 0.46]	3	scans-all-vectors
5	mongodb	703.9 [693.7, 705.0]	0.30 [0.30, 0.31]	3	-
6	sqlitevec	542.2 [529.8, 543.7]	1.93 [1.93, 1.97]	3	exact-by-design
7	vespa	524.0 [522.7, 527.0]	0.94 [0.92, 0.94]	3	-
8	opensearch	495.2 [494.1, 497.2]	0.46 [0.45, 0.46]	3	-
8	chroma	487.6 [486.3, 489.9]	0.46 [0.45, 0.47]	3	-
9	milvus	430.1 [428.8, 440.8]	0.55 [0.54, 0.55]	3	-
10	duckdb	280.9 [280.6, 282.1]	4.84 [4.84, 4.84]	3	-
10	sql-diskann	273.4 [272.5, 276.4]	1.01 [1.00, 1.03]	3	-
11	sql	250.7 [249.9, 255.6]	1.18 [1.18, 1.19]	3	exact-by-design
11	typesense	244.1 [243.8, 245.0]	0.51 [0.50, 0.52]	3	-
12	clickhouse	214.7 [214.7, 215.2]	0.82 [0.82, 0.83]	3	-
13	weaviate	171.2 [171.2, 171.6]	0.57 [0.57, 0.59]	3	-

Client CPU per search is the CPU time the test's .NET client itself used for each search, measured in the same pass as the figure beside it.

Per-engine notes

target	kind	note	source
sql	exact-by-design	Exact by design: every search compares the query with every stored vector, so its time grows with the collection and index quality plays no part in its speed. The results say: no index used, exact scan by design.	results
qdrant	exact-by-design	Exact by design: every search compares the query with every stored vector, so its time grows with the collection and index quality plays no part in its speed. The results say: no index used, exact scan by design (the builder's sink sends exact=true on every search).	results
oracle	cpu-cap	The engine cannot use more CPUs than its own cap, whatever it is pinned to. The results say: Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit).	results
oracle	flags	unsettled-target (evidence under Flags)	results
redis	flags	unsettled-target (evidence under Flags)	results
mongodb	flags	segment-layout-differs-between-runs (evidence under Flags)	results
clickhouse	flags	unsettled-target (evidence under Flags)	results
elasticsearch	scans-all-vectors	No index graph was built at this size: its searches scanned all 524 vectors, so its default search equals its exact search. The results say: NO HNSW GRAPH, searches scan all 524 vectors.	results
elasticsearch	flags	index-not-ready-after-load, index-not-ready-after-search (evidence under Flags)	results
duckdb	flags	client-engine-share-cores (evidence under Flags)	results
sqlitevec	exact-by-design	Exact by design: every search compares the query with every stored vector, so its time grows with the collection and index quality plays no part in its speed. The results say: vec0 brute-force scan, no ANN index (exact), float32, cosine distance, default chunk_size=1024; score = 1 - cosine distance; searches run concurrently, one WAL reader connection per searcher (opened as searchers arrive, at most 32), writes run one at a time and may overlap searches.	results
sqlitevec	flags	client-engine-share-cores (evidence under Flags)	results

Per target: median [min, max]

target	n	p50 ms	p95 ms	QPS@1	QPS@8	QPS ratio 8/1	client CPU ms/search@1	client CPU ms/search@8	load rows/s (not ranked)	recall@10	nDCG@10	exact p50 ms
sql	3	3.89 [3.82, 3.89]	4.48 [4.35, 4.51]	250.7 [249.9, 255.6]	613.9 [612.5, 621.4]	2.45 [2.40, 2.48]	1.18 [1.18, 1.19]	1.18 [1.18, 1.19]	575 [563, 601]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	-
sql-diskann	3	3.60 [3.56, 3.62]	4.06 [4.06, 4.08]	273.4 [272.5, 276.4]	690.4 [690.4, 690.7]	2.53 [2.50, 2.53]	1.01 [1.00, 1.03]	1.09 [1.07, 1.10]	637 [630, 637]	0.965 [0.965, 0.965]	0.526 [0.526, 0.526]	3.56 [3.55, 3.58]
qdrant	3	0.88 [0.88, 0.88]	0.99 [0.99, 0.99]	1122.7 [1122.0, 1125.4]	3295.5 [3291.4, 3303.0]	2.93 [2.93, 2.94]	0.74 [0.72, 0.74]	0.53 [0.53, 0.53]	9285 [8597, 9365]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	-
qdrant-hnsw	3	0.92 [0.90, 0.92]	1.03 [1.01, 1.03]	1074.8 [1073.1, 1093.0]	3465.9 [3453.8, 3473.2]	3.21 [3.18, 3.23]	0.73 [0.72, 0.73]	0.52 [0.51, 0.52]	5186 [4928, 5446]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	0.89 [0.88, 0.90]
pgvector	3	0.85 [0.82, 0.85]	1.00 [0.95, 1.00]	1153.4 [1150.9, 1200.4]	4050.0 [4007.6, 4142.5]	3.47 [3.45, 3.52]	0.68 [0.66, 0.68]	0.54 [0.53, 0.54]	612 [611, 616]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	2.17 [2.17, 2.18]
mariadb	3	0.62 [0.62, 0.63]	0.71 [0.70, 0.71]	1573.4 [1569.4, 1581.5]	5940.1 [5930.1, 5944.2]	3.78 [3.76, 3.78]	0.49 [0.47, 0.49]	0.38 [0.38, 0.38]	1039 [1020, 1052]	1.000 [0.995, 1.000]	0.518 [0.518, 0.518]	1.58 [1.58, 1.58]
oracle	3	0.89 [0.88, 0.90]	1.06 [1.05, 1.07]	1096.8 [1089.1, 1103.8]	2879.2 [2826.3, 2896.5]	2.61 [2.58, 2.66]	0.87 [0.85, 0.87]	0.64 [0.64, 0.65]	2007 [1938, 2020]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	2.37 [2.36, 2.38]
redis	3	0.37 [0.36, 0.37]	0.47 [0.47, 0.48]	2620.4 [2594.8, 2653.9]	5074.5 [5039.1, 5132.7]	1.94 [1.91, 1.96]	0.55 [0.54, 0.55]	0.36 [0.36, 0.37]	11834 [11414, 11939]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	0.35 [0.35, 0.36]
mongodb	3	1.39 [1.39, 1.41]	1.62 [1.61, 1.64]	703.9 [693.7, 705.0]	2088.9 [2088.1, 2102.4]	2.98 [2.97, 3.01]	0.30 [0.30, 0.31]	0.29 [0.29, 0.29]	3084 [2969, 3173]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	1.23 [1.22, 1.25]
clickhouse	3	4.50 [4.50, 4.51]	5.75 [5.55, 6.26]	214.7 [214.7, 215.2]	492.8 [479.8, 495.8]	2.30 [2.24, 2.30]	0.82 [0.82, 0.83]	1.02 [1.02, 1.02]	2977 [2520, 3361]	0.995 [0.990, 0.995]	0.528 [0.515, 0.528]	6.09 [6.06, 6.10]
milvus	3	2.21 [2.16, 2.22]	2.74 [2.67, 2.79]	430.1 [428.8, 440.8]	1285.1 [1281.5, 1290.5]	2.98 [2.93, 3.00]	0.55 [0.54, 0.55]	0.63 [0.62, 0.63]	1175 [1073, 1198]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	-
weaviate	3	5.19 [5.18, 5.19]	10.4 [10.4, 10.4]	171.2 [171.2, 171.6]	312.1 [312.1, 312.2]	1.82 [1.82, 1.82]	0.57 [0.57, 0.59]	0.60 [0.60, 0.60]	1007 [998, 1018]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	-
chroma	3	2.03 [2.02, 2.03]	2.30 [2.28, 2.33]	487.6 [486.3, 489.9]	806.9 [804.4, 807.5]	1.65 [1.65, 1.66]	0.46 [0.45, 0.47]	0.46 [0.45, 0.46]	860 [841, 895]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	-
elasticsearch	3	1.31 [1.30, 1.31]	1.48 [1.48, 1.49]	751.0 [750.6, 754.5]	2706.6 [2697.5, 2713.2]	3.59 [3.59, 3.61]	0.46 [0.45, 0.46]	0.49 [0.49, 0.50]	543 [442, 545]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	1.25 [1.25, 1.26]
opensearch	3	1.99 [1.96, 2.00]	2.24 [2.24, 2.25]	495.2 [494.1, 497.2]	1528.2 [1511.9, 1539.4]	3.09 [3.06, 3.10]	0.46 [0.45, 0.46]	0.51 [0.49, 0.51]	405 [388, 421]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	2.58 [2.56, 2.63]
typesense	3	4.04 [4.03, 4.04]	4.38 [4.36, 4.39]	244.1 [243.8, 245.0]	591.3 [590.9, 593.7]	2.42 [2.42, 2.42]	0.51 [0.50, 0.52]	0.57 [0.56, 0.58]	1040 [838, 1043]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	5.46 [5.46, 5.48]
vespa	3	1.85 [1.83, 1.86]	2.27 [2.26, 2.31]	524.0 [522.7, 527.0]	1560.0 [1539.8, 1595.2]	2.98 [2.94, 3.03]	0.94 [0.92, 0.94]	0.88 [0.86, 0.88]	288 [276, 322]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	1.84 [1.84, 1.85]
duckdb	3	3.52 [3.51, 3.53]	3.92 [3.87, 3.92]	280.9 [280.6, 282.1]	598.5 [596.6, 601.9]	2.13 [2.13, 2.13]	4.84 [4.84, 4.84]	6.64 [6.61, 6.66]	1559 [1546, 1574]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	4.02 [3.99, 4.04]
sqlitevec	3	1.82 [1.81, 1.85]	2.04 [2.04, 2.12]	542.2 [529.8, 543.7]	1158.9 [1150.7, 1161.4]	2.14 [2.13, 2.17]	1.93 [1.93, 1.97]	3.45 [3.44, 3.47]	4690 [4041, 5046]	1.000 [1.000, 1.000]	0.518 [0.518, 0.518]	1.83 [1.81, 1.85]

Per run: p50 ms

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	median
sql	3.89	3.82	3.89	3.89
sql-diskann	3.60	3.56	3.62	3.60
qdrant	0.88	0.88	0.88	0.88
qdrant-hnsw	0.90	0.92	0.92	0.92
pgvector	0.85	0.82	0.85	0.85
mariadb	0.63	0.62	0.62	0.62
oracle	0.88	0.90	0.89	0.89
redis	0.36	0.37	0.37	0.37
mongodb	1.39	1.41	1.39	1.39
clickhouse	4.50	4.51	4.50	4.50
milvus	2.16	2.22	2.21	2.21
weaviate	5.19	5.18	5.19	5.19
chroma	2.03	2.03	2.02	2.03
elasticsearch	1.30	1.31	1.31	1.31
opensearch	1.99	2.00	1.96	1.99
typesense	4.04	4.04	4.03	4.04
vespa	1.85	1.86	1.83	1.85
duckdb	3.53	3.52	3.51	3.52
sqlitevec	1.82	1.85	1.81	1.82

Per run: QPS@1

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	median
sql	250.7	255.6	249.9	250.7
sql-diskann	272.5	276.4	273.4	273.4
qdrant	1125.4	1122.0	1122.7	1122.7
qdrant-hnsw	1093.0	1074.8	1073.1	1074.8
pgvector	1153.4	1200.4	1150.9	1153.4
mariadb	1569.4	1581.5	1573.4	1573.4
oracle	1103.8	1089.1	1096.8	1096.8
redis	2653.9	2620.4	2594.8	2620.4
mongodb	705.0	693.7	703.9	703.9
clickhouse	215.2	214.7	214.7	214.7
milvus	440.8	430.1	428.8	430.1
weaviate	171.2	171.6	171.2	171.2
chroma	487.6	486.3	489.9	487.6
elasticsearch	754.5	751.0	750.6	751.0
opensearch	495.2	494.1	497.2	495.2
typesense	244.1	243.8	245.0	244.1
vespa	524.0	522.7	527.0	524.0
duckdb	280.6	280.9	282.1	280.9
sqlitevec	542.2	529.8	543.7	542.2

Per run: QPS@8

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	median
sql	621.4	613.9	612.5	613.9
sql-diskann	690.4	690.7	690.4	690.4
qdrant	3303.0	3291.4	3295.5	3295.5
qdrant-hnsw	3473.2	3453.8	3465.9	3465.9
pgvector	4007.6	4142.5	4050.0	4050.0
mariadb	5930.1	5940.1	5944.2	5940.1
oracle	2879.2	2896.5	2826.3	2879.2
redis	5074.5	5132.7	5039.1	5074.5
mongodb	2102.4	2088.1	2088.9	2088.9
clickhouse	495.8	492.8	479.8	492.8
milvus	1290.5	1281.5	1285.1	1285.1
weaviate	312.2	312.1	312.1	312.1
chroma	804.4	806.9	807.5	806.9
elasticsearch	2706.6	2713.2	2697.5	2706.6
opensearch	1528.2	1511.9	1539.4	1528.2
typesense	591.3	590.9	593.7	591.3
vespa	1539.8	1560.0	1595.2	1560.0
duckdb	596.6	598.5	601.9	598.5
sqlitevec	1161.4	1150.7	1158.9	1158.9

Per run: QPS ratio 8/1

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	median
sql	2.48	2.40	2.45	2.45
sql-diskann	2.53	2.50	2.53	2.53
qdrant	2.93	2.93	2.94	2.93
qdrant-hnsw	3.18	3.21	3.23	3.21
pgvector	3.47	3.45	3.52	3.47
mariadb	3.78	3.76	3.78	3.78
oracle	2.61	2.66	2.58	2.61
redis	1.91	1.96	1.94	1.94
mongodb	2.98	3.01	2.97	2.98
clickhouse	2.30	2.30	2.24	2.30
milvus	2.93	2.98	3.00	2.98
weaviate	1.82	1.82	1.82	1.82
chroma	1.65	1.66	1.65	1.65
elasticsearch	3.59	3.61	3.59	3.59
opensearch	3.09	3.06	3.10	3.09
typesense	2.42	2.42	2.42	2.42
vespa	2.94	2.98	3.03	2.98
duckdb	2.13	2.13	2.13	2.13
sqlitevec	2.14	2.17	2.13	2.14

Per run: client CPU ms per search@1

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	median
sql	1.189	1.182	1.181	1.182
sql-diskann	1.026	0.998	1.007	1.007
qdrant	0.724	0.736	0.736	0.736
qdrant-hnsw	0.716	0.729	0.733	0.729
pgvector	0.681	0.665	0.683	0.681
mariadb	0.470	0.486	0.487	0.486
oracle	0.853	0.868	0.870	0.868
redis	0.538	0.547	0.554	0.547
mongodb	0.305	0.308	0.303	0.305
clickhouse	0.826	0.815	0.819	0.819
milvus	0.546	0.547	0.544	0.546
weaviate	0.567	0.573	0.587	0.573
chroma	0.466	0.454	0.456	0.456
elasticsearch	0.459	0.461	0.449	0.459
opensearch	0.458	0.456	0.451	0.456
typesense	0.515	0.505	0.507	0.507
vespa	0.941	0.936	0.920	0.936
duckdb	4.838	4.837	4.843	4.838
sqlitevec	1.932	1.974	1.928	1.932

Per run: client CPU ms per search@8

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	median
sql	1.186	1.181	1.177	1.181
sql-diskann	1.095	1.088	1.068	1.088
qdrant	0.525	0.535	0.534	0.534
qdrant-hnsw	0.513	0.524	0.521	0.521
pgvector	0.540	0.531	0.539	0.539
mariadb	0.381	0.378	0.378	0.378
oracle	0.637	0.644	0.649	0.644
redis	0.364	0.361	0.368	0.364
mongodb	0.292	0.293	0.286	0.292
clickhouse	1.022	1.019	1.023	1.022
milvus	0.625	0.630	0.631	0.630
weaviate	0.604	0.603	0.599	0.603
chroma	0.453	0.458	0.456	0.456
elasticsearch	0.491	0.496	0.489	0.491
opensearch	0.508	0.507	0.495	0.507
typesense	0.577	0.564	0.569	0.569
vespa	0.882	0.877	0.863	0.877
duckdb	6.665	6.638	6.609	6.638
sqlitevec	3.438	3.466	3.446	3.446

Rank per run: p50 (1 = lowest)

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	band
sql	16	16	16	12
sql-diskann	15	15	15	11
qdrant	4	4	4	4
qdrant-hnsw	6	6	6	5
pgvector	3	3	3	3
mariadb	2	2	2	2
oracle	5	5	5	4
redis	1	1	1	1
mongodb	8	8	8	7
clickhouse	18	18	18	14
milvus	13	13	13	10
weaviate	19	19	19	15
chroma	12	12	12	9
elasticsearch	7	7	7	6
opensearch	11	11	11	9
typesense	17	17	17	13
vespa	10	10	10	8
duckdb	14	14	14	11
sqlitevec	9	9	9	8

Rank per run: QPS@8 (1 = highest)

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	band
sql	15	15	15	14
sql-diskann	14	14	14	13
qdrant	5	5	5	5
qdrant-hnsw	4	4	4	4
pgvector	3	3	3	3
mariadb	1	1	1	1
oracle	6	6	6	6
redis	2	2	2	2
mongodb	8	8	8	8
clickhouse	18	18	18	15
milvus	11	11	11	10
weaviate	19	19	19	16
chroma	13	13	13	12
elasticsearch	7	7	7	7
opensearch	10	10	10	9
typesense	17	17	17	14
vespa	9	9	9	9
duckdb	16	16	16	14
sqlitevec	12	12	12	11

Rank per run: QPS@1 (1 = highest)

target	20261005-073329-eshoponweb	20261005-085448-eshoponweb	20261005-101815-eshoponweb	band
sql	16	16	16	11
sql-diskann	15	15	15	10
qdrant	4	4	4	3
qdrant-hnsw	6	6	6	3
pgvector	3	3	3	3
mariadb	2	2	2	2
oracle	5	5	5	3
redis	1	1	1	1
mongodb	8	8	8	5
clickhouse	18	18	18	12
milvus	13	13	13	9
weaviate	19	19	19	13
chroma	12	12	12	8
elasticsearch	7	7	7	4
opensearch	11	11	11	8
typesense	17	17	17	11
vespa	10	10	10	7
duckdb	14	14	14	10
sqlitevec	9	9	9	6

Paired per run: exact p50 / default p50

target	run	default p50 ms	exact p50 ms	exact - default ms	exact / default	exact recall	exact pass before default@1
sql-diskann	20261005-073329-eshoponweb	3.60	3.55	-0.06	0.985	1.000	no
sql-diskann	20261005-085448-eshoponweb	3.56	3.56	-0.00	1.000	1.000	yes
sql-diskann	20261005-101815-eshoponweb	3.62	3.58	-0.04	0.989	1.000	no
qdrant-hnsw	20261005-073329-eshoponweb	0.90	0.88	-0.02	0.978	1.000	no
qdrant-hnsw	20261005-085448-eshoponweb	0.92	0.90	-0.02	0.976	1.000	yes
qdrant-hnsw	20261005-101815-eshoponweb	0.92	0.89	-0.03	0.969	1.000	yes
pgvector	20261005-073329-eshoponweb	0.85	2.18	1.33	2.570	1.000	yes
pgvector	20261005-085448-eshoponweb	0.82	2.17	1.35	2.655	1.000	no
pgvector	20261005-101815-eshoponweb	0.85	2.17	1.32	2.555	1.000	yes
mariadb	20261005-073329-eshoponweb	0.63	1.58	0.95	2.524	1.000	yes
mariadb	20261005-085448-eshoponweb	0.62	1.58	0.96	2.546	1.000	no
mariadb	20261005-101815-eshoponweb	0.62	1.58	0.96	2.533	1.000	no
oracle	20261005-073329-eshoponweb	0.88	2.37	1.49	2.684	1.000	yes
oracle	20261005-085448-eshoponweb	0.90	2.38	1.48	2.655	1.000	yes
oracle	20261005-101815-eshoponweb	0.89	2.36	1.47	2.664	1.000	yes
redis	20261005-073329-eshoponweb	0.36	0.35	-0.01	0.978	1.000	no
redis	20261005-085448-eshoponweb	0.37	0.35	-0.02	0.938	1.000	no
redis	20261005-101815-eshoponweb	0.37	0.36	-0.02	0.957	1.000	yes
mongodb	20261005-073329-eshoponweb	1.39	1.22	-0.17	0.876	1.000	no
mongodb	20261005-085448-eshoponweb	1.41	1.25	-0.16	0.883	1.000	yes
mongodb	20261005-101815-eshoponweb	1.39	1.23	-0.17	0.881	1.000	no
clickhouse	20261005-073329-eshoponweb	4.50	6.09	1.59	1.353	1.000	yes
clickhouse	20261005-085448-eshoponweb	4.51	6.10	1.59	1.354	1.000	yes
clickhouse	20261005-101815-eshoponweb	4.50	6.06	1.56	1.347	1.000	no
elasticsearch	20261005-073329-eshoponweb	1.30	1.25	-0.05	0.958	1.000	yes
elasticsearch	20261005-085448-eshoponweb	1.31	1.25	-0.06	0.956	1.000	yes
elasticsearch	20261005-101815-eshoponweb	1.31	1.26	-0.06	0.956	1.000	yes
opensearch	20261005-073329-eshoponweb	1.99	2.58	0.58	1.294	1.000	yes
opensearch	20261005-085448-eshoponweb	2.00	2.56	0.56	1.282	1.000	yes
opensearch	20261005-101815-eshoponweb	1.96	2.63	0.67	1.342	1.000	yes
typesense	20261005-073329-eshoponweb	4.04	5.46	1.42	1.353	1.000	no
typesense	20261005-085448-eshoponweb	4.04	5.48	1.44	1.356	1.000	no
typesense	20261005-101815-eshoponweb	4.03	5.46	1.43	1.356	1.000	no
vespa	20261005-073329-eshoponweb	1.85	1.84	-0.01	0.996	1.000	yes
vespa	20261005-085448-eshoponweb	1.86	1.85	-0.01	0.995	1.000	yes
vespa	20261005-101815-eshoponweb	1.83	1.84	0.00	1.002	1.000	yes
duckdb	20261005-073329-eshoponweb	3.53	4.04	0.52	1.147	1.000	yes
duckdb	20261005-085448-eshoponweb	3.52	3.99	0.46	1.132	1.000	yes
duckdb	20261005-101815-eshoponweb	3.51	4.02	0.51	1.145	1.000	no
sqlitevec	20261005-073329-eshoponweb	1.82	1.83	0.02	1.009	1.000	no
sqlitevec	20261005-085448-eshoponweb	1.85	1.85	0.00	1.001	1.000	yes
sqlitevec	20261005-101815-eshoponweb	1.81	1.81	0.00	1.000	1.000	yes

Exact / default summary

target	n	median exact/default	min	max	median exact - default ms	runs exact slower
sql-diskann	3	0.989	0.985	1.000	-0.04	0 of 3
qdrant-hnsw	3	0.976	0.969	0.978	-0.02	0 of 3
pgvector	3	2.570	2.555	2.655	1.33	3 of 3
mariadb	3	2.533	2.524	2.546	0.96	3 of 3
oracle	3	2.664	2.655	2.684	1.48	3 of 3
redis	3	0.957	0.938	0.978	-0.02	0 of 3
mongodb	3	0.881	0.876	0.883	-0.17	0 of 3
clickhouse	3	1.353	1.347	1.354	1.59	3 of 3
elasticsearch	3	0.956	0.956	0.958	-0.06	0 of 3
opensearch	3	1.294	1.282	1.342	0.58	3 of 3
typesense	3	1.356	1.353	1.356	1.43	3 of 3
vespa	3	0.996	0.995	1.002	-0.01	1 of 3
duckdb	3	1.145	1.132	1.147	0.51	3 of 3
sqlitevec	3	1.001	1.000	1.009	0.00	3 of 3

Recorded per run: order, passes, index state, durability

target	run	order	passOrder	afterLoad ready	afterLoad indexed/total	afterLoad detail	afterSearch ready	afterSearch indexed/total	segments after load / after search	durability	load indexNote	settled	mean ms
sql	20261005-073329-eshoponweb	8	default@8, default@1	true	0/524	no index used, exact scan by design: dbo.gvb_gvbbench_eshoponweb in GvbBench holds 524 rows; sys.vector_indexes lists no index on the table; indexes: PK_gvb_gvbbench_eshoponweb CLUSTERED, IX_gvb_gvbbench_eshoponweb_DocKey NONCLUSTERED; a real search under SET STATISTICS XML ON ran: Clustered Index Scan of GvbBench.gvb_gvbbench_eshoponweb through PK_gvb_gvbbench_eshoponweb (IndexKind Clustered), 524 rows read, no vector index operator, 10 hits	true	0/524	-	A commit returns after its transaction-log records are written to disk (SQL Server write-ahead logging; delayed durability is DISABLED); a database created here copies the model database: recovery model FULL, page_verify CHECKSUM; no global trace flags are enabled; mssql.conf of container gvb-mssql (/var/opt/mssql/mssql.conf, on the host at ~/gvb-data/engines/mssql/mssql.conf) does not exist, so it sets: nothing; it has no [control] or [traceflag] entry, so SQL Server's own Linux defaults for flushing writes apply (Microsoft's Linux performance guide names trace flag 3982 as that default; read from the guide, not tested here). Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. Container settings from its environment (names only): MSSQL_AGENT_ENABLED, MSSQL_MEMORY_LIMIT_MB, MSSQL_PID, MSSQL_RPC_PORT, MSSQL_SA_PASSWORD.	-	yes	3.99 (1000 / QPS@1)
sql	20261005-085448-eshoponweb	1	default@8, default@1	true	0/524	no index used, exact scan by design: dbo.gvb_gvbbench_eshoponweb in GvbBench holds 524 rows; sys.vector_indexes lists no index on the table; indexes: PK_gvb_gvbbench_eshoponweb CLUSTERED, IX_gvb_gvbbench_eshoponweb_DocKey NONCLUSTERED; a real search under SET STATISTICS XML ON ran: Clustered Index Scan of GvbBench.gvb_gvbbench_eshoponweb through PK_gvb_gvbbench_eshoponweb (IndexKind Clustered), 524 rows read, no vector index operator, 10 hits	true	0/524	-	A commit returns after its transaction-log records are written to disk (SQL Server write-ahead logging; delayed durability is DISABLED); a database created here copies the model database: recovery model FULL, page_verify CHECKSUM; no global trace flags are enabled; mssql.conf of container gvb-mssql (/var/opt/mssql/mssql.conf, on the host at ~/gvb-data/engines/mssql/mssql.conf) does not exist, so it sets: nothing; it has no [control] or [traceflag] entry, so SQL Server's own Linux defaults for flushing writes apply (Microsoft's Linux performance guide names trace flag 3982 as that default; read from the guide, not tested here). Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. Container settings from its environment (names only): MSSQL_AGENT_ENABLED, MSSQL_MEMORY_LIMIT_MB, MSSQL_PID, MSSQL_RPC_PORT, MSSQL_SA_PASSWORD.	-	yes	3.91 (1000 / QPS@1)
sql	20261005-101815-eshoponweb	1	default@1, default@8	true	0/524	no index used, exact scan by design: dbo.gvb_gvbbench_eshoponweb in GvbBench holds 524 rows; sys.vector_indexes lists no index on the table; indexes: PK_gvb_gvbbench_eshoponweb CLUSTERED, IX_gvb_gvbbench_eshoponweb_DocKey NONCLUSTERED; a real search under SET STATISTICS XML ON ran: Clustered Index Scan of GvbBench.gvb_gvbbench_eshoponweb through PK_gvb_gvbbench_eshoponweb (IndexKind Clustered), 524 rows read, no vector index operator, 10 hits	true	0/524	-	A commit returns after its transaction-log records are written to disk (SQL Server write-ahead logging; delayed durability is DISABLED); a database created here copies the model database: recovery model FULL, page_verify CHECKSUM; no global trace flags are enabled; mssql.conf of container gvb-mssql (/var/opt/mssql/mssql.conf, on the host at ~/gvb-data/engines/mssql/mssql.conf) does not exist, so it sets: nothing; it has no [control] or [traceflag] entry, so SQL Server's own Linux defaults for flushing writes apply (Microsoft's Linux performance guide names trace flag 3982 as that default; read from the guide, not tested here). Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. Container settings from its environment (names only): MSSQL_AGENT_ENABLED, MSSQL_MEMORY_LIMIT_MB, MSSQL_PID, MSSQL_RPC_PORT, MSSQL_SA_PASSWORD.	-	yes	4.00 (1000 / QPS@1)
sql-diskann	20261005-073329-eshoponweb	19	default@1, exact, default@8	true	524/524	DiskANN index built and used. sys.vector_indexes: vix_gvb_gvbbench_eshoponweb on dbo.gvb_gvbbench_eshoponweb_ann in GvbBenchDiskAnn, DiskANN, COSINE, enabled, build {"StartId":"306", "L":"48", "M":"8", "R":"48"}; graph table rows 524 of 524 table rows. Real VECTOR_SEARCH plan: Vector Index Seek on index vix_gvb_gvbbench_eshoponweb of GvbBenchDiskAnn.gvb_gvbbench_eshoponweb_ann (IndexKind DiskANN), 10 rows returned, 10 hits. The exact mode searches the SAME table (dbo.gvb_gvbbench_eshoponweb_ann, database GvbBenchDiskAnn) and its real plan is: Clustered Index Scan of GvbBenchDiskAnn.gvb_gvbbench_eshoponweb_ann through PK_gvb_gvbbench_eshoponweb_ann (IndexKind Clustered), 524 rows read, no vector index operator, 10 hits	true	524/524	-	A commit returns after its transaction-log records are written to disk (SQL Server write-ahead logging; delayed durability is DISABLED); a database created here copies the model database: recovery model FULL, page_verify CHECKSUM; no global trace flags are enabled; mssql.conf of container gvb-mssql (/var/opt/mssql/mssql.conf, on the host at ~/gvb-data/engines/mssql/mssql.conf) does not exist, so it sets: nothing; it has no [control] or [traceflag] entry, so SQL Server's own Linux defaults for flushing writes apply (Microsoft's Linux performance guide names trace flag 3982 as that default; read from the guide, not tested here). Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. Container settings from its environment (names only): MSSQL_AGENT_ENABLED, MSSQL_MEMORY_LIMIT_MB, MSSQL_PID, MSSQL_RPC_PORT, MSSQL_SA_PASSWORD.	copied 524 rows to dbo.gvb_gvbbench_eshoponweb_ann (INT key) and built DiskANN, parameters {"StartId":"306", "L":"48", "M":"8", "R":"48"}, graph covers 524 rows	yes	3.67 (1000 / QPS@1)
sql-diskann	20261005-085448-eshoponweb	12	exact, default@8, default@1	true	524/524	DiskANN index built and used. sys.vector_indexes: vix_gvb_gvbbench_eshoponweb on dbo.gvb_gvbbench_eshoponweb_ann in GvbBenchDiskAnn, DiskANN, COSINE, enabled, build {"StartId":"306", "L":"48", "M":"8", "R":"48"}; graph table rows 524 of 524 table rows. Real VECTOR_SEARCH plan: Vector Index Seek on index vix_gvb_gvbbench_eshoponweb of GvbBenchDiskAnn.gvb_gvbbench_eshoponweb_ann (IndexKind DiskANN), 10 rows returned, 10 hits. The exact mode searches the SAME table (dbo.gvb_gvbbench_eshoponweb_ann, database GvbBenchDiskAnn) and its real plan is: Clustered Index Scan of GvbBenchDiskAnn.gvb_gvbbench_eshoponweb_ann through PK_gvb_gvbbench_eshoponweb_ann (IndexKind Clustered), 524 rows read, no vector index operator, 10 hits	true	524/524	-	A commit returns after its transaction-log records are written to disk (SQL Server write-ahead logging; delayed durability is DISABLED); a database created here copies the model database: recovery model FULL, page_verify CHECKSUM; no global trace flags are enabled; mssql.conf of container gvb-mssql (/var/opt/mssql/mssql.conf, on the host at ~/gvb-data/engines/mssql/mssql.conf) does not exist, so it sets: nothing; it has no [control] or [traceflag] entry, so SQL Server's own Linux defaults for flushing writes apply (Microsoft's Linux performance guide names trace flag 3982 as that default; read from the guide, not tested here). Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. Container settings from its environment (names only): MSSQL_AGENT_ENABLED, MSSQL_MEMORY_LIMIT_MB, MSSQL_PID, MSSQL_RPC_PORT, MSSQL_SA_PASSWORD.	copied 524 rows to dbo.gvb_gvbbench_eshoponweb_ann (INT key) and built DiskANN, parameters {"StartId":"306", "L":"48", "M":"8", "R":"48"}, graph covers 524 rows	yes	3.62 (1000 / QPS@1)
sql-diskann	20261005-101815-eshoponweb	14	default@1, default@8, exact	true	524/524	DiskANN index built and used. sys.vector_indexes: vix_gvb_gvbbench_eshoponweb on dbo.gvb_gvbbench_eshoponweb_ann in GvbBenchDiskAnn, DiskANN, COSINE, enabled, build {"StartId":"306", "L":"48", "M":"8", "R":"48"}; graph table rows 524 of 524 table rows. Real VECTOR_SEARCH plan: Vector Index Seek on index vix_gvb_gvbbench_eshoponweb of GvbBenchDiskAnn.gvb_gvbbench_eshoponweb_ann (IndexKind DiskANN), 10 rows returned, 10 hits. The exact mode searches the SAME table (dbo.gvb_gvbbench_eshoponweb_ann, database GvbBenchDiskAnn) and its real plan is: Clustered Index Scan of GvbBenchDiskAnn.gvb_gvbbench_eshoponweb_ann through PK_gvb_gvbbench_eshoponweb_ann (IndexKind Clustered), 524 rows read, no vector index operator, 10 hits	true	524/524	-	A commit returns after its transaction-log records are written to disk (SQL Server write-ahead logging; delayed durability is DISABLED); a database created here copies the model database: recovery model FULL, page_verify CHECKSUM; no global trace flags are enabled; mssql.conf of container gvb-mssql (/var/opt/mssql/mssql.conf, on the host at ~/gvb-data/engines/mssql/mssql.conf) does not exist, so it sets: nothing; it has no [control] or [traceflag] entry, so SQL Server's own Linux defaults for flushing writes apply (Microsoft's Linux performance guide names trace flag 3982 as that default; read from the guide, not tested here). Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. Container settings from its environment (names only): MSSQL_AGENT_ENABLED, MSSQL_MEMORY_LIMIT_MB, MSSQL_PID, MSSQL_RPC_PORT, MSSQL_SA_PASSWORD.	copied 524 rows to dbo.gvb_gvbbench_eshoponweb_ann (INT key) and built DiskANN, parameters {"StartId":"306", "L":"48", "M":"8", "R":"48"}, graph covers 524 rows	yes	3.66 (1000 / QPS@1)
qdrant	20261005-073329-eshoponweb	15	default@1, default@8	true	0/524	status Green, optimizer ok, indexed_vectors_count 0 of 524 points, 2 segments, indexing_threshold_kb 10,000, full_scan_threshold_kb 10,000; no index used, exact scan by design (the builder's sink sends exact=true on every search); no graph was built; searches counted since the collection was created: unfiltered_hnsw 0, unfiltered_plain 0, unfiltered_exact 0	true	0/524	2 segments / 2 segments	What was measured (strace -f on the Qdrant server process, 30 single-point REST upserts per setting, every sync call timed against the request that caused it): with wait=true each upsert had exactly one msync(MS_SYNC) of the write-ahead-log segment inside the request, before the reply (30 of 30); with wait=false the 30 upserts were acknowledged within 0.26 s with no sync call, and the first WAL msync (one call covering all 30 records) came 2.7 s after the last reply, followed by the segment-file flushes. So the log is flushed to disk under both settings, but with wait=false the flush comes after the acknowledgement: an operating-system crash or power cut in that gap loses acknowledged writes, while a crash of the Qdrant process alone should not, because the bytes are already in the kernel's page cache (inferred, not tested). Every upsert here is sent with wait=true in batches of 256 over gRPC; the strace used one point per request, so one flush per batch is inferred, not measured. Segment files are flushed every 5 s; log segments 32 MB, 0 created ahead. /qdrant/config/config.yaml in container gvb-qdrant (the image's own file; its storage keys are listed) sets: storage.collection.quantization = null, storage.collection.replication_factor = 1, storage.collection.vectors.on_disk = null, storage.collection.write_consistency_factor = 1, storage.hnsw_index.ef_construct = 100, storage.hnsw_index.full_scan_threshold_kb = 10000, storage.hnsw_index.m = 16, storage.hnsw_index.max_indexing_threads = 0, storage.hnsw_index.on_disk = false, storage.hnsw_index.payload_m = null, storage.max_collections = null, storage.node_type = Normal, storage.on_disk_payload = true, storage.optimizers.default_segment_number = 0, storage.optimizers.deleted_threshold = 0.2, storage.optimizers.flush_interval_sec = 5, storage.optimizers.indexing_threshold_kb = 10000, storage.optimizers.max_optimization_threads = null, storage.optimizers.max_segment_size_kb = null, storage.optimizers.vacuum_min_vector_number = 1000, storage.performance.max_search_threads = 0, storage.performance.optimizer_cpu_budget = 0, storage.performance.update_rate_limit = null, storage.shard_transfer_method = null, storage.snapshots_config.snapshots_storage = local, storage.snapshots_path = ./snapshots, storage.storage_path = ./storage, storage.temp_path = null, storage.update_concurrency = null, storage.wal.wal_capacity_mb = 32, storage.wal.wal_segments_ahead = 0; no QDRANT__ environment overrides in the server process. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked.	status Green, 0 of 524 vectors in HNSW segments (2 segments), waited 1.0 s	yes	0.89 (1000 / QPS@1)
qdrant	20261005-085448-eshoponweb	9	default@1, default@8	true	0/524	status Green, optimizer ok, indexed_vectors_count 0 of 524 points, 2 segments, indexing_threshold_kb 10,000, full_scan_threshold_kb 10,000; no index used, exact scan by design (the builder's sink sends exact=true on every search); no graph was built; searches counted since the collection was created: unfiltered_hnsw 0, unfiltered_plain 0, unfiltered_exact 0	true	0/524	2 segments / 2 segments	What was measured (strace -f on the Qdrant server process, 30 single-point REST upserts per setting, every sync call timed against the request that caused it): with wait=true each upsert had exactly one msync(MS_SYNC) of the write-ahead-log segment inside the request, before the reply (30 of 30); with wait=false the 30 upserts were acknowledged within 0.26 s with no sync call, and the first WAL msync (one call covering all 30 records) came 2.7 s after the last reply, followed by the segment-file flushes. So the log is flushed to disk under both settings, but with wait=false the flush comes after the acknowledgement: an operating-system crash or power cut in that gap loses acknowledged writes, while a crash of the Qdrant process alone should not, because the bytes are already in the kernel's page cache (inferred, not tested). Every upsert here is sent with wait=true in batches of 256 over gRPC; the strace used one point per request, so one flush per batch is inferred, not measured. Segment files are flushed every 5 s; log segments 32 MB, 0 created ahead. /qdrant/config/config.yaml in container gvb-qdrant (the image's own file; its storage keys are listed) sets: storage.collection.quantization = null, storage.collection.replication_factor = 1, storage.collection.vectors.on_disk = null, storage.collection.write_consistency_factor = 1, storage.hnsw_index.ef_construct = 100, storage.hnsw_index.full_scan_threshold_kb = 10000, storage.hnsw_index.m = 16, storage.hnsw_index.max_indexing_threads = 0, storage.hnsw_index.on_disk = false, storage.hnsw_index.payload_m = null, storage.max_collections = null, storage.node_type = Normal, storage.on_disk_payload = true, storage.optimizers.default_segment_number = 0, storage.optimizers.deleted_threshold = 0.2, storage.optimizers.flush_interval_sec = 5, storage.optimizers.indexing_threshold_kb = 10000, storage.optimizers.max_optimization_threads = null, storage.optimizers.max_segment_size_kb = null, storage.optimizers.vacuum_min_vector_number = 1000, storage.performance.max_search_threads = 0, storage.performance.optimizer_cpu_budget = 0, storage.performance.update_rate_limit = null, storage.shard_transfer_method = null, storage.snapshots_config.snapshots_storage = local, storage.snapshots_path = ./snapshots, storage.storage_path = ./storage, storage.temp_path = null, storage.update_concurrency = null, storage.wal.wal_capacity_mb = 32, storage.wal.wal_segments_ahead = 0; no QDRANT__ environment overrides in the server process. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked.	status Green, 0 of 524 vectors in HNSW segments (2 segments), waited 1.0 s	yes	0.89 (1000 / QPS@1)
qdrant	20261005-101815-eshoponweb	10	default@8, default@1	true	0/524	status Green, optimizer ok, indexed_vectors_count 0 of 524 points, 2 segments, indexing_threshold_kb 10,000, full_scan_threshold_kb 10,000; no index used, exact scan by design (the builder's sink sends exact=true on every search); no graph was built; searches counted since the collection was created: unfiltered_hnsw 0, unfiltered_plain 0, unfiltered_exact 0	true	0/524	2 segments / 2 segments	What was measured (strace -f on the Qdrant server process, 30 single-point REST upserts per setting, every sync call timed against the request that caused it): with wait=true each upsert had exactly one msync(MS_SYNC) of the write-ahead-log segment inside the request, before the reply (30 of 30); with wait=false the 30 upserts were acknowledged within 0.26 s with no sync call, and the first WAL msync (one call covering all 30 records) came 2.7 s after the last reply, followed by the segment-file flushes. So the log is flushed to disk under both settings, but with wait=false the flush comes after the acknowledgement: an operating-system crash or power cut in that gap loses acknowledged writes, while a crash of the Qdrant process alone should not, because the bytes are already in the kernel's page cache (inferred, not tested). Every upsert here is sent with wait=true in batches of 256 over gRPC; the strace used one point per request, so one flush per batch is inferred, not measured. Segment files are flushed every 5 s; log segments 32 MB, 0 created ahead. /qdrant/config/config.yaml in container gvb-qdrant (the image's own file; its storage keys are listed) sets: storage.collection.quantization = null, storage.collection.replication_factor = 1, storage.collection.vectors.on_disk = null, storage.collection.write_consistency_factor = 1, storage.hnsw_index.ef_construct = 100, storage.hnsw_index.full_scan_threshold_kb = 10000, storage.hnsw_index.m = 16, storage.hnsw_index.max_indexing_threads = 0, storage.hnsw_index.on_disk = false, storage.hnsw_index.payload_m = null, storage.max_collections = null, storage.node_type = Normal, storage.on_disk_payload = true, storage.optimizers.default_segment_number = 0, storage.optimizers.deleted_threshold = 0.2, storage.optimizers.flush_interval_sec = 5, storage.optimizers.indexing_threshold_kb = 10000, storage.optimizers.max_optimization_threads = null, storage.optimizers.max_segment_size_kb = null, storage.optimizers.vacuum_min_vector_number = 1000, storage.performance.max_search_threads = 0, storage.performance.optimizer_cpu_budget = 0, storage.performance.update_rate_limit = null, storage.shard_transfer_method = null, storage.snapshots_config.snapshots_storage = local, storage.snapshots_path = ./snapshots, storage.storage_path = ./storage, storage.temp_path = null, storage.update_concurrency = null, storage.wal.wal_capacity_mb = 32, storage.wal.wal_segments_ahead = 0; no QDRANT__ environment overrides in the server process. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked.	status Green, 0 of 524 vectors in HNSW segments (2 segments), waited 1.0 s	yes	0.89 (1000 / QPS@1)
qdrant-hnsw	20261005-073329-eshoponweb	1	default@8, default@1, exact	true	524/524	status Green, optimizer ok, indexed_vectors_count 524 of 524 points, 2 segments, indexing_threshold_kb 1, full_scan_threshold_kb 10; every one of 1 non-empty segments has a complete HNSW graph above its full-scan threshold; no search has run yet, so the walk is proven by the segment settings only; searches counted since the collection was created: unfiltered_hnsw 0, unfiltered_plain 0, unfiltered_exact 0	true	524/524	2 segments / 2 segments	What was measured (strace -f on the Qdrant server process, 30 single-point REST upserts per setting, every sync call timed against the request that caused it): with wait=true each upsert had exactly one msync(MS_SYNC) of the write-ahead-log segment inside the request, before the reply (30 of 30); with wait=false the 30 upserts were acknowledged within 0.26 s with no sync call, and the first WAL msync (one call covering all 30 records) came 2.7 s after the last reply, followed by the segment-file flushes. So the log is flushed to disk under both settings, but with wait=false the flush comes after the acknowledgement: an operating-system crash or power cut in that gap loses acknowledged writes, while a crash of the Qdrant process alone should not, because the bytes are already in the kernel's page cache (inferred, not tested). Every upsert here is sent with wait=true in batches of 256 over gRPC; the strace used one point per request, so one flush per batch is inferred, not measured. Segment files are flushed every 5 s; log segments 32 MB, 0 created ahead. /qdrant/config/config.yaml in container gvb-qdrant (the image's own file; its storage keys are listed) sets: storage.collection.quantization = null, storage.collection.replication_factor = 1, storage.collection.vectors.on_disk = null, storage.collection.write_consistency_factor = 1, storage.hnsw_index.ef_construct = 100, storage.hnsw_index.full_scan_threshold_kb = 10000, storage.hnsw_index.m = 16, storage.hnsw_index.max_indexing_threads = 0, storage.hnsw_index.on_disk = false, storage.hnsw_index.payload_m = null, storage.max_collections = null, storage.node_type = Normal, storage.on_disk_payload = true, storage.optimizers.default_segment_number = 0, storage.optimizers.deleted_threshold = 0.2, storage.optimizers.flush_interval_sec = 5, storage.optimizers.indexing_threshold_kb = 10000, storage.optimizers.max_optimization_threads = null, storage.optimizers.max_segment_size_kb = null, storage.optimizers.vacuum_min_vector_number = 1000, storage.performance.max_search_threads = 0, storage.performance.optimizer_cpu_budget = 0, storage.performance.update_rate_limit = null, storage.shard_transfer_method = null, storage.snapshots_config.snapshots_storage = local, storage.snapshots_path = ./snapshots, storage.storage_path = ./storage, storage.temp_path = null, storage.update_concurrency = null, storage.wal.wal_capacity_mb = 32, storage.wal.wal_segments_ahead = 0; no QDRANT__ environment overrides in the server process. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked.	indexing_threshold_kb 1, full_scan_threshold_kb 10; status Green, 524 of 524 vectors in HNSW segments (2 segments), waited 2.0 s	yes	0.91 (1000 / QPS@1)
qdrant-hnsw	20261005-085448-eshoponweb	7	exact, default@1, default@8	true	524/524	status Green, optimizer ok, indexed_vectors_count 524 of 524 points, 2 segments, indexing_threshold_kb 1, full_scan_threshold_kb 10; every one of 1 non-empty segments has a complete HNSW graph above its full-scan threshold; no search has run yet, so the walk is proven by the segment settings only; searches counted since the collection was created: unfiltered_hnsw 0, unfiltered_plain 0, unfiltered_exact 0	true	524/524	2 segments / 2 segments	What was measured (strace -f on the Qdrant server process, 30 single-point REST upserts per setting, every sync call timed against the request that caused it): with wait=true each upsert had exactly one msync(MS_SYNC) of the write-ahead-log segment inside the request, before the reply (30 of 30); with wait=false the 30 upserts were acknowledged within 0.26 s with no sync call, and the first WAL msync (one call covering all 30 records) came 2.7 s after the last reply, followed by the segment-file flushes. So the log is flushed to disk under both settings, but with wait=false the flush comes after the acknowledgement: an operating-system crash or power cut in that gap loses acknowledged writes, while a crash of the Qdrant process alone should not, because the bytes are already in the kernel's page cache (inferred, not tested). Every upsert here is sent with wait=true in batches of 256 over gRPC; the strace used one point per request, so one flush per batch is inferred, not measured. Segment files are flushed every 5 s; log segments 32 MB, 0 created ahead. /qdrant/config/config.yaml in container gvb-qdrant (the image's own file; its storage keys are listed) sets: storage.collection.quantization = null, storage.collection.replication_factor = 1, storage.collection.vectors.on_disk = null, storage.collection.write_consistency_factor = 1, storage.hnsw_index.ef_construct = 100, storage.hnsw_index.full_scan_threshold_kb = 10000, storage.hnsw_index.m = 16, storage.hnsw_index.max_indexing_threads = 0, storage.hnsw_index.on_disk = false, storage.hnsw_index.payload_m = null, storage.max_collections = null, storage.node_type = Normal, storage.on_disk_payload = true, storage.optimizers.default_segment_number = 0, storage.optimizers.deleted_threshold = 0.2, storage.optimizers.flush_interval_sec = 5, storage.optimizers.indexing_threshold_kb = 10000, storage.optimizers.max_optimization_threads = null, storage.optimizers.max_segment_size_kb = null, storage.optimizers.vacuum_min_vector_number = 1000, storage.performance.max_search_threads = 0, storage.performance.optimizer_cpu_budget = 0, storage.performance.update_rate_limit = null, storage.shard_transfer_method = null, storage.snapshots_config.snapshots_storage = local, storage.snapshots_path = ./snapshots, storage.storage_path = ./storage, storage.temp_path = null, storage.update_concurrency = null, storage.wal.wal_capacity_mb = 32, storage.wal.wal_segments_ahead = 0; no QDRANT__ environment overrides in the server process. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked.	indexing_threshold_kb 1, full_scan_threshold_kb 10; status Green, 524 of 524 vectors in HNSW segments (2 segments), waited 2.0 s	yes	0.93 (1000 / QPS@1)
qdrant-hnsw	20261005-101815-eshoponweb	7	exact, default@1, default@8	true	524/524	status Green, optimizer ok, indexed_vectors_count 524 of 524 points, 2 segments, indexing_threshold_kb 1, full_scan_threshold_kb 10; every one of 1 non-empty segments has a complete HNSW graph above its full-scan threshold; no search has run yet, so the walk is proven by the segment settings only; searches counted since the collection was created: unfiltered_hnsw 0, unfiltered_plain 0, unfiltered_exact 0	true	524/524	2 segments / 2 segments	What was measured (strace -f on the Qdrant server process, 30 single-point REST upserts per setting, every sync call timed against the request that caused it): with wait=true each upsert had exactly one msync(MS_SYNC) of the write-ahead-log segment inside the request, before the reply (30 of 30); with wait=false the 30 upserts were acknowledged within 0.26 s with no sync call, and the first WAL msync (one call covering all 30 records) came 2.7 s after the last reply, followed by the segment-file flushes. So the log is flushed to disk under both settings, but with wait=false the flush comes after the acknowledgement: an operating-system crash or power cut in that gap loses acknowledged writes, while a crash of the Qdrant process alone should not, because the bytes are already in the kernel's page cache (inferred, not tested). Every upsert here is sent with wait=true in batches of 256 over gRPC; the strace used one point per request, so one flush per batch is inferred, not measured. Segment files are flushed every 5 s; log segments 32 MB, 0 created ahead. /qdrant/config/config.yaml in container gvb-qdrant (the image's own file; its storage keys are listed) sets: storage.collection.quantization = null, storage.collection.replication_factor = 1, storage.collection.vectors.on_disk = null, storage.collection.write_consistency_factor = 1, storage.hnsw_index.ef_construct = 100, storage.hnsw_index.full_scan_threshold_kb = 10000, storage.hnsw_index.m = 16, storage.hnsw_index.max_indexing_threads = 0, storage.hnsw_index.on_disk = false, storage.hnsw_index.payload_m = null, storage.max_collections = null, storage.node_type = Normal, storage.on_disk_payload = true, storage.optimizers.default_segment_number = 0, storage.optimizers.deleted_threshold = 0.2, storage.optimizers.flush_interval_sec = 5, storage.optimizers.indexing_threshold_kb = 10000, storage.optimizers.max_optimization_threads = null, storage.optimizers.max_segment_size_kb = null, storage.optimizers.vacuum_min_vector_number = 1000, storage.performance.max_search_threads = 0, storage.performance.optimizer_cpu_budget = 0, storage.performance.update_rate_limit = null, storage.shard_transfer_method = null, storage.snapshots_config.snapshots_storage = local, storage.snapshots_path = ./snapshots, storage.storage_path = ./storage, storage.temp_path = null, storage.update_concurrency = null, storage.wal.wal_capacity_mb = 32, storage.wal.wal_segments_ahead = 0; no QDRANT__ environment overrides in the server process. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked.	indexing_threshold_kb 1, full_scan_threshold_kb 10; status Green, 524 of 524 vectors in HNSW segments (2 segments), waited 2.0 s	yes	0.93 (1000 / QPS@1)
pgvector	20261005-073329-eshoponweb	18	exact, default@8, default@1	true	?/524	pg_indexes lists gvb_gvbbench_eshoponweb_hnsw (USING hnsw (embedding vector_cosine_ops) WITH (m='16', ef_construction='128')), pg_index valid and ready = True, EXPLAIN of the default search uses Index Scan on it = True, that search returned 10 of 10 rows; PostgreSQL keeps no entry count for an HNSW index, so indexed vectors are not reported	true	?/524	-	fsync on, synchronous_commit on, full_page_writes on, wal_sync_method fdatasync (PostgreSQL defaults; pgvector.compose.yaml sets only shared_buffers, maintenance_work_mem and max_wal_size): every commit is flushed to the write-ahead log before it returns and HNSW index changes are WAL-logged, so a crash loses no committed row (max_wal_size 4GB only spaces out checkpoints; measured with docker kill, which is SIGKILL, right after a 2,000-vector load and a restart: all 2,000 rows were there and the HNSW index was valid and used by the default search)	HNSW is maintained inside every insert, nothing to build; confirmed in 0.0 s: pg_indexes lists gvb_gvbbench_eshoponweb_hnsw (USING hnsw (embedding vector_cosine_ops) WITH (m='16', ef_construction='128')), pg_index valid and ready = True, EXPLAIN of the default search uses Index Scan on it = True, that search returned 10 of 10 rows; PostgreSQL keeps no entry count for an HNSW index, so indexed vectors are not reported	yes	0.87 (1000 / QPS@1)
pgvector	20261005-085448-eshoponweb	3	default@1, exact, default@8	true	?/524	pg_indexes lists gvb_gvbbench_eshoponweb_hnsw (USING hnsw (embedding vector_cosine_ops) WITH (m='16', ef_construction='128')), pg_index valid and ready = True, EXPLAIN of the default search uses Index Scan on it = True, that search returned 10 of 10 rows; PostgreSQL keeps no entry count for an HNSW index, so indexed vectors are not reported	true	?/524	-	fsync on, synchronous_commit on, full_page_writes on, wal_sync_method fdatasync (PostgreSQL defaults; pgvector.compose.yaml sets only shared_buffers, maintenance_work_mem and max_wal_size): every commit is flushed to the write-ahead log before it returns and HNSW index changes are WAL-logged, so a crash loses no committed row (max_wal_size 4GB only spaces out checkpoints; measured with docker kill, which is SIGKILL, right after a 2,000-vector load and a restart: all 2,000 rows were there and the HNSW index was valid and used by the default search)	HNSW is maintained inside every insert, nothing to build; confirmed in 0.0 s: pg_indexes lists gvb_gvbbench_eshoponweb_hnsw (USING hnsw (embedding vector_cosine_ops) WITH (m='16', ef_construction='128')), pg_index valid and ready = True, EXPLAIN of the default search uses Index Scan on it = True, that search returned 10 of 10 rows; PostgreSQL keeps no entry count for an HNSW index, so indexed vectors are not reported	yes	0.83 (1000 / QPS@1)
pgvector	20261005-101815-eshoponweb	11	default@8, exact, default@1	true	?/524	pg_indexes lists gvb_gvbbench_eshoponweb_hnsw (USING hnsw (embedding vector_cosine_ops) WITH (m='16', ef_construction='128')), pg_index valid and ready = True, EXPLAIN of the default search uses Index Scan on it = True, that search returned 10 of 10 rows; PostgreSQL keeps no entry count for an HNSW index, so indexed vectors are not reported	true	?/524	-	fsync on, synchronous_commit on, full_page_writes on, wal_sync_method fdatasync (PostgreSQL defaults; pgvector.compose.yaml sets only shared_buffers, maintenance_work_mem and max_wal_size): every commit is flushed to the write-ahead log before it returns and HNSW index changes are WAL-logged, so a crash loses no committed row (max_wal_size 4GB only spaces out checkpoints; measured with docker kill, which is SIGKILL, right after a 2,000-vector load and a restart: all 2,000 rows were there and the HNSW index was valid and used by the default search)	HNSW is maintained inside every insert, nothing to build; confirmed in 0.0 s: pg_indexes lists gvb_gvbbench_eshoponweb_hnsw (USING hnsw (embedding vector_cosine_ops) WITH (m='16', ef_construction='128')), pg_index valid and ready = True, EXPLAIN of the default search uses Index Scan on it = True, that search returned 10 of 10 rows; PostgreSQL keeps no entry count for an HNSW index, so indexed vectors are not reported	yes	0.87 (1000 / QPS@1)
mariadb	20261005-073329-eshoponweb	16	exact, default@8, default@1	true	?/524	information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 518 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported	true	?/524	-	innodb_flush_log_at_trx_commit=2 (set in mariadb-bench.compose.yaml for the benchmark's own container gvbbench-mariadb, and in mariadb.compose.yaml for the daily gvb-mariadb, which has the same server settings): the InnoDB redo log is written to the operating system at every commit but fsynced about once a second, so a crash of the mariadbd process loses nothing, while an operating-system crash or power cut can lose the last second of commits; innodb_doublewrite is on (default), the binary log is off, and the vector graph is an InnoDB table under the same log (settings read from the running server with SHOW VARIABLES; the crash behaviour is InnoDB's documented behaviour for this setting and was not tested on either container)	VECTOR INDEX is maintained inside every INSERT, nothing to build; confirmed after 2 poll(s) in 0.5 s (poll 1 of 2 said: not ready: a search at mhnsw_ef_search 100 returned only 405 of 524 requested rows through the index (EXPLAIN key 'vec_idx') (information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 405 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported)): information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 518 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported	yes	0.64 (1000 / QPS@1)
mariadb	20261005-085448-eshoponweb	16	default@1, exact, default@8	true	?/524	information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 515 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported	true	?/524	-	innodb_flush_log_at_trx_commit=2 (set in mariadb-bench.compose.yaml for the benchmark's own container gvbbench-mariadb, and in mariadb.compose.yaml for the daily gvb-mariadb, which has the same server settings): the InnoDB redo log is written to the operating system at every commit but fsynced about once a second, so a crash of the mariadbd process loses nothing, while an operating-system crash or power cut can lose the last second of commits; innodb_doublewrite is on (default), the binary log is off, and the vector graph is an InnoDB table under the same log (settings read from the running server with SHOW VARIABLES; the crash behaviour is InnoDB's documented behaviour for this setting and was not tested on either container)	VECTOR INDEX is maintained inside every INSERT, nothing to build; confirmed after 2 poll(s) in 0.5 s (poll 1 of 2 said: not ready: a search at mhnsw_ef_search 100 returned only 397 of 524 requested rows through the index (EXPLAIN key 'vec_idx') (information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 397 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported)): information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 515 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported	yes	0.63 (1000 / QPS@1)
mariadb	20261005-101815-eshoponweb	6	default@1, default@8, exact	true	?/524	information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 518 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported	true	?/524	-	innodb_flush_log_at_trx_commit=2 (set in mariadb-bench.compose.yaml for the benchmark's own container gvbbench-mariadb, and in mariadb.compose.yaml for the daily gvb-mariadb, which has the same server settings): the InnoDB redo log is written to the operating system at every commit but fsynced about once a second, so a crash of the mariadbd process loses nothing, while an operating-system crash or power cut can lose the last second of commits; innodb_doublewrite is on (default), the binary log is off, and the vector graph is an InnoDB table under the same log (settings read from the running server with SHOW VARIABLES; the crash behaviour is InnoDB's documented behaviour for this setting and was not tested on either container)	VECTOR INDEX is maintained inside every INSERT, nothing to build; confirmed after 2 poll(s) in 0.5 s (poll 1 of 2 said: not ready: a search at mhnsw_ef_search 100 returned only 389 of 524 requested rows through the index (EXPLAIN key 'vec_idx') (information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 389 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported)): information_schema lists vec_idx as INDEX_TYPE VECTOR, EXPLAIN of the default search uses key vec_idx, the server applied mhnsw_ef_search 100 (asked for 100, read back from the server), a search at that effort returned 518 of 524 requested rows through the index; MariaDB has no per-index row count (the graph is a hidden InnoDB table), so indexed vectors are not reported	yes	0.64 (1000 / QPS@1)
oracle	20261005-073329-eshoponweb	3	exact, default@8, default@1	true	524/524	HNSW graph holds 524 of 524 rows, change log waiting: 0 inserts and 0 deletes, USER_INDEXES status VALID, plan of the default search: VECTOR INDEX HNSW SCAN > TABLE ACCESS BY INDEX ROWID, index used by 0 queries so far; Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit)	true	524/524	-	By these settings a committed row should survive a crash or power loss. The sink uses a plain COMMIT and commit_logging, commit_wait and commit_write are unset in the database, so every commit waits for its redo to be written. Measured 2026-10-04: 50 separate client commits raised V$SYSSTAT 'redo synch writes' by 55 (the 50 commits plus the CREATE and DROP of the probe table), and the log writer and the datafile writer hold their files open with O_DSYNC (open flags 02110002, filesystemio_options none). The database runs NOARCHIVELOG (V$DATABASE.LOG_MODE), so redo serves crash recovery only and there is no point-in-time restore. The HNSW graph lives in the 768 MB vector memory pool (oracle-init/01-vector-memory.sh) and is not the durable copy; the table is. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. CPU: Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit).	HNSW graph holds 524 of 524 rows, change log waiting: 0 inserts and 0 deletes, USER_INDEXES status VALID, plan of the default search: VECTOR INDEX HNSW SCAN > TABLE ACCESS BY INDEX ROWID, index used by 0 queries so far; Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit); graph rebuilt in 2.2 s	no: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 6,134 searches (0 failed) at 1 searcher; p50 of the last windows 2.383, 2.353, 2.360 ms (windows of at least 2 s and 100 searches); trial of 1,220 searches in 3.0 s at 1 searcher: p50 2.382 ms against the settled p50 2.360 ms, 1% apart (limit 10%); default@8: warm-up 15.0 s and 43,925 searches (0 failed) at 8 searchers; QPS of the last windows 2,416, 3,480, 2,581 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 9,374 searches in 3.0 s at 8 searchers: 3,124 QPS against the settled 2,581 QPS, 17% apart (limit 10%), so the warm-up was EXTENDED once (120.3 s and 343,792 searches (0 failed) at 8 searchers; QPS of the last windows 3,449, 2,488, 3,050 (windows of at least 2 s and 100 searches), the 120 s cap ran out); second trial of 9,654 searches in 3.0 s at 8 searchers: 3,217 QPS against the settled 3,050 QPS, 5% apart (limit 10%); still disagreeing after the extension; default@1: warm-up 15.0 s and 16,210 searches (0 failed) at 1 searcher; p50 of the last windows 0.894, 0.885, 0.895 ms (windows of at least 2 s and 100 searches); trial of 3,375 searches in 3.0 s at 1 searcher: p50 0.867 ms against the settled p50 0.894 ms, 3% apart (limit 10%). Its numbers may still include warm-up; rerun before quoting them.	0.91 (1000 / QPS@1)
oracle	20261005-085448-eshoponweb	10	exact, default@1, default@8	true	524/524	HNSW graph holds 524 of 524 rows, change log waiting: 0 inserts and 0 deletes, USER_INDEXES status VALID, plan of the default search: VECTOR INDEX HNSW SCAN > TABLE ACCESS BY INDEX ROWID, index used by 0 queries so far; Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit)	true	524/524	-	By these settings a committed row should survive a crash or power loss. The sink uses a plain COMMIT and commit_logging, commit_wait and commit_write are unset in the database, so every commit waits for its redo to be written. Measured 2026-10-04: 50 separate client commits raised V$SYSSTAT 'redo synch writes' by 55 (the 50 commits plus the CREATE and DROP of the probe table), and the log writer and the datafile writer hold their files open with O_DSYNC (open flags 02110002, filesystemio_options none). The database runs NOARCHIVELOG (V$DATABASE.LOG_MODE), so redo serves crash recovery only and there is no point-in-time restore. The HNSW graph lives in the 768 MB vector memory pool (oracle-init/01-vector-memory.sh) and is not the durable copy; the table is. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. CPU: Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit).	HNSW graph holds 524 of 524 rows, change log waiting: 0 inserts and 0 deletes, USER_INDEXES status VALID, plan of the default search: VECTOR INDEX HNSW SCAN > TABLE ACCESS BY INDEX ROWID, index used by 0 queries so far; Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit); graph rebuilt in 2.3 s	no: latency had NOT settled when timing began for default@1, default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 5,949 searches (0 failed) at 1 searcher; p50 of the last windows 2.363, 2.376, 2.356 ms (windows of at least 2 s and 100 searches); trial of 1,229 searches in 3.0 s at 1 searcher: p50 2.387 ms against the settled p50 2.363 ms, 1% apart (limit 10%); default@1: warm-up 15.0 s and 16,397 searches (0 failed) at 1 searcher; p50 of the last windows 0.860, 0.892, 0.913 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 3,246 searches in 3.0 s at 1 searcher: p50 0.900 ms against the settled p50 0.892 ms, 1% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 32,617 searches (0 failed) at 1 searcher; p50 of the last windows 0.883, 0.857, 0.926 ms (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 3,341 searches in 3.0 s at 1 searcher: p50 0.874 ms against the settled p50 0.883 ms, 1% apart (limit 10%); still disagreeing after the extension; default@8: warm-up 15.0 s and 48,930 searches (0 failed) at 8 searchers; QPS of the last windows 3,514, 2,364, 3,100 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 7,829 searches in 3.1 s at 8 searchers: 2,519 QPS against the settled 3,100 QPS, 23% apart (limit 10%), so the warm-up was EXTENDED once (120.0 s and 315,148 searches (0 failed) at 8 searchers; QPS of the last windows 2,207, 2,452, 2,930 (windows of at least 2 s and 100 searches), the 120 s cap ran out); second trial of 7,269 searches in 3.3 s at 8 searchers: 2,230 QPS against the settled 2,452 QPS, 10% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them.	0.92 (1000 / QPS@1)
oracle	20261005-101815-eshoponweb	19	exact, default@1, default@8	true	524/524	HNSW graph holds 524 of 524 rows, change log waiting: 0 inserts and 0 deletes, USER_INDEXES status VALID, plan of the default search: VECTOR INDEX HNSW SCAN > TABLE ACCESS BY INDEX ROWID, index used by 0 queries so far; Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit)	true	524/524	-	By these settings a committed row should survive a crash or power loss. The sink uses a plain COMMIT and commit_logging, commit_wait and commit_write are unset in the database, so every commit waits for its redo to be written. Measured 2026-10-04: 50 separate client commits raised V$SYSSTAT 'redo synch writes' by 55 (the 50 commits plus the CREATE and DROP of the probe table), and the log writer and the datafile writer hold their files open with O_DSYNC (open flags 02110002, filesystemio_options none). The database runs NOARCHIVELOG (V$DATABASE.LOG_MODE), so redo serves crash recovery only and there is no point-in-time restore. The HNSW graph lives in the 768 MB vector memory pool (oracle-init/01-vector-memory.sh) and is not the durable copy; the table is. Not tested by cutting power; whether the disk's own write cache reaches the media was not checked. CPU: Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit).	HNSW graph holds 524 of 524 rows, change log waiting: 0 inserts and 0 deletes, USER_INDEXES status VALID, plan of the default search: VECTOR INDEX HNSW SCAN > TABLE ACCESS BY INDEX ROWID, index used by 0 queries so far; Oracle Free caps itself at 2 CPUs (cpu_count 2 in V$PARAMETER, edition FREE in V$INSTANCE, 8 host CPUs in V$OSSTAT NUM_CPUS; the 2 CPU thread limit is Oracle's documented Free edition limit); graph rebuilt in 2.2 s	no: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 6,064 searches (0 failed) at 1 searcher; p50 of the last windows 2.371, 2.350, 2.331 ms (windows of at least 2 s and 100 searches); trial of 1,244 searches in 3.0 s at 1 searcher: p50 2.356 ms against the settled p50 2.350 ms, 0% apart (limit 10%); default@1: warm-up 15.0 s and 16,495 searches (0 failed) at 1 searcher; p50 of the last windows 0.888, 0.870, 0.904 ms (windows of at least 2 s and 100 searches); trial of 3,251 searches in 3.0 s at 1 searcher: p50 0.896 ms against the settled p50 0.888 ms, 1% apart (limit 10%); default@8: warm-up 15.3 s and 44,258 searches (0 failed) at 8 searchers; QPS of the last windows 3,062, 2,834, 2,622 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 9,357 searches in 3.0 s at 8 searchers: 3,118 QPS against the settled 2,834 QPS, 9% apart (limit 10%), so the warm-up was EXTENDED once (120.2 s and 344,269 searches (0 failed) at 8 searchers; QPS of the last windows 3,394, 2,474, 2,998 (windows of at least 2 s and 100 searches), the 120 s cap ran out); second trial of 9,022 searches in 3.0 s at 8 searchers: 3,006 QPS against the settled 2,998 QPS, 0% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them.	0.91 (1000 / QPS@1)
redis	20261005-073329-eshoponweb	17	default@1, default@8, exact	true	524/524	FT.INFO indexing 0, percent_indexed 1, hash_indexing_failures 0, flat_buffer_size 0, num_docs 524, hashes counted with SCAN under gvb_gvbbench_eshoponweb: 524	true	524/524	-	save "300 1" and appendonly no (redis.compose.yaml): an RDB snapshot is written every 5 minutes if at least one key changed, and on a clean stop; there is no append-only log, so a crash loses every write since the last snapshot (up to 5 minutes plus the time a snapshot takes; measured with docker kill, which is SIGKILL, right after a 2,000-vector load: none of the 2,000 hashes were there after the restart, and the restart loaded an older snapshot that still held keys of a collection that had been dropped since)	HNSW index finished after 0.0 s of waiting: FT.INFO indexing 0, percent_indexed 1, hash_indexing_failures 0, flat_buffer_size 0, num_docs 524, hashes counted with SCAN under gvb_gvbbench_eshoponweb: 524	no: latency had NOT settled when timing began for exact (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). default@1: warm-up 15.0 s and 39,275 searches (0 failed) at 1 searcher; p50 of the last windows 0.383, 0.380, 0.382 ms (windows of at least 2 s and 100 searches); trial of 8,168 searches in 3.0 s at 1 searcher: p50 0.349 ms against the settled p50 0.382 ms, 10% apart (limit 10%); default@8: warm-up 15.0 s and 76,531 searches (0 failed) at 8 searchers; QPS of the last windows 5,217, 5,302, 5,056 (windows of at least 2 s and 100 searches); trial of 15,028 searches in 3.0 s at 8 searchers: 5,007 QPS against the settled 5,217 QPS, 4% apart (limit 10%); exact: warm-up 15.0 s and 41,741 searches (0 failed) at 1 searcher; p50 of the last windows 0.364, 0.362, 0.324 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 7,959 searches in 3.0 s at 1 searcher: p50 0.380 ms against the settled p50 0.362 ms, 5% apart (limit 10%), so the warm-up was EXTENDED once (36.0 s and 99,849 searches (0 failed) at 1 searcher; p50 of the last windows 0.362, 0.353, 0.342 ms (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 8,351 searches in 3.0 s at 1 searcher: p50 0.359 ms against the settled p50 0.353 ms, 2% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them.	0.38 (1000 / QPS@1)
redis	20261005-085448-eshoponweb	14	default@1, exact, default@8	true	524/524	FT.INFO indexing 0, percent_indexed 1, hash_indexing_failures 0, flat_buffer_size 0, num_docs 524, hashes counted with SCAN under gvb_gvbbench_eshoponweb: 524	true	524/524	-	save "300 1" and appendonly no (redis.compose.yaml): an RDB snapshot is written every 5 minutes if at least one key changed, and on a clean stop; there is no append-only log, so a crash loses every write since the last snapshot (up to 5 minutes plus the time a snapshot takes; measured with docker kill, which is SIGKILL, right after a 2,000-vector load: none of the 2,000 hashes were there after the restart, and the restart loaded an older snapshot that still held keys of a collection that had been dropped since)	HNSW index finished after 0.0 s of waiting: FT.INFO indexing 0, percent_indexed 1, hash_indexing_failures 0, flat_buffer_size 0, num_docs 524, hashes counted with SCAN under gvb_gvbbench_eshoponweb: 524	no: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). default@1: warm-up 15.0 s and 39,692 searches (0 failed) at 1 searcher; p50 of the last windows 0.352, 0.350, 0.369 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 8,035 searches in 3.0 s at 1 searcher: p50 0.355 ms against the settled p50 0.352 ms, 1% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 77,908 searches (0 failed) at 1 searcher; p50 of the last windows 0.379, 0.384, 0.376 ms (windows of at least 2 s and 100 searches)); second trial of 7,691 searches in 3.0 s at 1 searcher: p50 0.388 ms against the settled p50 0.379 ms, 3% apart (limit 10%); settled after the extension; exact: warm-up 15.0 s and 41,325 searches (0 failed) at 1 searcher; p50 of the last windows 0.367, 0.376, 0.359 ms (windows of at least 2 s and 100 searches); trial of 8,543 searches in 3.0 s at 1 searcher: p50 0.342 ms against the settled p50 0.367 ms, 7% apart (limit 10%); default@8: warm-up 15.0 s and 75,695 searches (0 failed) at 8 searchers; QPS of the last windows 4,921, 5,016, 5,277 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 15,098 searches in 3.0 s at 8 searchers: 5,030 QPS against the settled 5,016 QPS, 0% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 153,806 searches (0 failed) at 8 searchers; QPS of the last windows 5,068, 5,484, 4,940 (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 15,130 searches in 3.0 s at 8 searchers: 5,041 QPS against the settled 5,068 QPS, 1% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them.	0.38 (1000 / QPS@1)
redis	20261005-101815-eshoponweb	17	exact, default@1, default@8	true	524/524	FT.INFO indexing 0, percent_indexed 1, hash_indexing_failures 0, flat_buffer_size 0, num_docs 524, hashes counted with SCAN under gvb_gvbbench_eshoponweb: 524	true	524/524	-	save "300 1" and appendonly no (redis.compose.yaml): an RDB snapshot is written every 5 minutes if at least one key changed, and on a clean stop; there is no append-only log, so a crash loses every write since the last snapshot (up to 5 minutes plus the time a snapshot takes; measured with docker kill, which is SIGKILL, right after a 2,000-vector load: none of the 2,000 hashes were there after the restart, and the restart loaded an older snapshot that still held keys of a collection that had been dropped since)	HNSW index finished after 0.0 s of waiting: FT.INFO indexing 0, percent_indexed 1, hash_indexing_failures 0, flat_buffer_size 0, num_docs 524, hashes counted with SCAN under gvb_gvbbench_eshoponweb: 524	no: latency had NOT settled when timing began for exact (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 41,314 searches (0 failed) at 1 searcher; p50 of the last windows 0.336, 0.374, 0.372 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 8,416 searches in 3.0 s at 1 searcher: p50 0.335 ms against the settled p50 0.372 ms, 11% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 81,883 searches (0 failed) at 1 searcher; p50 of the last windows 0.363, 0.369, 0.338 ms (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 8,081 searches in 3.0 s at 1 searcher: p50 0.369 ms against the settled p50 0.363 ms, 2% apart (limit 10%); still disagreeing after the extension; default@1: warm-up 15.0 s and 38,516 searches (0 failed) at 1 searcher; p50 of the last windows 0.372, 0.407, 0.378 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 7,842 searches in 3.0 s at 1 searcher: p50 0.377 ms against the settled p50 0.378 ms, 0% apart (limit 10%), so the warm-up was EXTENDED once (32.0 s and 82,511 searches (0 failed) at 1 searcher; p50 of the last windows 0.385, 0.380, 0.391 ms (windows of at least 2 s and 100 searches)); second trial of 7,681 searches in 3.0 s at 1 searcher: p50 0.390 ms against the settled p50 0.385 ms, 1% apart (limit 10%); settled after the extension; default@8: warm-up 15.0 s and 75,402 searches (0 failed) at 8 searchers; QPS of the last windows 4,844, 5,008, 5,010 (windows of at least 2 s and 100 searches); trial of 14,794 searches in 3.0 s at 8 searchers: 4,929 QPS against the settled 5,008 QPS, 2% apart (limit 10%). Its numbers may still include warm-up; rerun before quoting them.	0.39 (1000 / QPS@1)
mongodb	20261005-073329-eshoponweb	7	default@1, exact, default@8	true	524/524	index status READY, queryable True; mongot holds 524 of 524 documents in 2 segment(s) (269 + 255 documents), 2 searched through the HNSW graph (Approximate)	true	524/524	2 segments / 2 segments	Acknowledged writes are journaled before the acknowledgement. The sink sets no write concern, so the server default applies: getDefaultRWConcern gives w majority and the one-member replica set (--replSet gvbmongo in the image) has writeConcernMajorityJournalDefault true, with WiredTiger journaling on (journalCommitInterval 100 ms is only the interval for unacknowledged work). Measured 2026-10-04: 30 acknowledged single-document inserts raised WiredTiger 'log sync operations' by 30 and strace showed fdatasync on /data/db/journal/WiredTigerLog files. A crash loses no acknowledged write. mongot's search index is not part of that promise: it follows the collection asynchronously and is rebuilt from it.	index status READY, queryable True; mongot holds 524 of 524 documents in 2 segment(s) (269 + 255 documents), 2 searched through the HNSW graph (Approximate); segment layout unchanged for 10.2 s over 11 readings; wait took 10.2 s	yes	1.42 (1000 / QPS@1)
mongodb	20261005-085448-eshoponweb	19	exact, default@8, default@1	true	524/524	index status READY, queryable True; mongot holds 524 of 524 documents in 4 segment(s) (268 + 254 + 1 + 1 documents), 4 searched through the HNSW graph (Approximate)	true	524/524	4 segments / 4 segments	Acknowledged writes are journaled before the acknowledgement. The sink sets no write concern, so the server default applies: getDefaultRWConcern gives w majority and the one-member replica set (--replSet gvbmongo in the image) has writeConcernMajorityJournalDefault true, with WiredTiger journaling on (journalCommitInterval 100 ms is only the interval for unacknowledged work). Measured 2026-10-04: 30 acknowledged single-document inserts raised WiredTiger 'log sync operations' by 30 and strace showed fdatasync on /data/db/journal/WiredTigerLog files. A crash loses no acknowledged write. mongot's search index is not part of that promise: it follows the collection asynchronously and is rebuilt from it.	index status READY, queryable True; mongot holds 524 of 524 documents in 4 segment(s) (268 + 254 + 1 + 1 documents), 4 searched through the HNSW graph (Approximate); segment layout unchanged for 10.2 s over 11 readings; wait took 10.2 s	yes	1.44 (1000 / QPS@1)
mongodb	20261005-101815-eshoponweb	4	default@1, exact, default@8	true	524/524	index status READY, queryable True; mongot holds 524 of 524 documents in 2 segment(s) (264 + 260 documents), 2 searched through the HNSW graph (Approximate)	true	524/524	2 segments / 2 segments	Acknowledged writes are journaled before the acknowledgement. The sink sets no write concern, so the server default applies: getDefaultRWConcern gives w majority and the one-member replica set (--replSet gvbmongo in the image) has writeConcernMajorityJournalDefault true, with WiredTiger journaling on (journalCommitInterval 100 ms is only the interval for unacknowledged work). Measured 2026-10-04: 30 acknowledged single-document inserts raised WiredTiger 'log sync operations' by 30 and strace showed fdatasync on /data/db/journal/WiredTigerLog files. A crash loses no acknowledged write. mongot's search index is not part of that promise: it follows the collection asynchronously and is rebuilt from it.	index status READY, queryable True; mongot holds 524 of 524 documents in 2 segment(s) (264 + 260 documents), 2 searched through the HNSW graph (Approximate); segment layout unchanged for 10.2 s over 11 readings; wait took 10.3 s	yes	1.42 (1000 / QPS@1)
clickhouse	20261005-073329-eshoponweb	5	exact, default@1, default@8	true	524/524	1 data part(s), index files on 1 of them, 524 of 524 live rows in indexed parts; 0 merge(s) running, 0 unfinished mutation(s); plan of the default search uses the Skip index vec_idx on 1 of 1 parts	true	524/524	-	Acknowledged inserts are not fsynced. The sink creates plain MergeTree tables, so the MergeTree settings are the defaults: fsync_after_insert 0 and fsync_part_directory 0 (system.merge_tree_settings), and async_insert 1 with wait_for_async_insert 1 is the server default for the gvb login (system.settings), so an insert is acknowledged once its part is written, not once it is on disk. Measured 2026-10-04 with strace over 30 acknowledged single-row inserts (30 Ok rows in system.asynchronous_insert_log): zero fsync, fdatasync or sync_file_range calls, while the control, a table created with fsync_after_insert=1, made 61 fdatasync calls for 5 inserts. A host power loss or kernel crash can lose acknowledged rows that are still in the OS page cache; a ClickHouse process crash alone should not (inferred, not tested).	1 data part(s), index files on 1 of them, 524 of 524 live rows in indexed parts; 0 merge(s) running, 0 unfinished mutation(s); plan of the default search uses the Skip index vec_idx on 1 of 1 parts; wait took 6.2 s	no: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 2,395 searches (0 failed) at 1 searcher; p50 of the last windows 6.058, 6.063, 6.057 ms (windows of at least 2 s and 100 searches); trial of 488 searches in 3.0 s at 1 searcher: p50 6.032 ms against the settled p50 6.058 ms, 0% apart (limit 10%); default@1: warm-up 15.0 s and 3,279 searches (0 failed) at 1 searcher; p50 of the last windows 4.472, 4.478, 4.471 ms (windows of at least 2 s and 100 searches); trial of 654 searches in 3.0 s at 1 searcher: p50 4.486 ms against the settled p50 4.472 ms, 0% apart (limit 10%); default@8: warm-up 15.0 s and 7,362 searches (0 failed) at 8 searchers; QPS of the last windows 434, 504, 522 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 1,512 searches in 3.0 s at 8 searchers: 502 QPS against the settled 504 QPS, 0% apart (limit 10%), so the warm-up was EXTENDED once (38.1 s and 18,460 searches (0 failed) at 8 searchers; QPS of the last windows 525, 524, 488 (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 1,302 searches in 3.0 s at 8 searchers: 432 QPS against the settled 524 QPS, 21% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them.	4.65 (1000 / QPS@1)
clickhouse	20261005-085448-eshoponweb	18	default@8, exact, default@1	true	524/524	1 data part(s), index files on 1 of them, 524 of 524 live rows in indexed parts; 0 merge(s) running, 0 unfinished mutation(s); plan of the default search uses the Skip index vec_idx on 1 of 1 parts	true	524/524	-	Acknowledged inserts are not fsynced. The sink creates plain MergeTree tables, so the MergeTree settings are the defaults: fsync_after_insert 0 and fsync_part_directory 0 (system.merge_tree_settings), and async_insert 1 with wait_for_async_insert 1 is the server default for the gvb login (system.settings), so an insert is acknowledged once its part is written, not once it is on disk. Measured 2026-10-04 with strace over 30 acknowledged single-row inserts (30 Ok rows in system.asynchronous_insert_log): zero fsync, fdatasync or sync_file_range calls, while the control, a table created with fsync_after_insert=1, made 61 fdatasync calls for 5 inserts. A host power loss or kernel crash can lose acknowledged rows that are still in the OS page cache; a ClickHouse process crash alone should not (inferred, not tested).	1 data part(s), index files on 1 of them, 524 of 524 live rows in indexed parts; 0 merge(s) running, 0 unfinished mutation(s); plan of the default search uses the Skip index vec_idx on 1 of 1 parts; wait took 6.2 s	no: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). default@8: warm-up 15.0 s and 7,401 searches (0 failed) at 8 searchers; QPS of the last windows 458, 442, 444 (windows of at least 2 s and 100 searches); trial of 1,581 searches in 3.0 s at 8 searchers: 525 QPS against the settled 444 QPS, 16% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 14,706 searches (0 failed) at 8 searchers; QPS of the last windows 530, 525, 452 (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 1,311 searches in 3.0 s at 8 searchers: 435 QPS against the settled 525 QPS, 21% apart (limit 10%); still disagreeing after the extension; exact: warm-up 15.0 s and 2,370 searches (0 failed) at 1 searcher; p50 of the last windows 6.089, 6.058, 6.067 ms (windows of at least 2 s and 100 searches); trial of 487 searches in 3.0 s at 1 searcher: p50 6.077 ms against the settled p50 6.067 ms, 0% apart (limit 10%); default@1: warm-up 15.0 s and 3,267 searches (0 failed) at 1 searcher; p50 of the last windows 4.489, 4.504, 4.493 ms (windows of at least 2 s and 100 searches); trial of 657 searches in 3.0 s at 1 searcher: p50 4.468 ms against the settled p50 4.493 ms, 1% apart (limit 10%). Its numbers may still include warm-up; rerun before quoting them.	4.66 (1000 / QPS@1)
clickhouse	20261005-101815-eshoponweb	9	default@1, exact, default@8	true	524/524	1 data part(s), index files on 1 of them, 524 of 524 live rows in indexed parts; 0 merge(s) running, 0 unfinished mutation(s); plan of the default search uses the Skip index vec_idx on 1 of 1 parts	true	524/524	-	Acknowledged inserts are not fsynced. The sink creates plain MergeTree tables, so the MergeTree settings are the defaults: fsync_after_insert 0 and fsync_part_directory 0 (system.merge_tree_settings), and async_insert 1 with wait_for_async_insert 1 is the server default for the gvb login (system.settings), so an insert is acknowledged once its part is written, not once it is on disk. Measured 2026-10-04 with strace over 30 acknowledged single-row inserts (30 Ok rows in system.asynchronous_insert_log): zero fsync, fdatasync or sync_file_range calls, while the control, a table created with fsync_after_insert=1, made 61 fdatasync calls for 5 inserts. A host power loss or kernel crash can lose acknowledged rows that are still in the OS page cache; a ClickHouse process crash alone should not (inferred, not tested).	1 data part(s), index files on 1 of them, 524 of 524 live rows in indexed parts; 0 merge(s) running, 0 unfinished mutation(s); plan of the default search uses the Skip index vec_idx on 1 of 1 parts; wait took 6.2 s	no: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). default@1: warm-up 15.0 s and 3,232 searches (0 failed) at 1 searcher; p50 of the last windows 4.436, 4.452, 4.476 ms (windows of at least 2 s and 100 searches); trial of 655 searches in 3.0 s at 1 searcher: p50 4.479 ms against the settled p50 4.452 ms, 1% apart (limit 10%); exact: warm-up 15.0 s and 2,442 searches (0 failed) at 1 searcher; p50 of the last windows 6.029, 6.056, 6.035 ms (windows of at least 2 s and 100 searches); trial of 457 searches in 3.0 s at 1 searcher: p50 6.120 ms against the settled p50 6.035 ms, 1% apart (limit 10%); default@8: warm-up 15.0 s and 7,381 searches (0 failed) at 8 searchers; QPS of the last windows 435, 510, 524 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 1,509 searches in 3.0 s at 8 searchers: 501 QPS against the settled 510 QPS, 2% apart (limit 10%), so the warm-up was EXTENDED once (32.0 s and 15,463 searches (0 failed) at 8 searchers; QPS of the last windows 440, 445, 524 (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 1,583 searches in 3.0 s at 8 searchers: 526 QPS against the settled 445 QPS, 15% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them.	4.66 (1000 / QPS@1)
milvus	20261005-073329-eshoponweb	2	default@8, default@1	true	524/524	index Finished, type HNSW (COSINE, {"M":16,"efConstruction":128}), indexedRows 524 of 524 sealed rows, pendingRows 0; stored rows 524; LoadStateLoaded; query node: 1 sealed segment(s) with the index loaded covering 524 rows against 524 stored rows, 0 sealed without it, 0 rows in growing segments; datacoord: 1 live segment(s), 1 flushed and indexed covering 524 rows, 0 delete-log (L0) segment(s) waiting for a compaction, 3 segment(s) compacted away so far; search ledger since the index finished: the sink sent 0 searches (searchParams.params.ef=100, Strong consistency), the query node counted 0 search requests for this collection, segment searches Sealed +0 and Growing +0, the same sealed segments with the same loaded index builds at both readings, segments compacted away +0	true	524/524	1 sealed segment covering 524 rows / 1 sealed segment covering 524 rows	Writes are not fsynced. Standalone uses the default message queue rocksmq (RocksDB, /var/lib/milvus/rdb_data, mq.type default) and flushed segments go to local-disk object storage (COMMON_STORAGETYPE=local in milvus.compose.yaml). Measured 2026-10-04 with strace over 30 acknowledged single-row upserts and one flush: fdatasync ran only on the embedded etcd files (member/wal, member/snap/db), never on rdb_data or the segment files. A host power loss or kernel crash can lose acknowledged rows that are still in the OS page cache; a Milvus process crash alone should not (inferred, not tested). Metadata in embedded etcd is fdatasynced on every commit.	index Finished, type HNSW (COSINE, {"M":16,"efConstruction":128}), indexedRows 524 of 524 sealed rows, pendingRows 0; stored rows 524; LoadStateLoaded; query node: 1 sealed segment(s) with the index loaded covering 524 rows against 524 stored rows, 0 sealed without it, 0 rows in growing segments; datacoord: 1 live segment(s), 1 flushed and indexed covering 524 rows, 0 delete-log (L0) segment(s) waiting for a compaction, 3 segment(s) compacted away so far; flush, index build and load took 14.7 s, then compaction: 1 job(s) accepted by Milvus, layout ready and unchanged for 75 s, 124.1 s for the whole step; search ledger started, later state reads count the searches against the query node's own counters	yes	2.27 (1000 / QPS@1)
milvus	20261005-085448-eshoponweb	5	default@1, default@8	true	524/524	index Finished, type HNSW (COSINE, {"M":16,"efConstruction":128}), indexedRows 524 of 524 sealed rows, pendingRows 0; stored rows 524; LoadStateLoaded; query node: 1 sealed segment(s) with the index loaded covering 524 rows against 524 stored rows, 0 sealed without it, 0 rows in growing segments; datacoord: 1 live segment(s), 1 flushed and indexed covering 524 rows, 0 delete-log (L0) segment(s) waiting for a compaction, 3 segment(s) compacted away so far; search ledger since the index finished: the sink sent 0 searches (searchParams.params.ef=100, Strong consistency), the query node counted 0 search requests for this collection, segment searches Sealed +0 and Growing +0, the same sealed segments with the same loaded index builds at both readings, segments compacted away +0	true	524/524	1 sealed segment covering 524 rows / 1 sealed segment covering 524 rows	Writes are not fsynced. Standalone uses the default message queue rocksmq (RocksDB, /var/lib/milvus/rdb_data, mq.type default) and flushed segments go to local-disk object storage (COMMON_STORAGETYPE=local in milvus.compose.yaml). Measured 2026-10-04 with strace over 30 acknowledged single-row upserts and one flush: fdatasync ran only on the embedded etcd files (member/wal, member/snap/db), never on rdb_data or the segment files. A host power loss or kernel crash can lose acknowledged rows that are still in the OS page cache; a Milvus process crash alone should not (inferred, not tested). Metadata in embedded etcd is fdatasynced on every commit.	index Finished, type HNSW (COSINE, {"M":16,"efConstruction":128}), indexedRows 524 of 524 sealed rows, pendingRows 0; stored rows 524; LoadStateLoaded; query node: 1 sealed segment(s) with the index loaded covering 524 rows against 524 stored rows, 0 sealed without it, 0 rows in growing segments; datacoord: 1 live segment(s), 1 flushed and indexed covering 524 rows, 0 delete-log (L0) segment(s) waiting for a compaction, 3 segment(s) compacted away so far; flush, index build and load took 14.7 s, then compaction: 1 job(s) accepted by Milvus, layout ready and unchanged for 75 s, 124.1 s for the whole step; search ledger started, later state reads count the searches against the query node's own counters	yes	2.33 (1000 / QPS@1)
milvus	20261005-101815-eshoponweb	15	default@1, default@8	true	524/524	index Finished, type HNSW (COSINE, {"M":16,"efConstruction":128}), indexedRows 524 of 524 sealed rows, pendingRows 0; stored rows 524; LoadStateLoaded; query node: 1 sealed segment(s) with the index loaded covering 524 rows against 524 stored rows, 0 sealed without it, 0 rows in growing segments; datacoord: 1 live segment(s), 1 flushed and indexed covering 524 rows, 0 delete-log (L0) segment(s) waiting for a compaction, 3 segment(s) compacted away so far; search ledger since the index finished: the sink sent 0 searches (searchParams.params.ef=100, Strong consistency), the query node counted 0 search requests for this collection, segment searches Sealed +0 and Growing +0, the same sealed segments with the same loaded index builds at both readings, segments compacted away +0	true	524/524	1 sealed segment covering 524 rows / 1 sealed segment covering 524 rows	Writes are not fsynced. Standalone uses the default message queue rocksmq (RocksDB, /var/lib/milvus/rdb_data, mq.type default) and flushed segments go to local-disk object storage (COMMON_STORAGETYPE=local in milvus.compose.yaml). Measured 2026-10-04 with strace over 30 acknowledged single-row upserts and one flush: fdatasync ran only on the embedded etcd files (member/wal, member/snap/db), never on rdb_data or the segment files. A host power loss or kernel crash can lose acknowledged rows that are still in the OS page cache; a Milvus process crash alone should not (inferred, not tested). Metadata in embedded etcd is fdatasynced on every commit.	index Finished, type HNSW (COSINE, {"M":16,"efConstruction":128}), indexedRows 524 of 524 sealed rows, pendingRows 0; stored rows 524; LoadStateLoaded; query node: 1 sealed segment(s) with the index loaded covering 524 rows against 524 stored rows, 0 sealed without it, 0 rows in growing segments; datacoord: 1 live segment(s), 1 flushed and indexed covering 524 rows, 0 delete-log (L0) segment(s) waiting for a compaction, 3 segment(s) compacted away so far; flush, index build and load took 14.7 s, then compaction: 1 job(s) accepted by Milvus, layout ready and unchanged for 75 s, 124.1 s for the whole step; search ledger started, later state reads count the searches against the query node's own counters	yes	2.33 (1000 / QPS@1)
weaviate	20261005-073329-eshoponweb	4	default@1, default@8	true	?/524	shard JOIqxslXLYy9 vectorIndexingStatus READY, vectorQueueLength 0, node status objectCount 0 (refreshed only when the memtable is flushed, so it lags a minute and does not decide readiness), schema shard JOIqxslXLYy9 status READY, Aggregate count 524, Aggregate nearVector with objectLimit 524 reached 524, Weaviate reports no count of vectors in the HNSW index, so indexed vectors are not reported	true	?/524	-	Weaviate 1.39.8 defaults, weaviate.compose.yaml sets no persistence variable: every object is appended to the LSM write-ahead log with a plain write and no fsync, and the log is fsynced only when its memtable is flushed, 60 seconds after the last write (PERSISTENCE_MEMTABLES_FLUSH_IDLE_AFTER_SECONDS default; measured with strace: 2,080 writes into the objects log during a 2,000-object load, the first fsync 60 s after the last write), so a power cut can lose the last minute of writes; the HNSW commit log is buffered inside the process (77 writes for 2,000 vectors), so a killed process loses the newest vectors from the vector index while their objects survive (measured with docker kill, which is SIGKILL, one second after the load and a restart, two runs each: 0 to 1 of 50, 264 to 267 of 300 and 1,992 to 1,997 of 2,000 stored objects were still reachable through a vector search)	HNSW is updated inside every batch, nothing to build; confirmed in 0.0 s: shard JOIqxslXLYy9 vectorIndexingStatus READY, vectorQueueLength 0, node status objectCount 0 (refreshed only when the memtable is flushed, so it lags a minute and does not decide readiness), schema shard JOIqxslXLYy9 status READY, Aggregate count 524, Aggregate nearVector with objectLimit 524 reached 524, Weaviate reports no count of vectors in the HNSW index, so indexed vectors are not reported	yes	5.84 (1000 / QPS@1)
weaviate	20261005-085448-eshoponweb	11	default@8, default@1	true	?/524	shard VyfgMkQG0NE1 vectorIndexingStatus READY, vectorQueueLength 0, node status objectCount 0 (refreshed only when the memtable is flushed, so it lags a minute and does not decide readiness), schema shard VyfgMkQG0NE1 status READY, Aggregate count 524, Aggregate nearVector with objectLimit 524 reached 524, Weaviate reports no count of vectors in the HNSW index, so indexed vectors are not reported	true	?/524	-	Weaviate 1.39.8 defaults, weaviate.compose.yaml sets no persistence variable: every object is appended to the LSM write-ahead log with a plain write and no fsync, and the log is fsynced only when its memtable is flushed, 60 seconds after the last write (PERSISTENCE_MEMTABLES_FLUSH_IDLE_AFTER_SECONDS default; measured with strace: 2,080 writes into the objects log during a 2,000-object load, the first fsync 60 s after the last write), so a power cut can lose the last minute of writes; the HNSW commit log is buffered inside the process (77 writes for 2,000 vectors), so a killed process loses the newest vectors from the vector index while their objects survive (measured with docker kill, which is SIGKILL, one second after the load and a restart, two runs each: 0 to 1 of 50, 264 to 267 of 300 and 1,992 to 1,997 of 2,000 stored objects were still reachable through a vector search)	HNSW is updated inside every batch, nothing to build; confirmed in 0.0 s: shard VyfgMkQG0NE1 vectorIndexingStatus READY, vectorQueueLength 0, node status objectCount 0 (refreshed only when the memtable is flushed, so it lags a minute and does not decide readiness), schema shard VyfgMkQG0NE1 status READY, Aggregate count 524, Aggregate nearVector with objectLimit 524 reached 524, Weaviate reports no count of vectors in the HNSW index, so indexed vectors are not reported	yes	5.83 (1000 / QPS@1)
weaviate	20261005-101815-eshoponweb	18	default@8, default@1	true	?/524	shard KRx7woimLViV vectorIndexingStatus READY, vectorQueueLength 0, node status objectCount 0 (refreshed only when the memtable is flushed, so it lags a minute and does not decide readiness), schema shard KRx7woimLViV status READY, Aggregate count 524, Aggregate nearVector with objectLimit 524 reached 524, Weaviate reports no count of vectors in the HNSW index, so indexed vectors are not reported	true	?/524	-	Weaviate 1.39.8 defaults, weaviate.compose.yaml sets no persistence variable: every object is appended to the LSM write-ahead log with a plain write and no fsync, and the log is fsynced only when its memtable is flushed, 60 seconds after the last write (PERSISTENCE_MEMTABLES_FLUSH_IDLE_AFTER_SECONDS default; measured with strace: 2,080 writes into the objects log during a 2,000-object load, the first fsync 60 s after the last write), so a power cut can lose the last minute of writes; the HNSW commit log is buffered inside the process (77 writes for 2,000 vectors), so a killed process loses the newest vectors from the vector index while their objects survive (measured with docker kill, which is SIGKILL, one second after the load and a restart, two runs each: 0 to 1 of 50, 264 to 267 of 300 and 1,992 to 1,997 of 2,000 stored objects were still reachable through a vector search)	HNSW is updated inside every batch, nothing to build; confirmed in 0.0 s: shard KRx7woimLViV vectorIndexingStatus READY, vectorQueueLength 0, node status objectCount 0 (refreshed only when the memtable is flushed, so it lags a minute and does not decide readiness), schema shard KRx7woimLViV status READY, Aggregate count 524, Aggregate nearVector with objectLimit 524 reached 524, Weaviate reports no count of vectors in the HNSW index, so indexed vectors are not reported	yes	5.84 (1000 / QPS@1)
chroma	20261005-073329-eshoponweb	11	default@8, default@1	true	?/524	Chroma exposes no index status (indexing_status endpoint: HTTP 500 {"error":"InternalError","message":"Method scout_logs is not implemented"}), so indexed vectors are not reported and ready only means the two counts agree to within 1 percent: count endpoint 524, a vector search asking for 524 results returned 524	true	?/524	-	SQLite rollback journal with its default synchronous=FULL under the data directory (chroma.compose.yaml sets IS_PERSISTENT=1 and PERSIST_DIRECTORY=/data and no sync setting): every write is committed to chroma.sqlite3 with fsync of the journal, the directory and the database file before the call returns (strace: 15 database fsyncs and 38 journal fsyncs for one create, four 500-vector upserts and one delete), and the HNSW files are written every sync_threshold=1000 vectors and rebuilt from the SQLite log after a crash; measured with kill -9 and a restart: all 50, 300 and 2,000 vectors were still stored and searchable	Chroma has no index build to wait for and exposes no index status; checked in 0.0 s: Chroma exposes no index status (indexing_status endpoint: HTTP 500 {"error":"InternalError","message":"Method scout_logs is not implemented"}), so indexed vectors are not reported and ready only means the two counts agree to within 1 percent: count endpoint 524, a vector search asking for 524 results returned 524	yes	2.05 (1000 / QPS@1)
chroma	20261005-085448-eshoponweb	13	default@1, default@8	true	?/524	Chroma exposes no index status (indexing_status endpoint: HTTP 500 {"error":"InternalError","message":"Method scout_logs is not implemented"}), so indexed vectors are not reported and ready only means the two counts agree to within 1 percent: count endpoint 524, a vector search asking for 524 results returned 524	true	?/524	-	SQLite rollback journal with its default synchronous=FULL under the data directory (chroma.compose.yaml sets IS_PERSISTENT=1 and PERSIST_DIRECTORY=/data and no sync setting): every write is committed to chroma.sqlite3 with fsync of the journal, the directory and the database file before the call returns (strace: 15 database fsyncs and 38 journal fsyncs for one create, four 500-vector upserts and one delete), and the HNSW files are written every sync_threshold=1000 vectors and rebuilt from the SQLite log after a crash; measured with kill -9 and a restart: all 50, 300 and 2,000 vectors were still stored and searchable	Chroma has no index build to wait for and exposes no index status; checked in 0.0 s: Chroma exposes no index status (indexing_status endpoint: HTTP 500 {"error":"InternalError","message":"Method scout_logs is not implemented"}), so indexed vectors are not reported and ready only means the two counts agree to within 1 percent: count endpoint 524, a vector search asking for 524 results returned 524	yes	2.06 (1000 / QPS@1)
chroma	20261005-101815-eshoponweb	5	default@8, default@1	true	?/524	Chroma exposes no index status (indexing_status endpoint: HTTP 500 {"error":"InternalError","message":"Method scout_logs is not implemented"}), so indexed vectors are not reported and ready only means the two counts agree to within 1 percent: count endpoint 524, a vector search asking for 524 results returned 524	true	?/524	-	SQLite rollback journal with its default synchronous=FULL under the data directory (chroma.compose.yaml sets IS_PERSISTENT=1 and PERSIST_DIRECTORY=/data and no sync setting): every write is committed to chroma.sqlite3 with fsync of the journal, the directory and the database file before the call returns (strace: 15 database fsyncs and 38 journal fsyncs for one create, four 500-vector upserts and one delete), and the HNSW files are written every sync_threshold=1000 vectors and rebuilt from the SQLite log after a crash; measured with kill -9 and a restart: all 50, 300 and 2,000 vectors were still stored and searchable	Chroma has no index build to wait for and exposes no index status; checked in 0.0 s: Chroma exposes no index status (indexing_status endpoint: HTTP 500 {"error":"InternalError","message":"Method scout_logs is not implemented"}), so indexed vectors are not reported and ready only means the two counts agree to within 1 percent: count endpoint 524, a vector search asking for 524 results returned 524	yes	2.04 (1000 / QPS@1)
elasticsearch	20261005-073329-eshoponweb	9	default@8, exact, default@1	false	0/524	NO HNSW GRAPH, searches scan all 524 vectors: 1 segment(s), 524 vectors, total_vex_size_bytes 0 (_stats dense_vector), index_options hnsw m=16 ef_construction=128; Lucene builds no graph for a segment this small (measured at 1,024 dimensions: 1,042 vectors none, 1,043 vectors a graph), so default search equals exact search	false	0/524	1 segment / 1 segment	Every acknowledged bulk request is fsynced to the translog before the answer: index.translog.durability=request, the Elasticsearch default, which neither this sink nor elasticsearch.compose.yaml overrides (ElasticsearchReadinessTests reads it back from the live index). By that setting a process crash or power loss loses no acknowledged write; this is read from the setting, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	FAILED after 0.4 s: NO HNSW GRAPH, searches scan all 524 vectors: 1 segment(s), 524 vectors, total_vex_size_bytes 0 (_stats dense_vector), index_options hnsw m=16 ef_construction=128; Lucene builds no graph for a segment this small (measured at 1,024 dimensions: 1,042 vectors none, 1,043 vectors a graph), so default search equals exact search	yes	1.33 (1000 / QPS@1)
elasticsearch	20261005-085448-eshoponweb	17	exact, default@1, default@8	false	0/524	NO HNSW GRAPH, searches scan all 524 vectors: 1 segment(s), 524 vectors, total_vex_size_bytes 0 (_stats dense_vector), index_options hnsw m=16 ef_construction=128; Lucene builds no graph for a segment this small (measured at 1,024 dimensions: 1,042 vectors none, 1,043 vectors a graph), so default search equals exact search	false	0/524	1 segment / 1 segment	Every acknowledged bulk request is fsynced to the translog before the answer: index.translog.durability=request, the Elasticsearch default, which neither this sink nor elasticsearch.compose.yaml overrides (ElasticsearchReadinessTests reads it back from the live index). By that setting a process crash or power loss loses no acknowledged write; this is read from the setting, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	FAILED after 0.4 s: NO HNSW GRAPH, searches scan all 524 vectors: 1 segment(s), 524 vectors, total_vex_size_bytes 0 (_stats dense_vector), index_options hnsw m=16 ef_construction=128; Lucene builds no graph for a segment this small (measured at 1,024 dimensions: 1,042 vectors none, 1,043 vectors a graph), so default search equals exact search	yes	1.33 (1000 / QPS@1)
elasticsearch	20261005-101815-eshoponweb	16	exact, default@8, default@1	false	0/524	NO HNSW GRAPH, searches scan all 524 vectors: 1 segment(s), 524 vectors, total_vex_size_bytes 0 (_stats dense_vector), index_options hnsw m=16 ef_construction=128; Lucene builds no graph for a segment this small (measured at 1,024 dimensions: 1,042 vectors none, 1,043 vectors a graph), so default search equals exact search	false	0/524	1 segment / 1 segment	Every acknowledged bulk request is fsynced to the translog before the answer: index.translog.durability=request, the Elasticsearch default, which neither this sink nor elasticsearch.compose.yaml overrides (ElasticsearchReadinessTests reads it back from the live index). By that setting a process crash or power loss loses no acknowledged write; this is read from the setting, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	FAILED after 0.4 s: NO HNSW GRAPH, searches scan all 524 vectors: 1 segment(s), 524 vectors, total_vex_size_bytes 0 (_stats dense_vector), index_options hnsw m=16 ef_construction=128; Lucene builds no graph for a segment this small (measured at 1,024 dimensions: 1,042 vectors none, 1,043 vectors a graph), so default search equals exact search	yes	1.33 (1000 / QPS@1)
opensearch	20261005-073329-eshoponweb	12	exact, default@8, default@1	true	524/524	every segment searched through its HNSW graph, covering 524 of 524 vectors: 1 segment(s), 0 merge(s) running, profiled probe search: ann_search_count 1 (segments tried through a graph), exact_search_count 0 (of those, scanned instead), approximate_threshold 0; force-merged to one segment on purpose, so one graph answers every search	true	524/524	1 segment / 1 segment	Every acknowledged bulk request is fsynced to the translog before the answer: index.translog.durability=request, the OpenSearch default, which neither this sink nor opensearch.compose.yaml overrides (OpenSearchReadinessTests reads it back from the live index). By that setting a process crash or power loss loses no acknowledged write; this is read from the setting, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	force-merged to one segment, graph ready after 0.9 s: every segment searched through its HNSW graph, covering 524 of 524 vectors: 1 segment(s), 0 merge(s) running, profiled probe search: ann_search_count 1 (segments tried through a graph), exact_search_count 0 (of those, scanned instead), approximate_threshold 0; force-merged to one segment on purpose, so one graph answers every search	yes	2.02 (1000 / QPS@1)
opensearch	20261005-085448-eshoponweb	2	default@8, exact, default@1	true	524/524	every segment searched through its HNSW graph, covering 524 of 524 vectors: 1 segment(s), 0 merge(s) running, profiled probe search: ann_search_count 1 (segments tried through a graph), exact_search_count 0 (of those, scanned instead), approximate_threshold 0; force-merged to one segment on purpose, so one graph answers every search	true	524/524	1 segment / 1 segment	Every acknowledged bulk request is fsynced to the translog before the answer: index.translog.durability=request, the OpenSearch default, which neither this sink nor opensearch.compose.yaml overrides (OpenSearchReadinessTests reads it back from the live index). By that setting a process crash or power loss loses no acknowledged write; this is read from the setting, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	force-merged to one segment, graph ready after 0.9 s: every segment searched through its HNSW graph, covering 524 of 524 vectors: 1 segment(s), 0 merge(s) running, profiled probe search: ann_search_count 1 (segments tried through a graph), exact_search_count 0 (of those, scanned instead), approximate_threshold 0; force-merged to one segment on purpose, so one graph answers every search	yes	2.02 (1000 / QPS@1)
opensearch	20261005-101815-eshoponweb	2	default@8, exact, default@1	true	524/524	every segment searched through its HNSW graph, covering 524 of 524 vectors: 1 segment(s), 0 merge(s) running, profiled probe search: ann_search_count 1 (segments tried through a graph), exact_search_count 0 (of those, scanned instead), approximate_threshold 0; force-merged to one segment on purpose, so one graph answers every search	true	524/524	1 segment / 1 segment	Every acknowledged bulk request is fsynced to the translog before the answer: index.translog.durability=request, the OpenSearch default, which neither this sink nor opensearch.compose.yaml overrides (OpenSearchReadinessTests reads it back from the live index). By that setting a process crash or power loss loses no acknowledged write; this is read from the setting, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	force-merged to one segment, graph ready after 0.9 s: every segment searched through its HNSW graph, covering 524 of 524 vectors: 1 segment(s), 0 merge(s) running, profiled probe search: ann_search_count 1 (segments tried through a graph), exact_search_count 0 (of those, scanned instead), approximate_threshold 0; force-merged to one segment on purpose, so one graph answers every search	yes	2.01 (1000 / QPS@1)
typesense	20261005-073329-eshoponweb	14	default@8, default@1, exact	true	524/524	HNSW graph returns 524 of 524 vectors, no writes queued: num_documents 524, pending_write_batches 0, health ok, unfiltered vector query with k above the count returned 524; the graph is built in memory during each write, so there is no later build step	true	524/524	-	Every acknowledged write is appended to Typesense's raft log and fsynced before the answer: braft raft_sync=true with raft_sync_policy=0 (sync immediately), read from the running container's brpc /flags page on 2026-10-04. A restart replays the log from the last snapshot (typesense.compose.yaml sets TYPESENSE_SNAPSHOT_INTERVAL_SECONDS=300) and rebuilds the in-memory HNSW graph, so by those settings a crash loses no acknowledged write, but the restart is slow after a big load. This is read from the settings, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	nothing to build, Typesense inserts into the HNSW graph while writing; ready after 0.0 s: HNSW graph returns 524 of 524 vectors, no writes queued: num_documents 524, pending_write_batches 0, health ok, unfiltered vector query with k above the count returned 524; the graph is built in memory during each write, so there is no later build step	yes	4.10 (1000 / QPS@1)
typesense	20261005-085448-eshoponweb	8	default@1, default@8, exact	true	524/524	HNSW graph returns 524 of 524 vectors, no writes queued: num_documents 524, pending_write_batches 0, health ok, unfiltered vector query with k above the count returned 524; the graph is built in memory during each write, so there is no later build step	true	524/524	-	Every acknowledged write is appended to Typesense's raft log and fsynced before the answer: braft raft_sync=true with raft_sync_policy=0 (sync immediately), read from the running container's brpc /flags page on 2026-10-04. A restart replays the log from the last snapshot (typesense.compose.yaml sets TYPESENSE_SNAPSHOT_INTERVAL_SECONDS=300) and rebuilds the in-memory HNSW graph, so by those settings a crash loses no acknowledged write, but the restart is slow after a big load. This is read from the settings, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	nothing to build, Typesense inserts into the HNSW graph while writing; ready after 0.0 s: HNSW graph returns 524 of 524 vectors, no writes queued: num_documents 524, pending_write_batches 0, health ok, unfiltered vector query with k above the count returned 524; the graph is built in memory during each write, so there is no later build step	yes	4.10 (1000 / QPS@1)
typesense	20261005-101815-eshoponweb	8	default@8, default@1, exact	true	524/524	HNSW graph returns 524 of 524 vectors, no writes queued: num_documents 524, pending_write_batches 0, health ok, unfiltered vector query with k above the count returned 524; the graph is built in memory during each write, so there is no later build step	true	524/524	-	Every acknowledged write is appended to Typesense's raft log and fsynced before the answer: braft raft_sync=true with raft_sync_policy=0 (sync immediately), read from the running container's brpc /flags page on 2026-10-04. A restart replays the log from the last snapshot (typesense.compose.yaml sets TYPESENSE_SNAPSHOT_INTERVAL_SECONDS=300) and rebuilds the in-memory HNSW graph, so by those settings a crash loses no acknowledged write, but the restart is slow after a big load. This is read from the settings, not shown by pulling power. One node and no replicas, so a lost disk loses the data.	nothing to build, Typesense inserts into the HNSW graph while writing; ready after 0.0 s: HNSW graph returns 524 of 524 vectors, no writes queued: num_documents 524, pending_write_batches 0, health ok, unfiltered vector query with k above the count returned 524; the graph is built in memory during each write, so there is no later build step	yes	4.08 (1000 / QPS@1)
vespa	20261005-073329-eshoponweb	13	default@8, exact, default@1	true	524/524	HNSW graph returns 524 of 524 vectors: totalCount 524, coverage full True, nearestNeighbor approximate:true with targetHits above the count: has_index True, algorithm "index top k", top_k_hits 524; the graph is updated while each write is applied, so there is no later build step	true	524/524	-	Vespa's transaction log server fsyncs after each commit: searchlib.translogserver usefsync=true, and an operation is searchable when it is acknowledged: proton documentdb visibilitydelay=0. Neither is overridden by this sink or by the services.xml it deploys; VespaReadinessTests reads both from the live config server. After a crash the node replays the transaction log over its last flushed data and rebuilds the in-memory HNSW graph. By those settings an acknowledged write survives a crash; this is read from the settings, not shown by pulling power. One node and min-redundancy 1, so a lost disk loses the data.	nothing to build, Vespa inserts into the HNSW graph while writing; ready after 0.0 s: HNSW graph returns 524 of 524 vectors: totalCount 524, coverage full True, nearestNeighbor approximate:true with targetHits above the count: has_index True, algorithm "index top k", top_k_hits 524; the graph is updated while each write is applied, so there is no later build step	yes	1.91 (1000 / QPS@1)
vespa	20261005-085448-eshoponweb	15	default@8, exact, default@1	true	524/524	HNSW graph returns 524 of 524 vectors: totalCount 524, coverage full True, nearestNeighbor approximate:true with targetHits above the count: has_index True, algorithm "index top k", top_k_hits 524; the graph is updated while each write is applied, so there is no later build step	true	524/524	-	Vespa's transaction log server fsyncs after each commit: searchlib.translogserver usefsync=true, and an operation is searchable when it is acknowledged: proton documentdb visibilitydelay=0. Neither is overridden by this sink or by the services.xml it deploys; VespaReadinessTests reads both from the live config server. After a crash the node replays the transaction log over its last flushed data and rebuilds the in-memory HNSW graph. By those settings an acknowledged write survives a crash; this is read from the settings, not shown by pulling power. One node and min-redundancy 1, so a lost disk loses the data.	nothing to build, Vespa inserts into the HNSW graph while writing; ready after 0.1 s: HNSW graph returns 524 of 524 vectors: totalCount 524, coverage full True, nearestNeighbor approximate:true with targetHits above the count: has_index True, algorithm "index top k", top_k_hits 524; the graph is updated while each write is applied, so there is no later build step	yes	1.91 (1000 / QPS@1)
vespa	20261005-101815-eshoponweb	12	exact, default@8, default@1	true	524/524	HNSW graph returns 524 of 524 vectors: totalCount 524, coverage full True, nearestNeighbor approximate:true with targetHits above the count: has_index True, algorithm "index top k", top_k_hits 524; the graph is updated while each write is applied, so there is no later build step	true	524/524	-	Vespa's transaction log server fsyncs after each commit: searchlib.translogserver usefsync=true, and an operation is searchable when it is acknowledged: proton documentdb visibilitydelay=0. Neither is overridden by this sink or by the services.xml it deploys; VespaReadinessTests reads both from the live config server. After a crash the node replays the transaction log over its last flushed data and rebuilds the in-memory HNSW graph. By those settings an acknowledged write survives a crash; this is read from the settings, not shown by pulling power. One node and min-redundancy 1, so a lost disk loses the data.	nothing to build, Vespa inserts into the HNSW graph while writing; ready after 0.1 s: HNSW graph returns 524 of 524 vectors: totalCount 524, coverage full True, nearestNeighbor approximate:true with targetHits above the count: has_index True, algorithm "index top k", top_k_hits 524; the graph is updated while each write is applied, so there is no later build step	yes	1.90 (1000 / QPS@1)
duckdb	20261005-073329-eshoponweb	10	exact, default@8, default@1	true	524/524	duckdb_indexes() lists gvb_gvbbench_eshoponweb_hnsw, pragma_hnsw_index_info() counts 524 vectors of 524 rows, EXPLAIN of the default search shows HNSW_INDEX_SCAN on it = True	true	524/524	-	DuckDB's write-ahead log is fsynced at every commit and no DuckDbSink setting changes that (checkpoint_threshold=256MB only spaces out the checkpoints that write the database file; measured with strace: 42 WAL fsyncs for 40 single-record commits plus 2 setup statements), so an operating-system crash or power cut loses no committed row; measured with kill -9 right after the last commit and a reopen: all 50, 300 and 2,000 rows and an HNSW index that counted the same number were recovered from the log; not tested and documented by DuckDB: the HNSW index is file-backed only through hnsw_enable_experimental_persistence = true, which this sink turns on, and WAL recovery for such custom indexes is not complete, so a crash during a checkpoint or a later commit can damage the index while the rows survive	HNSW is maintained inside every transaction, nothing to build; confirmed in 0.01 s: duckdb_indexes() lists gvb_gvbbench_eshoponweb_hnsw, pragma_hnsw_index_info() counts 524 vectors of 524 rows, EXPLAIN of the default search shows HNSW_INDEX_SCAN on it = True	yes	3.56 (1000 / QPS@1)
duckdb	20261005-085448-eshoponweb	4	exact, default@8, default@1	true	524/524	duckdb_indexes() lists gvb_gvbbench_eshoponweb_hnsw, pragma_hnsw_index_info() counts 524 vectors of 524 rows, EXPLAIN of the default search shows HNSW_INDEX_SCAN on it = True	true	524/524	-	DuckDB's write-ahead log is fsynced at every commit and no DuckDbSink setting changes that (checkpoint_threshold=256MB only spaces out the checkpoints that write the database file; measured with strace: 42 WAL fsyncs for 40 single-record commits plus 2 setup statements), so an operating-system crash or power cut loses no committed row; measured with kill -9 right after the last commit and a reopen: all 50, 300 and 2,000 rows and an HNSW index that counted the same number were recovered from the log; not tested and documented by DuckDB: the HNSW index is file-backed only through hnsw_enable_experimental_persistence = true, which this sink turns on, and WAL recovery for such custom indexes is not complete, so a crash during a checkpoint or a later commit can damage the index while the rows survive	HNSW is maintained inside every transaction, nothing to build; confirmed in 0.01 s: duckdb_indexes() lists gvb_gvbbench_eshoponweb_hnsw, pragma_hnsw_index_info() counts 524 vectors of 524 rows, EXPLAIN of the default search shows HNSW_INDEX_SCAN on it = True	yes	3.56 (1000 / QPS@1)
duckdb	20261005-101815-eshoponweb	3	default@1, default@8, exact	true	524/524	duckdb_indexes() lists gvb_gvbbench_eshoponweb_hnsw, pragma_hnsw_index_info() counts 524 vectors of 524 rows, EXPLAIN of the default search shows HNSW_INDEX_SCAN on it = True	true	524/524	-	DuckDB's write-ahead log is fsynced at every commit and no DuckDbSink setting changes that (checkpoint_threshold=256MB only spaces out the checkpoints that write the database file; measured with strace: 42 WAL fsyncs for 40 single-record commits plus 2 setup statements), so an operating-system crash or power cut loses no committed row; measured with kill -9 right after the last commit and a reopen: all 50, 300 and 2,000 rows and an HNSW index that counted the same number were recovered from the log; not tested and documented by DuckDB: the HNSW index is file-backed only through hnsw_enable_experimental_persistence = true, which this sink turns on, and WAL recovery for such custom indexes is not complete, so a crash during a checkpoint or a later commit can damage the index while the rows survive	HNSW is maintained inside every transaction, nothing to build; confirmed in 0.01 s: duckdb_indexes() lists gvb_gvbbench_eshoponweb_hnsw, pragma_hnsw_index_info() counts 524 vectors of 524 rows, EXPLAIN of the default search shows HNSW_INDEX_SCAN on it = True	yes	3.54 (1000 / QPS@1)
sqlitevec	20261005-073329-eshoponweb	6	default@8, default@1, exact	true	?/524	no index, exact scan by design: gvb_gvbbench_eshoponweb is a vec0 virtual table holding 524 vectors and every search compares all of them (EXPLAIN QUERY PLAN: SCAN gvb_gvbbench_eshoponweb VIRTUAL TABLE INDEX 0:3{___}___ \| USE TEMP B-TREE FOR ORDER BY)	true	?/524	-	PRAGMA journal_mode=WAL and PRAGMA synchronous=NORMAL (set by this sink when it opens the file): each commit is appended to the -wal file and handed to the operating system, but the WAL is fsynced only when SQLite checkpoints it (measured with strace: 40 single-record commits caused 3 WAL fsyncs), so a crash of the process loses nothing (measured with kill -9 and a reopen: all 50, 300 and 2,000 rows were there), while an operating-system crash or power cut can lose the newest commits since the last checkpoint and leaves the database consistent	nothing to build, every search scans all vectors; checked in 0.00 s: no index, exact scan by design: gvb_gvbbench_eshoponweb is a vec0 virtual table holding 524 vectors and every search compares all of them (EXPLAIN QUERY PLAN: SCAN gvb_gvbbench_eshoponweb VIRTUAL TABLE INDEX 0:3{___}___ \| USE TEMP B-TREE FOR ORDER BY)	yes	1.84 (1000 / QPS@1)
sqlitevec	20261005-085448-eshoponweb	6	exact, default@8, default@1	true	?/524	no index, exact scan by design: gvb_gvbbench_eshoponweb is a vec0 virtual table holding 524 vectors and every search compares all of them (EXPLAIN QUERY PLAN: SCAN gvb_gvbbench_eshoponweb VIRTUAL TABLE INDEX 0:3{___}___ \| USE TEMP B-TREE FOR ORDER BY)	true	?/524	-	PRAGMA journal_mode=WAL and PRAGMA synchronous=NORMAL (set by this sink when it opens the file): each commit is appended to the -wal file and handed to the operating system, but the WAL is fsynced only when SQLite checkpoints it (measured with strace: 40 single-record commits caused 3 WAL fsyncs), so a crash of the process loses nothing (measured with kill -9 and a reopen: all 50, 300 and 2,000 rows were there), while an operating-system crash or power cut can lose the newest commits since the last checkpoint and leaves the database consistent	nothing to build, every search scans all vectors; checked in 0.00 s: no index, exact scan by design: gvb_gvbbench_eshoponweb is a vec0 virtual table holding 524 vectors and every search compares all of them (EXPLAIN QUERY PLAN: SCAN gvb_gvbbench_eshoponweb VIRTUAL TABLE INDEX 0:3{___}___ \| USE TEMP B-TREE FOR ORDER BY)	yes	1.89 (1000 / QPS@1)
sqlitevec	20261005-101815-eshoponweb	13	exact, default@8, default@1	true	?/524	no index, exact scan by design: gvb_gvbbench_eshoponweb is a vec0 virtual table holding 524 vectors and every search compares all of them (EXPLAIN QUERY PLAN: SCAN gvb_gvbbench_eshoponweb VIRTUAL TABLE INDEX 0:3{___}___ \| USE TEMP B-TREE FOR ORDER BY)	true	?/524	-	PRAGMA journal_mode=WAL and PRAGMA synchronous=NORMAL (set by this sink when it opens the file): each commit is appended to the -wal file and handed to the operating system, but the WAL is fsynced only when SQLite checkpoints it (measured with strace: 40 single-record commits caused 3 WAL fsyncs), so a crash of the process loses nothing (measured with kill -9 and a reopen: all 50, 300 and 2,000 rows were there), while an operating-system crash or power cut can lose the newest commits since the last checkpoint and leaves the database consistent	nothing to build, every search scans all vectors; checked in 0.00 s: no index, exact scan by design: gvb_gvbbench_eshoponweb is a vec0 virtual table holding 524 vectors and every search compares all of them (EXPLAIN QUERY PLAN: SCAN gvb_gvbbench_eshoponweb VIRTUAL TABLE INDEX 0:3{___}___ \| USE TEMP B-TREE FOR ORDER BY)	yes	1.84 (1000 / QPS@1)

Flags

target	flag	runs	detail
oracle	unsettled-target	3 of 3	not settled: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 6,134 searches (0 failed) at 1 searcher; p50 of the last windows 2.383, 2.353, 2.360 ms (windows of at least 2 s and 100 searches); trial of 1,220 searches in 3.0 s at 1 searcher: p50 2.382 ms against the settled p50 2.360 ms, 1% apart (limit 10%); default@8: warm-up 15.0 s and 43,925 searches (0 failed) at 8 searchers; QPS of the last windows 2,416, 3,480, 2,581 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 9,374 searches in 3.0 s at 8 searchers: 3,124 QPS against the settled 2,581 QPS, 17% apart (limit 10%), so the warm-up was EXTENDED once (120.3 s and 343,792 searches (0 failed) at 8 searchers; QPS of the last windows 3,449, 2,488, 3,050 (windows of at least 2 s and 100 searches), the 120 s cap ran out); second trial of 9,654 searches in 3.0 s at 8 searchers: 3,217 QPS against the settled 3,050 QPS, 5% apart (limit 10%); still disagreeing after the extension; default@1: warm-up 15.0 s and 16,210 searches (0 failed) at 1 searcher; p50 of the last windows 0.894, 0.885, 0.895 ms (windows of at least 2 s and 100 searches); trial of 3,375 searches in 3.0 s at 1 searcher: p50 0.867 ms against the settled p50 0.894 ms, 3% apart (limit 10%). Its numbers may still include warm-up; rerun before quoting them. (1 run); not settled: latency had NOT settled when timing began for default@1, default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 5,949 searches (0 failed) at 1 searcher; p50 of the last windows 2.363, 2.376, 2.356 ms (windows of at least 2 s and 100 searches); trial of 1,229 searches in 3.0 s at 1 searcher: p50 2.387 ms against the settled p50 2.363 ms, 1% apart (limit 10%); default@1: warm-up 15.0 s and 16,397 searches (0 failed) at 1 searcher; p50 of the last windows 0.860, 0.892, 0.913 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 3,246 searches in 3.0 s at 1 searcher: p50 0.900 ms against the settled p50 0.892 ms, 1% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 32,617 searches (0 failed) at 1 searcher; p50 of the last windows 0.883, 0.857, 0.926 ms (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 3,341 searches in 3.0 s at 1 searcher: p50 0.874 ms against the settled p50 0.883 ms, 1% apart (limit 10%); still disagreeing after the extension; default@8: warm-up 15.0 s and 48,930 searches (0 failed) at 8 searchers; QPS of the last windows 3,514, 2,364, 3,100 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 7,829 searches in 3.1 s at 8 searchers: 2,519 QPS against the settled 3,100 QPS, 23% apart (limit 10%), so the warm-up was EXTENDED once (120.0 s and 315,148 searches (0 failed) at 8 searchers; QPS of the last windows 2,207, 2,452, 2,930 (windows of at least 2 s and 100 searches), the 120 s cap ran out); second trial of 7,269 searches in 3.3 s at 8 searchers: 2,230 QPS against the settled 2,452 QPS, 10% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them. (1 run); not settled: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 6,064 searches (0 failed) at 1 searcher; p50 of the last windows 2.371, 2.350, 2.331 ms (windows of at least 2 s and 100 searches); trial of 1,244 searches in 3.0 s at 1 searcher: p50 2.356 ms against the settled p50 2.350 ms, 0% apart (limit 10%); default@1: warm-up 15.0 s and 16,495 searches (0 failed) at 1 searcher; p50 of the last windows 0.888, 0.870, 0.904 ms (windows of at least 2 s and 100 searches); trial of 3,251 searches in 3.0 s at 1 searcher: p50 0.896 ms against the settled p50 0.888 ms, 1% apart (limit 10%); default@8: warm-up 15.3 s and 44,258 searches (0 failed) at 8 searchers; QPS of the last windows 3,062, 2,834, 2,622 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 9,357 searches in 3.0 s at 8 searchers: 3,118 QPS against the settled 2,834 QPS, 9% apart (limit 10%), so the warm-up was EXTENDED once (120.2 s and 344,269 searches (0 failed) at 8 searchers; QPS of the last windows 3,394, 2,474, 2,998 (windows of at least 2 s and 100 searches), the 120 s cap ran out); second trial of 9,022 searches in 3.0 s at 8 searchers: 3,006 QPS against the settled 2,998 QPS, 0% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them. (1 run)
redis	unsettled-target	3 of 3	not settled: latency had NOT settled when timing began for exact (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). default@1: warm-up 15.0 s and 39,275 searches (0 failed) at 1 searcher; p50 of the last windows 0.383, 0.380, 0.382 ms (windows of at least 2 s and 100 searches); trial of 8,168 searches in 3.0 s at 1 searcher: p50 0.349 ms against the settled p50 0.382 ms, 10% apart (limit 10%); default@8: warm-up 15.0 s and 76,531 searches (0 failed) at 8 searchers; QPS of the last windows 5,217, 5,302, 5,056 (windows of at least 2 s and 100 searches); trial of 15,028 searches in 3.0 s at 8 searchers: 5,007 QPS against the settled 5,217 QPS, 4% apart (limit 10%); exact: warm-up 15.0 s and 41,741 searches (0 failed) at 1 searcher; p50 of the last windows 0.364, 0.362, 0.324 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 7,959 searches in 3.0 s at 1 searcher: p50 0.380 ms against the settled p50 0.362 ms, 5% apart (limit 10%), so the warm-up was EXTENDED once (36.0 s and 99,849 searches (0 failed) at 1 searcher; p50 of the last windows 0.362, 0.353, 0.342 ms (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 8,351 searches in 3.0 s at 1 searcher: p50 0.359 ms against the settled p50 0.353 ms, 2% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them. (1 run); not settled: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). default@1: warm-up 15.0 s and 39,692 searches (0 failed) at 1 searcher; p50 of the last windows 0.352, 0.350, 0.369 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 8,035 searches in 3.0 s at 1 searcher: p50 0.355 ms against the settled p50 0.352 ms, 1% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 77,908 searches (0 failed) at 1 searcher; p50 of the last windows 0.379, 0.384, 0.376 ms (windows of at least 2 s and 100 searches)); second trial of 7,691 searches in 3.0 s at 1 searcher: p50 0.388 ms against the settled p50 0.379 ms, 3% apart (limit 10%); settled after the extension; exact: warm-up 15.0 s and 41,325 searches (0 failed) at 1 searcher; p50 of the last windows 0.367, 0.376, 0.359 ms (windows of at least 2 s and 100 searches); trial of 8,543 searches in 3.0 s at 1 searcher: p50 0.342 ms against the settled p50 0.367 ms, 7% apart (limit 10%); default@8: warm-up 15.0 s and 75,695 searches (0 failed) at 8 searchers; QPS of the last windows 4,921, 5,016, 5,277 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 15,098 searches in 3.0 s at 8 searchers: 5,030 QPS against the settled 5,016 QPS, 0% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 153,806 searches (0 failed) at 8 searchers; QPS of the last windows 5,068, 5,484, 4,940 (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 15,130 searches in 3.0 s at 8 searchers: 5,041 QPS against the settled 5,068 QPS, 1% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them. (1 run); not settled: latency had NOT settled when timing began for exact (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 41,314 searches (0 failed) at 1 searcher; p50 of the last windows 0.336, 0.374, 0.372 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 8,416 searches in 3.0 s at 1 searcher: p50 0.335 ms against the settled p50 0.372 ms, 11% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 81,883 searches (0 failed) at 1 searcher; p50 of the last windows 0.363, 0.369, 0.338 ms (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 8,081 searches in 3.0 s at 1 searcher: p50 0.369 ms against the settled p50 0.363 ms, 2% apart (limit 10%); still disagreeing after the extension; default@1: warm-up 15.0 s and 38,516 searches (0 failed) at 1 searcher; p50 of the last windows 0.372, 0.407, 0.378 ms (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 7,842 searches in 3.0 s at 1 searcher: p50 0.377 ms against the settled p50 0.378 ms, 0% apart (limit 10%), so the warm-up was EXTENDED once (32.0 s and 82,511 searches (0 failed) at 1 searcher; p50 of the last windows 0.385, 0.380, 0.391 ms (windows of at least 2 s and 100 searches)); second trial of 7,681 searches in 3.0 s at 1 searcher: p50 0.390 ms against the settled p50 0.385 ms, 1% apart (limit 10%); settled after the extension; default@8: warm-up 15.0 s and 75,402 searches (0 failed) at 8 searchers; QPS of the last windows 4,844, 5,008, 5,010 (windows of at least 2 s and 100 searches); trial of 14,794 searches in 3.0 s at 8 searchers: 4,929 QPS against the settled 5,008 QPS, 2% apart (limit 10%). Its numbers may still include warm-up; rerun before quoting them. (1 run)
mongodb	segment-layout-differs-between-runs	3 of 3	after the load: 2 segments (20261005-073329-eshoponweb, 20261005-101815-eshoponweb); 4 segments (20261005-085448-eshoponweb); after the searches: 2 segments (20261005-073329-eshoponweb, 20261005-101815-eshoponweb); 4 segments (20261005-085448-eshoponweb). Searches ran over different layouts, so the medians mix them.
clickhouse	unsettled-target	3 of 3	not settled: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). exact: warm-up 15.0 s and 2,395 searches (0 failed) at 1 searcher; p50 of the last windows 6.058, 6.063, 6.057 ms (windows of at least 2 s and 100 searches); trial of 488 searches in 3.0 s at 1 searcher: p50 6.032 ms against the settled p50 6.058 ms, 0% apart (limit 10%); default@1: warm-up 15.0 s and 3,279 searches (0 failed) at 1 searcher; p50 of the last windows 4.472, 4.478, 4.471 ms (windows of at least 2 s and 100 searches); trial of 654 searches in 3.0 s at 1 searcher: p50 4.486 ms against the settled p50 4.472 ms, 0% apart (limit 10%); default@8: warm-up 15.0 s and 7,362 searches (0 failed) at 8 searchers; QPS of the last windows 434, 504, 522 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 1,512 searches in 3.0 s at 8 searchers: 502 QPS against the settled 504 QPS, 0% apart (limit 10%), so the warm-up was EXTENDED once (38.1 s and 18,460 searches (0 failed) at 8 searchers; QPS of the last windows 525, 524, 488 (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 1,302 searches in 3.0 s at 8 searchers: 432 QPS against the settled 524 QPS, 21% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them. (1 run); not settled: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). default@8: warm-up 15.0 s and 7,401 searches (0 failed) at 8 searchers; QPS of the last windows 458, 442, 444 (windows of at least 2 s and 100 searches); trial of 1,581 searches in 3.0 s at 8 searchers: 525 QPS against the settled 444 QPS, 16% apart (limit 10%), so the warm-up was EXTENDED once (30.0 s and 14,706 searches (0 failed) at 8 searchers; QPS of the last windows 530, 525, 452 (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 1,311 searches in 3.0 s at 8 searchers: 435 QPS against the settled 525 QPS, 21% apart (limit 10%); still disagreeing after the extension; exact: warm-up 15.0 s and 2,370 searches (0 failed) at 1 searcher; p50 of the last windows 6.089, 6.058, 6.067 ms (windows of at least 2 s and 100 searches); trial of 487 searches in 3.0 s at 1 searcher: p50 6.077 ms against the settled p50 6.067 ms, 0% apart (limit 10%); default@1: warm-up 15.0 s and 3,267 searches (0 failed) at 1 searcher; p50 of the last windows 4.489, 4.504, 4.493 ms (windows of at least 2 s and 100 searches); trial of 657 searches in 3.0 s at 1 searcher: p50 4.468 ms against the settled p50 4.493 ms, 1% apart (limit 10%). Its numbers may still include warm-up; rerun before quoting them. (1 run); not settled: latency had NOT settled when timing began for default@8 (each by its own warm-up at its own concurrency and a trial of the same pass within 10% of the warm-up's settled figure). default@1: warm-up 15.0 s and 3,232 searches (0 failed) at 1 searcher; p50 of the last windows 4.436, 4.452, 4.476 ms (windows of at least 2 s and 100 searches); trial of 655 searches in 3.0 s at 1 searcher: p50 4.479 ms against the settled p50 4.452 ms, 1% apart (limit 10%); exact: warm-up 15.0 s and 2,442 searches (0 failed) at 1 searcher; p50 of the last windows 6.029, 6.056, 6.035 ms (windows of at least 2 s and 100 searches); trial of 457 searches in 3.0 s at 1 searcher: p50 6.120 ms against the settled p50 6.035 ms, 1% apart (limit 10%); default@8: warm-up 15.0 s and 7,381 searches (0 failed) at 8 searchers; QPS of the last windows 435, 510, 524 (windows of at least 2 s and 100 searches) (its last 3 windows differed by more than 5%); trial of 1,509 searches in 3.0 s at 8 searchers: 501 QPS against the settled 510 QPS, 2% apart (limit 10%), so the warm-up was EXTENDED once (32.0 s and 15,463 searches (0 failed) at 8 searchers; QPS of the last windows 440, 445, 524 (windows of at least 2 s and 100 searches), its last 3 windows differed by more than 5%); second trial of 1,583 searches in 3.0 s at 8 searchers: 526 QPS against the settled 445 QPS, 15% apart (limit 10%); still disagreeing after the extension. Its numbers may still include warm-up; rerun before quoting them. (1 run)
elasticsearch	index-not-ready-after-load	3 of 3	ready false, 0 of 524: NO HNSW GRAPH, searches scan all 524 vectors: 1 segment(s), 524 vectors, total_vex_size_bytes 0 (_stats dense_vector), index_options hnsw m=16 ef_construction=128; Lucene builds no graph for a segment this small (measured at 1,024 dimensions: 1,042 vectors none, 1,043 vectors a graph), so default search equals exact search
elasticsearch	index-not-ready-after-search	3 of 3	ready false, 0 of 524: NO HNSW GRAPH, searches scan all 524 vectors: 1 segment(s), 524 vectors, total_vex_size_bytes 0 (_stats dense_vector), index_options hnsw m=16 ef_construction=128; Lucene builds no graph for a segment this small (measured at 1,024 dimensions: 1,042 vectors none, 1,043 vectors a graph), so default search equals exact search
duckdb	client-engine-share-cores	3 of 3	embedded engine runs inside the client process on the client CPUs 0-1,4-5
sqlitevec	client-engine-share-cores	3 of 3	embedded engine runs inside the client process on the client CPUs 0-1,4-5

Notes

Load rows/s is reported but not ranked and does not feed any comparison: each load wrote 524 rows, which is too few to separate engines from connection set-up and first-call cost.
Runs were used together only when their build configuration, CPU governor, CPU partition, warm-up count, exact-mode seconds, seconds per level and every listed target's search settings matched; runs that differed are listed under Runs dropped. Spread is flagged when the largest value is more than 1.15 times the smallest across runs.
Engines in different bands never overlap: every run of an engine in a faster band beat every run of an engine in a slower band, and the medians on either side of a band boundary are at least 3% apart. Engines in one band are linked by overlapping slowest-to-fastest ranges or by neighboring medians less than 3% apart (an engine varies about 2% from run to run), so these runs do not separate them cleanly. Inside a band they are listed by median, and that order is not a ranking. Bands are drawn only from two runs or more.
Runs of different commands (run-all against bench) are refused, never merged, and nothing is written. A target whose engine hosting differs between the runs (container against native) is refused for that target alone, never merged: it has no row and is named under "Targets not in this report" with the reason. The largest-group rule does not apply to either.
A segment layout that differs between the runs (the engine's own count after the load or after the searches) does not refuse or drop anything: the target stays in every table and carries the segment-layout-differs-between-runs flag, which names each layout and the runs that had it.
Every target the runs hold that has no row in this report (left out of --targets, or refused for a different hosting) is named under "Targets not in this report" with its reason (0 in this report), so no measured engine is left out unsaid.

Raw files

consolidated.md is kept unedited. It still holds the sentences this page leaves out of its copy. Count: 2