Scale a Cluster
Scale a cluster's compute or cache capacity to meet workload requirements. Choose a scaling method based on the resource and workload pattern.
Choose a scaling method
| Your goal | Scaling method | Behavior |
|---|---|---|
| Make a one-time compute adjustment | Manual scaling | Scale on-demand compute out or in. Cache capacity adjusts with compute capacity. |
| Adjust compute as workload demand changes | Auto Scaling | Automatically adjust on-demand compute within the configured vCPU range. |
| Adjust compute on a daily schedule | Time-Based Scaling | Set target vCPU values for specified times each day. |
| Increase cache capacity without adding vCPU | Manual scaling (Cache) | Scale out cache independently. Separate cache scale-in is not supported. |
When AutoScaling is enabled, manual and time-based scaling are unavailable. Disable it before you choose another strategy.
When time-based scaling is enabled, disable it before scaling manually or enabling AutoScaling.
Understand scaling impact
Warning:
- Scaling can temporarily interrupt connections and delay requests.
- Scaling in compute can reduce cache capacity, but not below the minimum for the target compute size. If cache capacity decreases, cached data beyond the new capacity is removed, which can affect request response times.
Before you scale
- You need permission to manage compute resources in the warehouse.
- The cluster must be Running, and the warehouse must not be in the Creating state.
- If Scaling is unavailable, point to it to view the reason.
- For manual scaling, review the current and estimated new cost before confirming the change.
Open scaling settings
- Log in to the VeloDB Cloud console.
- In the upper-left corner, select the warehouse that contains the cluster.
- In the left navigation pane, under Compute, click Clusters.
- Click Physical Clusters.
- Click Card, then select the running cluster to display its details panel.
- Click Scaling.
- If a resource menu opens, select On-Demand (Hourly).
In Elastic Scaling, you can configure Auto Scaling, manual scaling, or time-based scaling.
After a resource change is submitted, the cluster status changes to Scaling and then returns to Running. Verify the new compute and cache values in the cluster details panel.