# Consolidated benchmark

| item | value |
|---|---|
| created (UTC) | 2026-10-06T17:11:07Z |
| 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/20261006-130619-eshoponweb,~/ForClaude/GenericVectorBuilder/bench-results/20261006-142724-eshoponweb,~/ForClaude/GenericVectorBuilder/bench-results/20261006-154837-eshoponweb --out ~/ForClaude/GenericVectorBuilder/bench-results/candidate-v7` |
| 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 before each timed pass | time based: the pass's own search at the pass's own concurrency for at least 15 s and at least 20 searches (at most 120 s), read in windows of at least 2 s and 100 searches |
| settle check before each timed pass | a 3 s trial of the same pass must land within 10% of the warm-up's settled figure (the median of its last 3 windows, which must agree within 5%); if not, the warm-up is extended once (at least 30 s, at most 120 s) and a second trial is taken; the extension stops once the older and the newer half of its latest windows (5 to 10 windows a half, each half read as the pass reads it) agree within 5%, judged on the windows that stopped it, and the second trial must lie inside the range of the newer half's windows or within 10% of the newer half's figure; after the pass its own figure must lie within 10% of the settled figure; in the level test, the second trial and the hold, one-searcher p50s within 0.1 ms of each other agree; a pass whose trial still disagrees, or whose own figure did not hold, flags its target as unsettled |
| rehearsal before the first timed pass | every pass type at its own concurrency for 30 s each, untimed |
| least searches a warm-up must run (the --warmup setting, besides the time above) | 20 |
| exact mode seconds | 60 |

## Warm-up method as the runs recorded it

- Preparation, untimed, before any timed pass: a rehearsal of every pass type at its own concurrency for 30 s each, through the same code the passes use.
- Warm-up and settle check, untimed, right before every timed pass: the pass's own search at the pass's own number of searchers for at least 15 s and at least 20 searches (at most 120 s), read in windows of at least 2 s and 100 searches; then a 3 s trial of the same pass. The trial's figure (p50 with one searcher, QPS with several) must lie within 10% of the warm-up's settled figure (the median of its last 3 windows, which must agree within 5%); if not, the warm-up is extended once (at least 30 s, until its windows agree, at most 120 s), where an extension's windows agree when its level test passes: the older and the newer half of its latest windows, 5 to 10 windows a half, each half read as the pass reads it (the p50 of all its searches with one searcher, its searches per second with several), agree within 5%, judged on the windows that stopped it (an extension whose cap runs out with fewer than 10 windows is judged by its last 3 instead); then a second trial is taken, which must lie inside the range of the newer half's windows or within 10% of the newer half's figure, and the warm-up runs again before the pass. After the pass its own figure is held against the settled figure, within 10%. In the level test, the second trial and the hold, two one-searcher p50s no more than 0.1 ms apart agree whatever their percentage (below what this box resolves at one searcher). Each target's notes give every check, and a pass that still disagrees, or whose own figure did not hold, flags its target as unsettled. With machine control on, the check for a quiet box is made when the warm-up is announced, before it starts (a wait between the warm-up and the timed pass let the engine go cold), so by the time the clock opens that check is as old as the warm-up and the trial (about 18 s, more after an extension); each pass's conditions record that lead (quietCheckLeadSeconds). Failed untimed searches are counted per target (warmupErrors) and are not in the timed error counts.

## Runs used

| run | started (UTC) | runSeed | load average | targetOrder |
|---|---|---|---|---|
| 20261006-130619-eshoponweb | 2026-10-06T13:06:19Z | 701 | 0.81 0.48 0.28 | clickhouse, vespa, oracle, elasticsearch, sql, pgvector, sqlitevec, qdrant, opensearch, qdrant-hnsw, redis, milvus, mariadb, weaviate, mongodb, chroma, typesense, sql-diskann, duckdb |
| 20261006-142724-eshoponweb | 2026-10-06T14:27:24Z | 702 | 3.30 3.89 3.49 | opensearch, redis, qdrant-hnsw, weaviate, qdrant, mariadb, vespa, oracle, milvus, clickhouse, sql, duckdb, pgvector, elasticsearch, sql-diskann, chroma, typesense, mongodb, sqlitevec |
| 20261006-154837-eshoponweb | 2026-10-06T15:48:37Z | 703 | 4.99 3.36 3.26 | sqlitevec, mariadb, duckdb, qdrant, elasticsearch, vespa, qdrant-hnsw, sql-diskann, pgvector, weaviate, clickhouse, oracle, sql, opensearch, redis, chroma, typesense, mongodb, milvus |

## Runs dropped

(none)

## Targets not in this report

(none)

## Targets

| target | hosting | engine | index | search settings | engine settings (recorded) | durability | engine files (SHA-256) |
|---|---|---|---|---|---|---|---|
| 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) | missing | 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. | mssql.compose.yaml b7359663cc15 |
| 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 | missing | 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. | mssql.compose.yaml b7359663cc15 |
| 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 | missing | 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. | qdrant.compose.yaml eb57e55e93c1 |
| 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 | missing | 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. | qdrant.compose.yaml eb57e55e93c1 |
| 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 | missing | 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) | pgvector.compose.yaml 27549563c622 |
| 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 | missing | 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) | mariadb-bench.compose.yaml e9a2147e6f91 |
| 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 | missing | 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). | oracle-init/01-vector-memory.sh 6452e4e1953e; oracle.compose.yaml 2a7fd367012f |
| 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 | missing | 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) | redis.compose.yaml 7448634e0d92 |
| 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 | missing | 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. | mongodb.compose.yaml 4ee6f6411f1f |
| clickhouse | compose | ClickHouse 26.3.39.7 (MergeTree + vector_similarity index; image-default system logging, each log table with a TTL of 1 hour) | 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 | missing | 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). | clickhouse-config/gvb-system-logs.xml 02cc53f0f171; clickhouse.compose.yaml 560e0ae487c6 |
| 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 | missing | 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. | milvus.compose.yaml eaefecdc3671 |
| 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 | missing | 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) | weaviate.compose.yaml d96b7399662a |
| 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 | missing | 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.compose.yaml f7ed9d3c8ff7 |
| 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 | missing | 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. | elasticsearch.compose.yaml 582b9a97b8de |
| 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 | missing | 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. | opensearch.compose.yaml 028b44c40129 |
| 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 | missing | 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. | typesense.compose.yaml 96a165f62566 |
| 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 | missing | 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. | vespa.compose.yaml 3cfb702cc29f |
| 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 | missing | 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 | missing |
| 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 | missing | 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 | missing |

Every column is what the runs recorded for the engine: its description, its index and search settings, its non-default engine settings and configuration files (when a run recorded them) and its durability statement. Runs that differ in any of them are refused for that target, never merged; a column that reads missing was not recorded by any run, so a setting changed there would not show.

## 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.40 [0.39, 0.40] | 0.57 [0.56, 0.57] | 3 | - |
| 2 | mariadb | 0.63 [0.62, 0.64] | 0.48 [0.48, 0.49] | 3 | - |
| 3 | pgvector | 0.88 [0.87, 0.88] | 0.69 [0.67, 0.69] | 3 | - |
| 3 | qdrant | 0.88 [0.88, 0.89] | 0.73 [0.72, 0.74] | 3 | exact-by-design |
| 4 | qdrant-hnsw | 0.92 [0.92, 0.92] | 0.73 [0.73, 0.74] | 3 | - |
| 4 | oracle | 0.93 [0.92, 0.93] | 0.89 [0.88, 0.89] | 3 | cpu-cap |
| 5 | elasticsearch | 1.33 [1.31, 1.33] | 0.46 [0.46, 0.46] | 3 | scans-all-vectors; flags: index-not-ready-after-load, index-not-ready-after-search |
| 5 | mongodb | 1.41 [1.26, 1.41] | 0.31 [0.30, 0.31] | 3 | flags: segment-layout-differs-between-runs, busy-box |
| 6 | sqlitevec | 1.92 [1.91, 1.93] | 2.07 [2.04, 2.07] | 3 | exact-by-design; flags: client-engine-share-cores |
| 6 | vespa | 1.95 [1.95, 1.97] | 0.94 [0.94, 0.96] | 3 | - |
| 7 | opensearch | 2.03 [1.99, 2.16] | 0.47 [0.46, 0.47] | 3 | - |
| 7 | chroma | 2.11 [2.11, 2.11] | 0.48 [0.47, 0.48] | 3 | - |
| 8 | milvus | 2.32 [2.32, 2.34] | 0.57 [0.56, 0.57] | 3 | - |
| 9 | duckdb | 3.67 [3.67, 3.68] | 5.02 [5.02, 5.03] | 3 | flags: client-engine-share-cores |
| 9 | sql-diskann | 3.68 [3.60, 3.69] | 1.02 [1.02, 1.03] | 3 | - |
| 10 | sql | 4.05 [4.02, 4.06] | 1.22 [1.21, 1.22] | 3 | exact-by-design |
| 11 | typesense | 4.19 [4.18, 4.20] | 0.52 [0.52, 0.53] | 3 | - |
| 12 | clickhouse | 4.96 [4.94, 4.97] | 0.88 [0.87, 0.89] | 3 | - |
| 13 | weaviate | 5.36 [5.36, 5.37] | 0.60 [0.57, 0.61] | 3 | - |

### QPS with 8 searchers at once (higher is faster)

| band | target | median [min, max] | client CPU ms/search | runs | engine notes |
|---|---|---|---|---|---|
| 1 | mariadb | 5917.8 [5911.5, 5919.7] | 0.38 [0.37, 0.38] | 3 | - |
| 2 | redis | 5067.3 [5037.8, 5120.1] | 0.37 [0.36, 0.37] | 3 | - |
| 3 | pgvector | 3933.9 [3909.9, 4001.3] | 0.54 [0.53, 0.54] | 3 | - |
| 4 | qdrant-hnsw | 3448.3 [3440.1, 3451.9] | 0.51 [0.51, 0.52] | 3 | - |
| 5 | qdrant | 3280.1 [3273.8, 3287.0] | 0.53 [0.52, 0.53] | 3 | exact-by-design |
| 6 | oracle | 2802.2 [2655.3, 2803.4] | 0.64 [0.64, 0.65] | 3 | cpu-cap |
| 6 | elasticsearch | 2671.3 [2668.9, 2708.0] | 0.49 [0.49, 0.50] | 3 | scans-all-vectors; flags: index-not-ready-after-load, index-not-ready-after-search |
| 7 | mongodb | 2115.3 [2066.0, 2351.9] | 0.29 [0.28, 0.29] | 3 | flags: segment-layout-differs-between-runs, busy-box |
| 8 | vespa | 1526.2 [1505.7, 1564.7] | 0.88 [0.88, 0.88] | 3 | - |
| 8 | opensearch | 1476.5 [1346.3, 1516.0] | 0.51 [0.50, 0.51] | 3 | - |
| 9 | milvus | 1258.0 [1254.7, 1262.8] | 0.64 [0.63, 0.64] | 3 | - |
| 10 | sqlitevec | 1138.4 [1136.4, 1141.9] | 3.50 [3.49, 3.51] | 3 | exact-by-design; flags: client-engine-share-cores |
| 11 | chroma | 777.1 [777.1, 777.2] | 0.47 [0.47, 0.48] | 3 | - |
| 12 | sql-diskann | 682.3 [645.4, 690.7] | 1.09 [1.08, 1.11] | 3 | - |
| 13 | sql | 611.6 [602.2, 613.6] | 1.19 [1.18, 1.20] | 3 | exact-by-design |
| 14 | duckdb | 576.0 [576.0, 576.1] | 6.90 [6.90, 6.91] | 3 | flags: client-engine-share-cores |
| 14 | typesense | 575.0 [574.0, 576.1] | 0.59 [0.59, 0.59] | 3 | - |
| 15 | clickhouse | 402.4 [374.8, 428.5] | 1.06 [1.06, 1.06] | 3 | - |
| 16 | weaviate | 305.4 [304.9, 305.5] | 0.62 [0.62, 0.62] | 3 | - |

### QPS with one searcher (higher is faster)

| band | target | median [min, max] | client CPU ms/search | runs | engine notes |
|---|---|---|---|---|---|
| 1 | redis | 2526.9 [2518.9, 2536.6] | 0.57 [0.56, 0.57] | 3 | - |
| 2 | mariadb | 1551.8 [1546.4, 1578.0] | 0.48 [0.48, 0.49] | 3 | - |
| 3 | pgvector | 1117.4 [1107.1, 1125.7] | 0.69 [0.67, 0.69] | 3 | - |
| 3 | qdrant | 1113.8 [1111.2, 1118.4] | 0.73 [0.72, 0.74] | 3 | exact-by-design |
| 4 | qdrant-hnsw | 1076.6 [1071.5, 1077.3] | 0.73 [0.73, 0.74] | 3 | - |
| 4 | oracle | 1050.9 [1042.1, 1055.4] | 0.89 [0.88, 0.89] | 3 | cpu-cap |
| 5 | elasticsearch | 739.5 [739.4, 748.1] | 0.46 [0.46, 0.46] | 3 | scans-all-vectors; flags: index-not-ready-after-load, index-not-ready-after-search |
| 5 | mongodb | 693.4 [691.0, 770.4] | 0.31 [0.30, 0.31] | 3 | flags: segment-layout-differs-between-runs, busy-box |
| 6 | sqlitevec | 509.9 [506.4, 514.3] | 2.07 [2.04, 2.07] | 3 | exact-by-design; flags: client-engine-share-cores |
| 6 | vespa | 495.9 [491.5, 496.0] | 0.94 [0.94, 0.96] | 3 | - |
| 6 | opensearch | 483.7 [450.9, 490.8] | 0.47 [0.46, 0.47] | 3 | - |
| 6 | chroma | 468.9 [468.8, 468.9] | 0.48 [0.47, 0.48] | 3 | - |
| 7 | milvus | 407.2 [405.4, 408.5] | 0.57 [0.56, 0.57] | 3 | - |
| 8 | duckdb | 269.6 [269.1, 270.2] | 5.02 [5.02, 5.03] | 3 | flags: client-engine-share-cores |
| 8 | sql-diskann | 267.9 [263.3, 271.5] | 1.02 [1.02, 1.03] | 3 | - |
| 9 | sql | 241.0 [241.0, 242.9] | 1.22 [1.21, 1.22] | 3 | exact-by-design |
| 9 | typesense | 235.2 [234.5, 235.8] | 0.52 [0.52, 0.53] | 3 | - |
| 10 | clickhouse | 193.1 [191.6, 195.8] | 0.88 [0.87, 0.89] | 3 | - |
| 11 | weaviate | 165.6 [165.4, 166.7] | 0.60 [0.57, 0.61] | 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. Where it is close to the latency, the client library is a large part of what is measured. For an embedded engine (DuckDB, sqlite-vec) the engine runs inside the client process, so its figure is the engine's own CPU time, not client overhead.

The engine notes column lists the notes under Per-engine notes and, after "flags:", every flag the engine carries (an unsettled engine, a spread above 15%, a shared core, a segment layout that differs between runs, and the rest). The number is still shown; read it with its flag, whose evidence is under Flags.

## 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 |
| mongodb | flags | segment-layout-differs-between-runs, busy-box (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 | errors | warm-up errors |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| sql | 3 | 4.05 [4.02, 4.06] | 4.58 [4.57, 4.60] | 241.0 [241.0, 242.9] | 611.6 [602.2, 613.6] | 2.54 [2.48, 2.55] | 1.22 [1.21, 1.22] | 1.19 [1.18, 1.20] | 587 [586, 614] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | - | 0 | 0 |
| sql-diskann | 3 | 3.68 [3.60, 3.69] | 4.17 [4.06, 4.20] | 267.9 [263.3, 271.5] | 682.3 [645.4, 690.7] | 2.54 [2.41, 2.59] | 1.02 [1.02, 1.03] | 1.09 [1.08, 1.11] | 611 [561, 617] | 0.965 [0.965, 0.965] | 0.526 [0.526, 0.526] | 3.75 [3.74, 3.79] | 0 | 0 |
| qdrant | 3 | 0.88 [0.88, 0.89] | 1.02 [1.01, 1.02] | 1113.8 [1111.2, 1118.4] | 3280.1 [3273.8, 3287.0] | 2.95 [2.94, 2.95] | 0.73 [0.72, 0.74] | 0.53 [0.52, 0.53] | 5454 [5033, 6919] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | - | 0 | 0 |
| qdrant-hnsw | 3 | 0.92 [0.92, 0.92] | 1.04 [1.03, 1.05] | 1076.6 [1071.5, 1077.3] | 3448.3 [3440.1, 3451.9] | 3.20 [3.20, 3.22] | 0.73 [0.73, 0.74] | 0.51 [0.51, 0.52] | 7067 [4640, 7094] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 0.89 [0.89, 0.89] | 0 | 0 |
| pgvector | 3 | 0.88 [0.87, 0.88] | 1.04 [1.04, 1.05] | 1117.4 [1107.1, 1125.7] | 3933.9 [3909.9, 4001.3] | 3.55 [3.50, 3.55] | 0.69 [0.67, 0.69] | 0.54 [0.53, 0.54] | 609 [605, 611] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 2.25 [2.21, 2.26] | 0 | 0 |
| mariadb | 3 | 0.63 [0.62, 0.64] | 0.72 [0.71, 0.72] | 1551.8 [1546.4, 1578.0] | 5917.8 [5911.5, 5919.7] | 3.81 [3.75, 3.82] | 0.48 [0.48, 0.49] | 0.38 [0.37, 0.38] | 1010 [1001, 1035] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 1.64 [1.63, 1.64] | 0 | 0 |
| oracle | 3 | 0.93 [0.92, 0.93] | 1.12 [1.09, 1.12] | 1050.9 [1042.1, 1055.4] | 2802.2 [2655.3, 2803.4] | 2.66 [2.55, 2.67] | 0.89 [0.88, 0.89] | 0.64 [0.64, 0.65] | 1797 [1729, 1955] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 2.49 [2.48, 2.50] | 0 | 0 |
| redis | 3 | 0.40 [0.39, 0.40] | 0.49 [0.49, 0.49] | 2526.9 [2518.9, 2536.6] | 5067.3 [5037.8, 5120.1] | 2.00 [2.00, 2.03] | 0.57 [0.56, 0.57] | 0.37 [0.36, 0.37] | 12031 [11736, 12405] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 0.38 [0.38, 0.38] | 0 | 0 |
| mongodb | 3 | 1.41 [1.26, 1.41] | 1.66 [1.49, 1.66] | 693.4 [691.0, 770.4] | 2115.3 [2066.0, 2351.9] | 3.05 [2.99, 3.05] | 0.31 [0.30, 0.31] | 0.29 [0.28, 0.29] | 3111 [2896, 3545] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 1.24 [1.24, 1.26] | 0 | 0 |
| clickhouse | 3 | 4.96 [4.94, 4.97] | 7.20 [6.00, 7.40] | 193.1 [191.6, 195.8] | 402.4 [374.8, 428.5] | 2.08 [1.96, 2.19] | 0.88 [0.87, 0.89] | 1.06 [1.06, 1.06] | 2339 [2160, 3196] | 0.990 [0.965, 0.995] | 0.519 [0.515, 0.528] | 6.67 [6.66, 6.68] | 0 | 0 |
| milvus | 3 | 2.32 [2.32, 2.34] | 2.90 [2.89, 2.91] | 407.2 [405.4, 408.5] | 1258.0 [1254.7, 1262.8] | 3.10 [3.08, 3.10] | 0.57 [0.56, 0.57] | 0.64 [0.63, 0.64] | 1171 [1155, 1178] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | - | 0 | 0 |
| weaviate | 3 | 5.36 [5.36, 5.37] | 10.7 [10.5, 10.9] | 165.6 [165.4, 166.7] | 305.4 [304.9, 305.5] | 1.84 [1.83, 1.85] | 0.60 [0.57, 0.61] | 0.62 [0.62, 0.62] | 1001 [949, 1004] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | - | 0 | 0 |
| chroma | 3 | 2.11 [2.11, 2.11] | 2.38 [2.38, 2.39] | 468.9 [468.8, 468.9] | 777.1 [777.1, 777.2] | 1.66 [1.66, 1.66] | 0.48 [0.47, 0.48] | 0.47 [0.47, 0.48] | 820 [668, 863] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | - | 0 | 0 |
| elasticsearch | 3 | 1.33 [1.31, 1.33] | 1.51 [1.51, 1.52] | 739.5 [739.4, 748.1] | 2671.3 [2668.9, 2708.0] | 3.61 [3.61, 3.62] | 0.46 [0.46, 0.46] | 0.49 [0.49, 0.50] | 416 [391, 452] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 1.28 [1.26, 1.28] | 0 | 0 |
| opensearch | 3 | 2.03 [1.99, 2.16] | 2.32 [2.29, 2.50] | 483.7 [450.9, 490.8] | 1476.5 [1346.3, 1516.0] | 3.05 [2.99, 3.09] | 0.47 [0.46, 0.47] | 0.51 [0.50, 0.51] | 322 [306, 369] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 2.69 [2.61, 2.75] | 0 | 0 |
| typesense | 3 | 4.19 [4.18, 4.20] | 4.56 [4.54, 4.60] | 235.2 [234.5, 235.8] | 575.0 [574.0, 576.1] | 2.44 [2.44, 2.45] | 0.52 [0.52, 0.53] | 0.59 [0.59, 0.59] | 991 [980, 998] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 5.67 [5.66, 5.68] | 0 | 0 |
| vespa | 3 | 1.95 [1.95, 1.97] | 2.42 [2.42, 2.42] | 495.9 [491.5, 496.0] | 1526.2 [1505.7, 1564.7] | 3.10 [3.04, 3.16] | 0.94 [0.94, 0.96] | 0.88 [0.88, 0.88] | 276 [238, 313] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 1.94 [1.93, 1.96] | 0 | 0 |
| duckdb | 3 | 3.67 [3.67, 3.68] | 4.07 [4.06, 4.07] | 269.6 [269.1, 270.2] | 576.0 [576.0, 576.1] | 2.14 [2.13, 2.14] | 5.02 [5.02, 5.03] | 6.90 [6.90, 6.91] | 1486 [1443, 1527] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 4.20 [4.19, 4.21] | 0 | 0 |
| sqlitevec | 3 | 1.92 [1.91, 1.93] | 2.18 [2.13, 2.20] | 509.9 [506.4, 514.3] | 1138.4 [1136.4, 1141.9] | 2.24 [2.21, 2.25] | 2.07 [2.04, 2.07] | 3.50 [3.49, 3.51] | 4274 [4077, 4338] | 1.000 [1.000, 1.000] | 0.518 [0.518, 0.518] | 1.91 [1.91, 1.94] | 0 | 0 |

## Per run: p50 ms

| target | 20261006-130619-eshoponweb | 20261006-142724-eshoponweb | 20261006-154837-eshoponweb | median |
|---|---|---|---|---|
| sql | 4.06 | 4.02 | 4.05 | 4.05 |
| sql-diskann | 3.60 | 3.69 | 3.68 | 3.68 |
| qdrant | 0.89 | 0.88 | 0.88 | 0.88 |
| qdrant-hnsw | 0.92 | 0.92 | 0.92 | 0.92 |
| pgvector | 0.88 | 0.87 | 0.88 | 0.88 |
| mariadb | 0.64 | 0.62 | 0.63 | 0.63 |
| oracle | 0.93 | 0.93 | 0.92 | 0.93 |
| redis | 0.40 | 0.39 | 0.40 | 0.40 |
| mongodb | 1.41 | 1.41 | 1.26 | 1.41 |
| clickhouse | 4.97 | 4.94 | 4.96 | 4.96 |
| milvus | 2.34 | 2.32 | 2.32 | 2.32 |
| weaviate | 5.36 | 5.36 | 5.37 | 5.36 |
| chroma | 2.11 | 2.11 | 2.11 | 2.11 |
| elasticsearch | 1.33 | 1.33 | 1.31 | 1.33 |
| opensearch | 2.16 | 1.99 | 2.03 | 2.03 |
| typesense | 4.18 | 4.20 | 4.19 | 4.19 |
| vespa | 1.97 | 1.95 | 1.95 | 1.95 |
| duckdb | 3.67 | 3.68 | 3.67 | 3.67 |
| sqlitevec | 1.92 | 1.91 | 1.93 | 1.92 |

## Per run: QPS@1

| target | 20261006-130619-eshoponweb | 20261006-142724-eshoponweb | 20261006-154837-eshoponweb | median |
|---|---|---|---|---|
| sql | 241.0 | 242.9 | 241.0 | 241.0 |
| sql-diskann | 271.5 | 263.3 | 267.9 | 267.9 |
| qdrant | 1111.2 | 1113.8 | 1118.4 | 1113.8 |
| qdrant-hnsw | 1071.5 | 1076.6 | 1077.3 | 1076.6 |
| pgvector | 1107.1 | 1125.7 | 1117.4 | 1117.4 |
| mariadb | 1546.4 | 1578.0 | 1551.8 | 1551.8 |
| oracle | 1050.9 | 1042.1 | 1055.4 | 1050.9 |
| redis | 2526.9 | 2536.6 | 2518.9 | 2526.9 |
| mongodb | 691.0 | 693.4 | 770.4 | 693.4 |
| clickhouse | 191.6 | 195.8 | 193.1 | 193.1 |
| milvus | 405.4 | 408.5 | 407.2 | 407.2 |
| weaviate | 165.6 | 166.7 | 165.4 | 165.6 |
| chroma | 468.9 | 468.9 | 468.8 | 468.9 |
| elasticsearch | 739.5 | 739.4 | 748.1 | 739.5 |
| opensearch | 450.9 | 490.8 | 483.7 | 483.7 |
| typesense | 235.2 | 234.5 | 235.8 | 235.2 |
| vespa | 491.5 | 496.0 | 495.9 | 495.9 |
| duckdb | 269.6 | 269.1 | 270.2 | 269.6 |
| sqlitevec | 509.9 | 514.3 | 506.4 | 509.9 |

## Per run: QPS@8

| target | 20261006-130619-eshoponweb | 20261006-142724-eshoponweb | 20261006-154837-eshoponweb | median |
|---|---|---|---|---|
| sql | 611.6 | 602.2 | 613.6 | 611.6 |
| sql-diskann | 690.7 | 682.3 | 645.4 | 682.3 |
| qdrant | 3273.8 | 3280.1 | 3287.0 | 3280.1 |
| qdrant-hnsw | 3451.9 | 3440.1 | 3448.3 | 3448.3 |
| pgvector | 3933.9 | 4001.3 | 3909.9 | 3933.9 |
| mariadb | 5911.5 | 5919.7 | 5917.8 | 5917.8 |
| oracle | 2802.2 | 2655.3 | 2803.4 | 2802.2 |
| redis | 5120.1 | 5067.3 | 5037.8 | 5067.3 |
| mongodb | 2066.0 | 2115.3 | 2351.9 | 2115.3 |
| clickhouse | 374.8 | 428.5 | 402.4 | 402.4 |
| milvus | 1254.7 | 1258.0 | 1262.8 | 1258.0 |
| weaviate | 304.9 | 305.5 | 305.4 | 305.4 |
| chroma | 777.1 | 777.2 | 777.1 | 777.1 |
| elasticsearch | 2671.3 | 2668.9 | 2708.0 | 2671.3 |
| opensearch | 1346.3 | 1516.0 | 1476.5 | 1476.5 |
| typesense | 575.0 | 574.0 | 576.1 | 575.0 |
| vespa | 1526.2 | 1505.7 | 1564.7 | 1526.2 |
| duckdb | 576.1 | 576.0 | 576.0 | 576.0 |
| sqlitevec | 1141.9 | 1136.4 | 1138.4 | 1138.4 |

## Per run: QPS ratio 8/1

| target | 20261006-130619-eshoponweb | 20261006-142724-eshoponweb | 20261006-154837-eshoponweb | median |
|---|---|---|---|---|
| sql | 2.54 | 2.48 | 2.55 | 2.54 |
| sql-diskann | 2.54 | 2.59 | 2.41 | 2.54 |
| qdrant | 2.95 | 2.95 | 2.94 | 2.95 |
| qdrant-hnsw | 3.22 | 3.20 | 3.20 | 3.20 |
| pgvector | 3.55 | 3.55 | 3.50 | 3.55 |
| mariadb | 3.82 | 3.75 | 3.81 | 3.81 |
| oracle | 2.67 | 2.55 | 2.66 | 2.66 |
| redis | 2.03 | 2.00 | 2.00 | 2.00 |
| mongodb | 2.99 | 3.05 | 3.05 | 3.05 |
| clickhouse | 1.96 | 2.19 | 2.08 | 2.08 |
| milvus | 3.10 | 3.08 | 3.10 | 3.10 |
| weaviate | 1.84 | 1.83 | 1.85 | 1.84 |
| chroma | 1.66 | 1.66 | 1.66 | 1.66 |
| elasticsearch | 3.61 | 3.61 | 3.62 | 3.61 |
| opensearch | 2.99 | 3.09 | 3.05 | 3.05 |
| typesense | 2.44 | 2.45 | 2.44 | 2.44 |
| vespa | 3.10 | 3.04 | 3.16 | 3.10 |
| duckdb | 2.14 | 2.14 | 2.13 | 2.14 |
| sqlitevec | 2.24 | 2.21 | 2.25 | 2.24 |

## Per run: client CPU ms per search@1

| target | 20261006-130619-eshoponweb | 20261006-142724-eshoponweb | 20261006-154837-eshoponweb | median |
|---|---|---|---|---|
| sql | 1.219 | 1.220 | 1.208 | 1.219 |
| sql-diskann | 1.023 | 1.031 | 1.024 | 1.024 |
| qdrant | 0.737 | 0.729 | 0.723 | 0.729 |
| qdrant-hnsw | 0.727 | 0.737 | 0.730 | 0.730 |
| pgvector | 0.688 | 0.687 | 0.669 | 0.687 |
| mariadb | 0.486 | 0.482 | 0.482 | 0.482 |
| oracle | 0.880 | 0.888 | 0.886 | 0.886 |
| redis | 0.569 | 0.561 | 0.569 | 0.569 |
| mongodb | 0.312 | 0.311 | 0.303 | 0.311 |
| clickhouse | 0.873 | 0.878 | 0.886 | 0.878 |
| milvus | 0.569 | 0.564 | 0.569 | 0.569 |
| weaviate | 0.572 | 0.608 | 0.595 | 0.595 |
| chroma | 0.480 | 0.466 | 0.476 | 0.476 |
| elasticsearch | 0.463 | 0.456 | 0.458 | 0.458 |
| opensearch | 0.473 | 0.458 | 0.465 | 0.465 |
| typesense | 0.519 | 0.528 | 0.521 | 0.521 |
| vespa | 0.958 | 0.938 | 0.937 | 0.938 |
| duckdb | 5.023 | 5.026 | 5.017 | 5.023 |
| sqlitevec | 2.067 | 2.038 | 2.067 | 2.067 |

## Per run: client CPU ms per search@8

| target | 20261006-130619-eshoponweb | 20261006-142724-eshoponweb | 20261006-154837-eshoponweb | median |
|---|---|---|---|---|
| sql | 1.184 | 1.204 | 1.192 | 1.192 |
| sql-diskann | 1.095 | 1.108 | 1.082 | 1.095 |
| qdrant | 0.527 | 0.531 | 0.524 | 0.527 |
| qdrant-hnsw | 0.510 | 0.517 | 0.512 | 0.512 |
| pgvector | 0.538 | 0.538 | 0.533 | 0.538 |
| mariadb | 0.376 | 0.376 | 0.374 | 0.376 |
| oracle | 0.643 | 0.654 | 0.643 | 0.643 |
| redis | 0.364 | 0.366 | 0.369 | 0.366 |
| mongodb | 0.288 | 0.284 | 0.291 | 0.288 |
| clickhouse | 1.057 | 1.055 | 1.062 | 1.057 |
| milvus | 0.638 | 0.636 | 0.629 | 0.636 |
| weaviate | 0.617 | 0.621 | 0.623 | 0.621 |
| chroma | 0.480 | 0.469 | 0.472 | 0.472 |
| elasticsearch | 0.497 | 0.488 | 0.491 | 0.491 |
| opensearch | 0.515 | 0.499 | 0.510 | 0.510 |
| typesense | 0.592 | 0.591 | 0.592 | 0.592 |
| vespa | 0.880 | 0.876 | 0.875 | 0.876 |
| duckdb | 6.910 | 6.899 | 6.902 | 6.902 |
| sqlitevec | 3.493 | 3.512 | 3.502 | 3.502 |

## Rank per run: p50 (1 = lowest)

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

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

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

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

| target | 20261006-130619-eshoponweb | 20261006-142724-eshoponweb | 20261006-154837-eshoponweb | band |
|---|---|---|---|---|
| sql | 16 | 16 | 16 | 9 |
| sql-diskann | 14 | 15 | 15 | 8 |
| qdrant | 3 | 4 | 3 | 3 |
| qdrant-hnsw | 5 | 5 | 5 | 4 |
| pgvector | 4 | 3 | 4 | 3 |
| mariadb | 2 | 2 | 2 | 2 |
| oracle | 6 | 6 | 6 | 4 |
| redis | 1 | 1 | 1 | 1 |
| mongodb | 8 | 8 | 7 | 5 |
| clickhouse | 18 | 18 | 18 | 10 |
| milvus | 13 | 13 | 13 | 7 |
| weaviate | 19 | 19 | 19 | 11 |
| chroma | 11 | 12 | 12 | 6 |
| elasticsearch | 7 | 7 | 8 | 5 |
| opensearch | 12 | 11 | 11 | 6 |
| typesense | 17 | 17 | 17 | 9 |
| vespa | 10 | 10 | 10 | 6 |
| duckdb | 15 | 14 | 14 | 8 |
| 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 | 20261006-130619-eshoponweb | 3.60 | 3.74 | 0.14 | 1.040 | 1.000 | no |
| sql-diskann | 20261006-142724-eshoponweb | 3.69 | 3.75 | 0.06 | 1.015 | 1.000 | yes |
| sql-diskann | 20261006-154837-eshoponweb | 3.68 | 3.79 | 0.11 | 1.029 | 1.000 | no |
| qdrant-hnsw | 20261006-130619-eshoponweb | 0.92 | 0.89 | -0.03 | 0.972 | 1.000 | no |
| qdrant-hnsw | 20261006-142724-eshoponweb | 0.92 | 0.89 | -0.02 | 0.974 | 1.000 | yes |
| qdrant-hnsw | 20261006-154837-eshoponweb | 0.92 | 0.89 | -0.03 | 0.973 | 1.000 | yes |
| pgvector | 20261006-130619-eshoponweb | 0.88 | 2.26 | 1.37 | 2.552 | 1.000 | yes |
| pgvector | 20261006-142724-eshoponweb | 0.87 | 2.21 | 1.34 | 2.541 | 1.000 | yes |
| pgvector | 20261006-154837-eshoponweb | 0.88 | 2.25 | 1.37 | 2.568 | 1.000 | yes |
| mariadb | 20261006-130619-eshoponweb | 0.64 | 1.64 | 1.00 | 2.576 | 1.000 | no |
| mariadb | 20261006-142724-eshoponweb | 0.62 | 1.63 | 1.01 | 2.623 | 1.000 | no |
| mariadb | 20261006-154837-eshoponweb | 0.63 | 1.64 | 1.01 | 2.596 | 1.000 | no |
| oracle | 20261006-130619-eshoponweb | 0.93 | 2.48 | 1.56 | 2.680 | 1.000 | yes |
| oracle | 20261006-142724-eshoponweb | 0.93 | 2.49 | 1.56 | 2.665 | 1.000 | no |
| oracle | 20261006-154837-eshoponweb | 0.92 | 2.50 | 1.58 | 2.710 | 1.000 | no |
| redis | 20261006-130619-eshoponweb | 0.40 | 0.38 | -0.02 | 0.950 | 1.000 | no |
| redis | 20261006-142724-eshoponweb | 0.39 | 0.38 | -0.01 | 0.971 | 1.000 | no |
| redis | 20261006-154837-eshoponweb | 0.40 | 0.38 | -0.02 | 0.945 | 1.000 | yes |
| mongodb | 20261006-130619-eshoponweb | 1.41 | 1.24 | -0.17 | 0.879 | 1.000 | no |
| mongodb | 20261006-142724-eshoponweb | 1.41 | 1.26 | -0.14 | 0.897 | 1.000 | no |
| mongodb | 20261006-154837-eshoponweb | 1.26 | 1.24 | -0.02 | 0.984 | 1.000 | no |
| clickhouse | 20261006-130619-eshoponweb | 4.97 | 6.67 | 1.70 | 1.342 | 1.000 | no |
| clickhouse | 20261006-142724-eshoponweb | 4.94 | 6.66 | 1.72 | 1.347 | 1.000 | no |
| clickhouse | 20261006-154837-eshoponweb | 4.96 | 6.68 | 1.72 | 1.347 | 1.000 | yes |
| elasticsearch | 20261006-130619-eshoponweb | 1.33 | 1.28 | -0.05 | 0.962 | 1.000 | yes |
| elasticsearch | 20261006-142724-eshoponweb | 1.33 | 1.28 | -0.05 | 0.966 | 1.000 | yes |
| elasticsearch | 20261006-154837-eshoponweb | 1.31 | 1.26 | -0.05 | 0.962 | 1.000 | yes |
| opensearch | 20261006-130619-eshoponweb | 2.16 | 2.75 | 0.59 | 1.275 | 1.000 | yes |
| opensearch | 20261006-142724-eshoponweb | 1.99 | 2.69 | 0.69 | 1.347 | 1.000 | yes |
| opensearch | 20261006-154837-eshoponweb | 2.03 | 2.61 | 0.59 | 1.290 | 1.000 | yes |
| typesense | 20261006-130619-eshoponweb | 4.18 | 5.66 | 1.48 | 1.353 | 1.000 | no |
| typesense | 20261006-142724-eshoponweb | 4.20 | 5.68 | 1.48 | 1.352 | 1.000 | yes |
| typesense | 20261006-154837-eshoponweb | 4.19 | 5.67 | 1.48 | 1.354 | 1.000 | yes |
| vespa | 20261006-130619-eshoponweb | 1.97 | 1.96 | -0.01 | 0.996 | 1.000 | yes |
| vespa | 20261006-142724-eshoponweb | 1.95 | 1.94 | -0.01 | 0.997 | 1.000 | no |
| vespa | 20261006-154837-eshoponweb | 1.95 | 1.93 | -0.01 | 0.993 | 1.000 | no |
| duckdb | 20261006-130619-eshoponweb | 3.67 | 4.21 | 0.55 | 1.149 | 1.000 | yes |
| duckdb | 20261006-142724-eshoponweb | 3.68 | 4.20 | 0.52 | 1.142 | 1.000 | yes |
| duckdb | 20261006-154837-eshoponweb | 3.67 | 4.19 | 0.53 | 1.144 | 1.000 | yes |
| sqlitevec | 20261006-130619-eshoponweb | 1.92 | 1.91 | -0.02 | 0.990 | 1.000 | no |
| sqlitevec | 20261006-142724-eshoponweb | 1.91 | 1.91 | 0.00 | 1.002 | 1.000 | no |
| sqlitevec | 20261006-154837-eshoponweb | 1.93 | 1.94 | 0.00 | 1.002 | 1.000 | no |

## Exact / default summary

| target | n | median exact/default | min | max | median exact - default ms | runs exact slower |
|---|---|---|---|---|---|---|
| sql-diskann | 3 | 1.029 | 1.015 | 1.040 | 0.11 | 3 of 3 |
| qdrant-hnsw | 3 | 0.973 | 0.972 | 0.974 | -0.03 | 0 of 3 |
| pgvector | 3 | 2.552 | 2.541 | 2.568 | 1.37 | 3 of 3 |
| mariadb | 3 | 2.596 | 2.576 | 2.623 | 1.01 | 3 of 3 |
| oracle | 3 | 2.680 | 2.665 | 2.710 | 1.56 | 3 of 3 |
| redis | 3 | 0.950 | 0.945 | 0.971 | -0.02 | 0 of 3 |
| mongodb | 3 | 0.897 | 0.879 | 0.984 | -0.14 | 0 of 3 |
| clickhouse | 3 | 1.347 | 1.342 | 1.347 | 1.72 | 3 of 3 |
| elasticsearch | 3 | 0.962 | 0.962 | 0.966 | -0.05 | 0 of 3 |
| opensearch | 3 | 1.290 | 1.275 | 1.347 | 0.59 | 3 of 3 |
| typesense | 3 | 1.353 | 1.352 | 1.354 | 1.48 | 3 of 3 |
| vespa | 3 | 0.996 | 0.993 | 0.997 | -0.01 | 0 of 3 |
| duckdb | 3 | 1.144 | 1.142 | 1.149 | 0.53 | 3 of 3 |
| sqlitevec | 3 | 1.002 | 0.990 | 1.002 | 0.00 | 2 of 3 |

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

| target | run | order | passOrder | warm-up errors | errors | afterLoad ready | afterLoad indexed/total | afterLoad detail | afterSearch ready | afterSearch indexed/total | segments after load / after search | durability | load indexNote | settled | mean ms |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| sql | 20261006-130619-eshoponweb | 5 | default@8, default@1 | 0 | 0 | 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.15 (1000 / QPS@1) |
| sql | 20261006-142724-eshoponweb | 11 | default@1, default@8 | 0 | 0 | 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.12 (1000 / QPS@1) |
| sql | 20261006-154837-eshoponweb | 13 | default@1, default@8 | 0 | 0 | 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.15 (1000 / QPS@1) |
| sql-diskann | 20261006-130619-eshoponweb | 18 | default@1, default@8, exact | 0 | 0 | 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.68 (1000 / QPS@1) |
| sql-diskann | 20261006-142724-eshoponweb | 15 | exact, default@8, default@1 | 0 | 0 | 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.80 (1000 / QPS@1) |
| sql-diskann | 20261006-154837-eshoponweb | 8 | default@8, default@1, exact | 0 | 0 | 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.73 (1000 / QPS@1) |
| qdrant | 20261006-130619-eshoponweb | 8 | default@1, default@8 | 0 | 0 | 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.90 (1000 / QPS@1) |
| qdrant | 20261006-142724-eshoponweb | 5 | default@8, default@1 | 0 | 0 | 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.90 (1000 / QPS@1) |
| qdrant | 20261006-154837-eshoponweb | 4 | default@8, default@1 | 0 | 0 | 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 | 20261006-130619-eshoponweb | 10 | default@1, default@8, exact | 0 | 0 | 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 | 20261006-142724-eshoponweb | 3 | exact, default@1, default@8 | 0 | 0 | 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 | 20261006-154837-eshoponweb | 7 | exact, default@1, default@8 | 0 | 0 | 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 | 20261006-130619-eshoponweb | 6 | exact, default@8, default@1 | 0 | 0 | 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.90 (1000 / QPS@1) |
| pgvector | 20261006-142724-eshoponweb | 13 | default@8, exact, default@1 | 0 | 0 | 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.89 (1000 / QPS@1) |
| pgvector | 20261006-154837-eshoponweb | 9 | exact, default@8, default@1 | 0 | 0 | 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.89 (1000 / QPS@1) |
| mariadb | 20261006-130619-eshoponweb | 13 | default@8, default@1, exact | 0 | 0 | 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 521 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 393 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 393 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 521 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.65 (1000 / QPS@1) |
| mariadb | 20261006-142724-eshoponweb | 6 | default@1, exact, default@8 | 0 | 0 | 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 519 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 391 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 391 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 519 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 | 20261006-154837-eshoponweb | 2 | default@1, default@8, exact | 0 | 0 | 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 520 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 402 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 402 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 520 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 | 20261006-130619-eshoponweb | 3 | default@8, exact, default@1 | 0 | 0 | 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.5 s | yes | 0.95 (1000 / QPS@1) |
| oracle | 20261006-142724-eshoponweb | 8 | default@1, exact, default@8 | 0 | 0 | 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 | yes | 0.96 (1000 / QPS@1) |
| oracle | 20261006-154837-eshoponweb | 12 | default@8, default@1, exact | 0 | 0 | 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 | yes | 0.95 (1000 / QPS@1) |
| redis | 20261006-130619-eshoponweb | 11 | default@8, default@1, exact | 0 | 0 | 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 | yes | 0.40 (1000 / QPS@1) |
| redis | 20261006-142724-eshoponweb | 2 | default@8, default@1, exact | 0 | 0 | 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 | yes | 0.39 (1000 / QPS@1) |
| redis | 20261006-154837-eshoponweb | 15 | default@8, exact, default@1 | 0 | 0 | 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 | yes | 0.40 (1000 / QPS@1) |
| mongodb | 20261006-130619-eshoponweb | 15 | default@1, exact, default@8 | 0 | 0 | true | 524/524 | index status READY, queryable True; mongot holds 524 of 524 documents in 4 segment(s) (269 + 251 + 2 + 2 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) (269 + 251 + 2 + 2 documents), 4 searched through the HNSW graph (Approximate); segment layout unchanged for 10.2 s over 11 readings; wait took 10.3 s | yes | 1.45 (1000 / QPS@1) |
| mongodb | 20261006-142724-eshoponweb | 18 | default@1, exact, default@8 | 0 | 0 | true | 524/524 | index status READY, queryable True; mongot holds 524 of 524 documents in 2 segment(s) (278 + 246 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) (278 + 246 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.44 (1000 / QPS@1) |
| mongodb | 20261006-154837-eshoponweb | 18 | default@1, default@8, exact | 0 | 0 | true | 524/524 | index status READY, queryable True; mongot holds 524 of 524 documents in 4 segment(s) (196 + 175 + 139 + 14 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) (196 + 175 + 139 + 14 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.30 (1000 / QPS@1) |
| clickhouse | 20261006-130619-eshoponweb | 1 | default@1, default@8, exact | 0 | 0 | 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 | yes | 5.22 (1000 / QPS@1) |
| clickhouse | 20261006-142724-eshoponweb | 10 | default@8, default@1, exact | 0 | 0 | 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 | yes | 5.11 (1000 / QPS@1) |
| clickhouse | 20261006-154837-eshoponweb | 11 | default@8, exact, default@1 | 0 | 0 | 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 | yes | 5.18 (1000 / QPS@1) |
| milvus | 20261006-130619-eshoponweb | 12 | default@8, default@1 | 0 | 0 | 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, 123.9 s for the whole step; search ledger started, later state reads count the searches against the query node's own counters | yes | 2.47 (1000 / QPS@1) |
| milvus | 20261006-142724-eshoponweb | 9 | default@1, default@8 | 0 | 0 | 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.6 s, then compaction: 1 job(s) accepted by Milvus, layout ready and unchanged for 75 s, 123.9 s for the whole step; search ledger started, later state reads count the searches against the query node's own counters | yes | 2.45 (1000 / QPS@1) |
| milvus | 20261006-154837-eshoponweb | 19 | default@1, default@8 | 0 | 0 | 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.6 s, then compaction: 1 job(s) accepted by Milvus, layout ready and unchanged for 75 s, 123.9 s for the whole step; search ledger started, later state reads count the searches against the query node's own counters | yes | 2.46 (1000 / QPS@1) |
| weaviate | 20261006-130619-eshoponweb | 14 | default@1, default@8 | 0 | 0 | true | ?/524 | shard 9u0EFW2dYzBR 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 9u0EFW2dYzBR 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 9u0EFW2dYzBR 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 9u0EFW2dYzBR 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 | 6.04 (1000 / QPS@1) |
| weaviate | 20261006-142724-eshoponweb | 4 | default@8, default@1 | 0 | 0 | true | ?/524 | shard iKiSj18BxrvU 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 iKiSj18BxrvU 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 iKiSj18BxrvU 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 iKiSj18BxrvU 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 | 6.00 (1000 / QPS@1) |
| weaviate | 20261006-154837-eshoponweb | 10 | default@1, default@8 | 0 | 0 | true | ?/524 | shard gtd945wzSIS6 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 gtd945wzSIS6 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 gtd945wzSIS6 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 gtd945wzSIS6 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 | 6.04 (1000 / QPS@1) |
| chroma | 20261006-130619-eshoponweb | 16 | default@8, default@1 | 0 | 0 | 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.13 (1000 / QPS@1) |
| chroma | 20261006-142724-eshoponweb | 16 | default@1, default@8 | 0 | 0 | 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.13 (1000 / QPS@1) |
| chroma | 20261006-154837-eshoponweb | 16 | default@8, default@1 | 0 | 0 | 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.13 (1000 / QPS@1) |
| elasticsearch | 20261006-130619-eshoponweb | 4 | exact, default@8, default@1 | 0 | 0 | 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.35 (1000 / QPS@1) |
| elasticsearch | 20261006-142724-eshoponweb | 14 | exact, default@1, default@8 | 0 | 0 | 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.35 (1000 / QPS@1) |
| elasticsearch | 20261006-154837-eshoponweb | 5 | default@8, exact, default@1 | 0 | 0 | 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.34 (1000 / QPS@1) |
| opensearch | 20261006-130619-eshoponweb | 9 | exact, default@8, default@1 | 0 | 0 | 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.22 (1000 / QPS@1) |
| opensearch | 20261006-142724-eshoponweb | 1 | default@8, exact, default@1 | 0 | 0 | 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.04 (1000 / QPS@1) |
| opensearch | 20261006-154837-eshoponweb | 14 | default@8, exact, default@1 | 0 | 0 | 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.07 (1000 / QPS@1) |
| typesense | 20261006-130619-eshoponweb | 17 | default@8, default@1, exact | 0 | 0 | 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.25 (1000 / QPS@1) |
| typesense | 20261006-142724-eshoponweb | 17 | default@8, exact, default@1 | 0 | 0 | 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.26 (1000 / QPS@1) |
| typesense | 20261006-154837-eshoponweb | 17 | exact, default@1, default@8 | 0 | 0 | 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.24 (1000 / QPS@1) |
| vespa | 20261006-130619-eshoponweb | 2 | exact, default@1, default@8 | 0 | 0 | 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 | 2.03 (1000 / QPS@1) |
| vespa | 20261006-142724-eshoponweb | 7 | default@8, default@1, exact | 0 | 0 | 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 | 2.02 (1000 / QPS@1) |
| vespa | 20261006-154837-eshoponweb | 6 | default@1, default@8, exact | 0 | 0 | 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 | 2.02 (1000 / QPS@1) |
| duckdb | 20261006-130619-eshoponweb | 19 | default@8, exact, default@1 | 0 | 0 | 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.71 (1000 / QPS@1) |
| duckdb | 20261006-142724-eshoponweb | 12 | exact, default@8, default@1 | 0 | 0 | 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.72 (1000 / QPS@1) |
| duckdb | 20261006-154837-eshoponweb | 3 | default@8, exact, default@1 | 0 | 0 | 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.70 (1000 / QPS@1) |
| sqlitevec | 20261006-130619-eshoponweb | 7 | default@1, default@8, exact | 0 | 0 | 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.96 (1000 / QPS@1) |
| sqlitevec | 20261006-142724-eshoponweb | 19 | default@1, exact, default@8 | 0 | 0 | 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.94 (1000 / QPS@1) |
| sqlitevec | 20261006-154837-eshoponweb | 1 | default@1, default@8, exact | 0 | 0 | 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.97 (1000 / QPS@1) |

## Flags

| target | flag | runs | detail |
|---|---|---|---|
| mongodb | segment-layout-differs-between-runs | 3 of 3 | after the load: 4 segments (20261006-130619-eshoponweb, 20261006-154837-eshoponweb); 2 segments (20261006-142724-eshoponweb); after the searches: 4 segments (20261006-130619-eshoponweb, 20261006-154837-eshoponweb); 2 segments (20261006-142724-eshoponweb). Searches ran over different layouts, so the medians mix them. |
| mongodb | busy-box | 3 of 3 | busy during exact: processes outside the benchmark used 0.31 CPUs on average during the pass, above the limit of 0.3 (1 run); busy during exact: processes outside the benchmark used 0.32 CPUs on average during the pass, above the limit of 0.3 (1 run); busy during default@1: processes outside the benchmark used 0.35 CPUs on average during the pass, above the limit of 0.3; busy during exact: processes outside the benchmark used 0.30 CPUs on average during the pass, above the limit of 0.3 (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 method (the warm-up time and count, the settle trial, the extension and the rehearsal as the runs recorded them), exact-mode seconds, seconds per level and every listed target's index description and 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 target whose engine description, recorded engine settings, configuration files (compose file and read-only mounted config, by SHA-256) or durability statement differs between the runs is refused for that target alone, like a different hosting: it has no row and is named under "Targets not in this report" with the differing values. A setting no run recorded cannot be compared and shows as missing.
- 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 or engine setup) is named under "Targets not in this report" with its reason (0 in this report), so no measured engine is left out unsaid.