Benchmarks / turbopuffer workloads
turbopuffer's own benchmark, run on WarpSearch.
turbopuffer publishes latency for a fixed set of workloads and open-sources the harness that produces it. We pointed that same harness at WarpSearch's turbopuffer-compatible API, with the same data, query rate and duration: 10M Cohere Wikipedia embeddings, 1024 dimensions, cosine, top 10, 8 queries a second for 30 minutes on a warm cache.
Vector, 10M, warm
Faster at every percentile
Shorter is better. All bars share one scale.
turbopuffer: homepage figures for this workload, client in the same region, as of 2026-11-04. WarpSearch: Serverless, server time reported by the service, 13,851 queries after the first 500, 0 errors, run 2026-11-14.
Scaling
Same harness, three sizes
The website configuration at 100K, 1M and 10M documents, at 8 queries a second with a warm cache. Median latency stays under 10 ms as the namespace grows 100x.
| Documents | Queries | p50 | p90 | p99 | Errors |
|---|---|---|---|---|---|
| 100K x 1024 | 4,799 | 5 ms | 6 ms | 6 ms | 0 |
| 1M x 1024 | 14,399 | 5 ms | 6 ms | 6 ms | 0 |
| 10M x 1024 | 13,851 | 9 ms | 10 ms | 10 ms | 0 |
Server time, WarpSearch Serverless, runs 2026-11-14. turbopuffer publishes its homepage figures for 10M only.
VectorDBBench
And at the same recall
turbopuffer also appears in VectorDBBench, which reports recall next to latency. On Cohere 1M x 768, WarpSearch returns slightly better neighbours in a fraction of the time.
recall@10: WarpSearch 0.902, turbopuffer 0.899. See the vector search results.
turbopuffer: VectorDBBench result file, case Performance768D1M, serial p99, 2026-03. WarpSearch: Serverless, server p99, run 2026-11-13.
Full-text, warm
Keyword search, too
BM25 over MS MARCO passages, top 10, warm cache.
turbopuffer: /docs/performance, full-text on 1M MS MARCO documents, warm, as of 2026-11-04. WarpSearch: 1M MS MARCO passages, single client, warm.
Full-text, query by query
turbopuffer's own full-text queries
The 5M-article English Wikipedia corpus and the queries turbopuffer published for its FTS v2 engine, top 10. Median latency.
| Query | WarpSearch | turbopuffer FTS v2 | At p50 |
|---|---|---|---|
| the incredibles | 1 ms | 3.3 ms | 3.3x faster |
| to be or not to be | 8 ms | 18.4 ms | 2.3x faster |
| lord of the rings | 2 ms | 4.2 ms | 2.1x faster |
| new york | 2 ms | 4.0 ms | 2x faster |
| united states constitution | 2 ms | 3.8 ms | 1.9x faster |
turbopuffer: appendix of its blog post on FTS v2 (/blog/fts-v2-maxscore). WarpSearch: Serverless, through the turbopuffer-compatible API, server time, median of 150 runs per query, 2026-11-04.
Already on turbopuffer? Keep your SDK. Point its base URL at https://api.warpsearch.io/compat/turbopuffer and use a WarpSearch API key. The compatibility guide lists the supported operations, and the price comparison shows what the same workload costs.
Reproduce
turbopuffer's open-source harness (MIT), pointed at the compatible endpoint, using the website configuration unchanged. Our patch sends vectors as base64 and skips turbopuffer-specific index checks; it is published with the run.
# base URL: https://api.warpsearch.io/compat/turbopuffer tpufbench run --warm-cache --namespace-setup-concurrency 8 \ benchmarks/website/vector-10m-hot.toml
Run reports: 20261114T035946Z (10M), 20261114T025847Z (1M), 20261114T024015Z (100K).