Lakebase compute cache (low-latency reads of hot data)

Each Lakebase compute keeps hot data close to Postgres in two tiers: the Postgres shared buffers in memory and a local disk-backed compute cache sized to the compute's memory, so frequent reads avoid trips to the pageservers and object storage. The cache has been part of every Lakebase compute since the autoscaling version of Lakebase launched. This row was previously listed as Lakebase low-latency query execution.

Status and dates are extracted from public sources only. We don't see the private AE-shared roadmap. If something looks wrong, tell us.