A deep dive into how we scale Postgres in real time

by Carlota Soto

Choosing a database instance size before you know the workload is an old building pattern. The process is generally wonky and feels very wasteful of compute, especially now that compute is becoming a luxury.

Lakebase Postgres omits the sizing experience altogether thanks to autoscaling. Autoscaling responsiveness comes from in-place VM resizing and an algorithm that tracks CPU, memory, and the database’s working set.

How autoscaling looks like for an arbitrary sample of Lakebase Postgres databases. Note how this is only one hour.