> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lancedb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Page Cache

> How LanceDB Enterprise caches table data pages to avoid re-reading object storage.

**Applies to:** Embedded ❌, Enterprise ✅

The data page cache holds fixed-size pages of raw table data read from
object storage, keyed by their location, so a later read of the same range
is served from memory or local disk instead of round-tripping to the
backing store. Plan executors and query nodes each keep their own cache for
the pages they serve. A background prewarm job can populate a cache ahead
of a request that needs it, rather than filling it lazily on first read.
See [Architecture](https://docs.lancedb.com/index.md#architecture).

```mermaid theme={"theme":{"light":"vitesse-light","dark":"catppuccin-mocha"}}
%%{init: {"theme": "base", "themeVariables": {
  "background": "#ffffff", "primaryColor": "#ffffff", "primaryTextColor": "#221d19",
  "primaryBorderColor": "#ad9e95", "lineColor": "#6b625c", "textColor": "#221d19",
  "edgeLabelBackground": "#ffffff", "fontFamily": "Inter, sans-serif", "fontSize": "18px"
}}}%%
flowchart LR
    R["Read request<br/>for a data page"] --> M{"In memory?"}
    M -->|hit| Return["Served from memory"]
    M -->|miss| D{"In local disk cache?"}
    D -->|hit| Promote["Loaded into memory,<br/>served"]
    D -->|miss| O[("Object storage")]
    O --> Fill["Fills memory and disk,<br/>served"]
    classDef default fill:#ffffff,stroke:#ad9e95,stroke-width:1px,color:#221d19
```

A table's local disk cache shares one configurable budget with the
[tiered index cache](https://docs.lancedb.com/enterprise/tiered-index-cache.md#disk-budget)'s disk
tier where both are enabled on the same executor.

## Why it matters

Object storage is durable and cheap, but every round trip to it adds
latency and egress cost. For workloads that read the same ranges
repeatedly -- a hot subset of embeddings, a frequently-filtered column --
the data page cache turns most of those reads into local memory or disk
hits instead, so performance stays predictable as traffic grows and you
pay object storage once per page, not once per read.

[Contact us](https://www.lancedb.com/contact) to learn more about how
caching is sized and tuned for your workload.

## Cache interfaces

* [Tiered Index Cache](https://docs.lancedb.com/enterprise/tiered-index-cache.md) for the related
  cache that holds deserialized index structures instead of raw data pages.
* [Query plans](https://docs.lancedb.com/basics/sql.md#query-plans) for inspecting what a query actually read.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.