Topic

Database caching

How database engines keep hot data in memory and on local disk to avoid fetching pages from slower storage, including buffer pool sizing and the replacement policies that decide what stays resident.

Current clusters

build2 publishers

Databricks raises Lakebase's 1 GB shared buffers cap to most of the machine's memory

Hot pages on large fixed-size Lakebase computes now sit in Postgres shared buffers backed by huge pages instead of falling through to the local file cache, and Databricks measures up to about 2x throughput.

Publishers:databricks.comneon.tech

Reality

Evidence55
Adoption40
Hype gap+15
Incentives85
Confidence60