Tiered Index Cache

Applies to: Embedded ❌, Enterprise ✅ The tiered index cache holds deserialized vector, full-text and scalar index structures in memory, backed by a local-disk tier beneath it. When memory fills, the cache serializes evicted entries and spills them to disk instead of dropping them; a later hit on a spilled entry promotes it back into memory. This lets a plan executor serve an index larger than its available memory without re-reading and re-deserializing it from object storage on every eviction. See Architecture.

​

Sharing the disk budget

Where enabled, the index disk tier and the data page cache’s disk tier draw from one combined, configurable disk allocation per executor, split between the two tiers so neither one needs its own dedicated volume.

​

Why it matters

Vector, full-text, and scalar indexes can easily outgrow available memory on large tables. Without this cache, an eviction means re-reading and re-deserializing that index from object storage on the next request — slow, and repeated on every eviction. Spilling to local disk instead keeps index lookups fast even when the working set is larger than memory, without giving every executor enough memory to hold every index at once. Contact us to learn more about how caching is sized and tuned for your workload.

​

Index cache interfaces

• Cache Prewarm for warming this cache ahead of the first request.
• Data Page Cache for the related cache that holds raw table data pages instead of deserialized index structures.
• Vector indexes, full-text indexes, and scalar indexes for the index types this cache serves.