๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Databricks
@databricks
Databricks is the Data + AI company, helping organizations build and scale data and AI apps, analytics and agents.
๊ฐ€์ž… July 2013
1.1K ํŒ”๋กœ์ž‰ ์ค‘    99.6K ํŒฌ
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.
๋” ๋ณด๊ธฐ