# Databricks benchmarks Lakebase Search vector latency at 1M to 4M passages

> Original title: We benchmarked Lakebase Search on 1M to 4M passages to understand how vector search performs as the index grows. Here's what we learned 👇

- Source: Databricks
- Published: 2026-11-03T20:38:02.000Z
- Bad Influence: https://badinfluence.news/items/jo2r13cna6my6ugj9g0naurg8
- Original: https://x.com/databricks/status/2117717961628582036

## Summary

Databricks benchmarked Lakebase Search on 1M to 4M passages and found cache size relative to the vector index mattered more than row count. When the cache roughly matched the index, 95–98% of page reads avoided storage and warm vector search p50 latency stayed between 11 and 23 ms.

## Post

We benchmarked Lakebase Search on 1M to 4M passages to understand how vector search performs as the index grows. Here's what we learned 👇

Cache size relative to the vector index mattered more than row count. When the cache roughly matched the index, 95–98% of page reads avoided storage and warm vector search p50 latency stayed between 11 and 23 ms.

As datasets grow, sizing the cache alongside the vector index helps maintain low-latency search.
https://www.databricks.com/blog/sizing-lakebase-search-lessons-real-app-and-4-million-passages?utm_source=twitter&utm_medium=organic-social

![](https://badinfluence.news/api/img-proxy?u=https%3A%2F%2Fpbs.twimg.com%2Fmedia%2FHWOlQ3uXwAA2Euh.png&mode=thumb&exp=1793923200&sig=7acbfa07ccf1f448)