Databricks
@databricks
Why size Postgres for a peak you rarely reach?
Lakebase Postgres autoscaling watches CPU, memory, and the database’s working set, then resizes compute to match the workload in real time.
Because storage and compute are separated, CPU and memory can be added or removed on a running VM without stopping Postgres or dropping connections.
That means capacity can scale up when demand rises and scale down when it falls, so you stop paying for compute you no longer need.
https://t.co/w6droCQ6Pc