← all runs

Cohere-10M — 2026-06-16

r8i.8xlarge · peak recall 0.9994 @ 3 QPS

QPS at recall

RecallMeerkatvchordrqvchordrq-rabitq8vchordrq-rabitq4Δ vs best competitor
0.9047822510442+112%
0.95258995723+162%
0.99772198+262%

Latency at recall

Meerkatvchordrqvchordrq-rabitq8vchordrq-rabitq4Δ vs best competitor
@ recall 0.90
p502.05 ms4.35 ms8.22 ms23.33 ms-53%
p952.67 ms5.56 ms20.13 ms37.11 ms-52%
p992.97 ms6.20 ms27.50 ms44.79 ms-52%
@ recall 0.95
p503.80 ms9.94 ms14.27 ms42.49 ms-62%
p954.81 ms12.51 ms37.59 ms70.40 ms-62%
p995.39 ms13.85 ms51.61 ms84.79 ms-61%
@ recall 0.99
p5012.88 ms46.70 ms104.06 ms124.37 ms-72%
p9515.34 ms55.51 ms193.88 ms232.95 ms-72%
p9916.49 ms59.42 ms266.56 ms277.87 ms-72%

All values are taken at exactly the stated recall: each configuration's own sweep is log-interpolated between its two surrounding measured points (measured values are used verbatim on an exact hit) and the best configuration at that recall is shown — values are never interpolated across different configurations. “—” means no single sweep spans that recall; nothing is extrapolated. Recall is distance-based (ann-benchmarks, tie-aware). Insert/update/delete workloads are not measured.

Interpolated on config — Meerkat @0.90: mkt-n24000-cctrue-fs16-soar · vchordrq @0.90: vchordrq-n16000 · vchordrq-rabitq8 @0.90: vchordrq-rabitq8-n16000 · vchordrq-rabitq4 @0.90: vchordrq-rabitq4-rerank-n16000 · Meerkat @0.95: mkt-n24000-cctrue-fs16-soar · vchordrq @0.95: vchordrq-n16000 · vchordrq-rabitq8 @0.95: vchordrq-rabitq8-n16000 · vchordrq-rabitq4 @0.95: vchordrq-rabitq4-rerank-n16000 · Meerkat @0.99: mkt-n24000-cctrue-fs16-soar · vchordrq @0.99: vchordrq-n16000 · vchordrq-rabitq8 @0.99: vchordrq-rabitq8-n16000 · vchordrq-rabitq4 @0.99: vchordrq-rabitq4-rerank-n16000

Build comparison

Meerkatvchordrqvchordrq-rabitq8vchordrq-rabitq4Δ vs best competitor
Build time632 s1216 s1544 s1744 s-48%
Index size2.3 GB40.0 GB9.5 GB5.8 GB-60%

Build stats are for the configuration backing each column's best operating point: Meerkat = mkt-n24000-cctrue-fs16-soar · vchordrq = vchordrq-n16000 · vchordrq-rabitq8 = vchordrq-rabitq8-n16000 · vchordrq-rabitq4 = vchordrq-rabitq4-rerank-n16000.

Plots

Pareto svg  ·  Distance-recall svg  ·  Per-config svg  ·  Build times svg  ·  Index sizes svg
paretodistance-recallbuild-timesbuild-sizes

Host

Instance typer8i.8xlarge
Hostnameip-172-31-44-251
CPUIntel(R) Xeon(R) 6975P-C (32 vCPU)
Memory248 GB
OSUbuntu 26.04 LTS
Kernel7.0.0-1006-aws

Versions

rekall0.1.0 (e083fdb / main)
PostgreSQLPostgreSQL 18.4 (Ubuntu 18.4-1.pgdg26.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0, 64-bit
meerkat0.1.0 (cd8e895)
pageinspect1.13
pg_prewarm1.2
vchord1.1.1
vector0.8.2

Search

k10
runs3
warmup500
num_queries10000
S3 archives3://rekall-bench/runs/cohere-10m/2026-06-16/r8i.8xlarge-101846/

Index builds

IndexTypeBuild timeSizeWorkers
mkt-n24000-cctrue-fs16-soarmeerkat632.3s2.3 GB16
vchordrq-n16000vchordrq1216.0s40.0 GB16
vchordrq-rabitq4-rerank-n16000vchordrq-rabitq41743.9s5.8 GB16
vchordrq-rabitq8-n16000vchordrq-rabitq81543.9s9.5 GB16
Index parameters
mkt-n24000-cctrue-fs16-soar: {"boundary_epsilon":0.05,"centroid_compression":true,"centroid_fastscan":true,"fan_out":null,"fastscan":true,"fastscan_bits":null,"nlist":24000,"rerank_vectors":null,"soar_lambda":1.0}
vchordrq-n16000: {"build_threads":16,"lists":[16000],"rerank_n":200,"residual_quantization":true,"spherical_centroids":true}
vchordrq-rabitq4-rerank-n16000: {"build_threads":16,"lists":[16000],"rerank_n":200,"residual_quantization":false,"spherical_centroids":true}
vchordrq-rabitq8-n16000: {"build_threads":16,"lists":[16000],"rerank_n":200,"residual_quantization":false,"spherical_centroids":true}
PostgreSQL settings
effective_cache_size = 192 GB
effective_io_concurrency = 256
huge_pages = try
maintenance_work_mem = 102 GB
max_connections = 100
max_parallel_maintenance_workers = 16
max_parallel_workers = 32
random_page_cost = 1.1
shared_buffers = 64 GB
wal_level = replica
work_mem = 1 GB