Quick answer
Neon documents local file cache as 75% of compute RAM. The cache is tied to compute memory rather than persistent database storage.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| local file cacheThe cache is tied to compute memory rather than persistent database storage. | 75% of compute RAM | Neon computes | NeonAug 22, 2026 |
Why does this limit matter?
Compute size affects both connection capacity and local cache available for frequently accessed pages.
This value is scoped to Neon computes; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Compare working-set size, compute RAM, autosuspend behavior, and observed cache hit rates.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- The cache can warm and cool with compute lifecycle and should not be treated as durable data.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related