Benchmarks

Measured on the industry's own benchmarks.

Up to 80x faster than Elasticsearch, 31x faster p99 than Amazon S3 Vectors and 2.7x faster p99 than turbopuffer. Each result comes from the benchmark that vendor publishes against: Elastic's Rally tracks, VectorDBBench and turbopuffer's open harness.

Last updated 2026-11-17 · WarpSearch v0.4.1

Headline results

Where we stand

Each number is WarpSearch against the competitor's own published figure for the same workload.

Benchmark families

Every kind of search, measured the way the industry measures it

We use the suites other engines already publish against, so every result can be checked against a number someone else produced.

Results

Elasticsearch compatibility

Elastic's own Rally tracks sent to WarpSearch's Elasticsearch API: full-text, sorting, aggregations, nested documents, geo and scroll.

nestedgeonamespmcgeopointgeopointshape

Compared with: Elasticsearch nightly benchmarks

See Rally results →
Results

Vector search

Recall against latency and load time for approximate nearest-neighbour search, on the dataset vector databases publish against.

VectorDBBenchCohere 1M768-d

Compared with: S3 Vectors, pgvector, turbopuffer, Weaviate, Elastic Cloud, OpenSearch, Qdrant

See vector results →
Results

turbopuffer workloads

turbopuffer's open harness and website configuration, run against WarpSearch's turbopuffer-compatible API.

vector 10Mvector 1Mvector 100Kfull-text

Compared with: turbopuffer's homepage, docs and blog figures

See turbopuffer results →
Coming soon

Percolation (reverse search)

Store millions of queries and find the ones that match each new document. On Rally's percolator track with 2M stored queries, WarpSearch is 2.7x to 5.9x faster than Elasticsearch.

Rally percolator2M queries
Coming soon

Hybrid search and relevance

Ranking quality for keyword, vector and hybrid search on judged query sets, next to Elasticsearch, OpenSearch and Apache Pinot.

Amazon ESCIBEIRMS MARCO
Coming soon

Logs and observability

Log ingestion, time ranges and aggregations on the log tracks Elasticsearch and OpenSearch publish against.

http_logsbig5nyc_taxis

How we measure

Four rules every result follows

1

Their benchmark, their numbers.We pick workloads a competitor already publishes, run them on WarpSearch, and quote the competitor's own figure with its source and date. We do not install or tune other engines.

2

Official tracks and harnesses.Rally tracks, VectorDBBench and turbopuffer's harness run as published, against WarpSearch's compatible APIs.

3

Recall next to vector latency.A fast answer with the wrong neighbours is not a result. Where a vendor publishes recall, we compare at the same recall or higher.

4

Every number says what was timed.Server time and client time are labelled on every page, so you can see exactly what is being compared.

Run it on your own data.

Point your Elasticsearch, OpenSearch or turbopuffer client at WarpSearch and see the numbers for your workload. Free up to 1 GB.

Cookie settings

Optional tracking stays off until you choose it. Your choice applies to this browser for 180 days. Read the details.

Essential storage keeps you signed in, protects forms, and remembers this choice. It is always available.