Skip to main content

Time-Based Scaling

Time-based scaling adjusts a cluster's compute capacity at fixed daily times. Use it when workload peaks and low periods are predictable, such as regular business hours and overnight traffic.

Each policy requires at least two rules with different Target vCPU values so VeloDB Cloud can scale out and scale in over the day.

Warning:

  • Queries can be delayed or interrupted while the cluster scales.
  • When scaling in compute, cache space shrinks proportionally, and data outside the new cache capacity is evicted. Query latency may increase while the cache warms up again.

Rule requirements and limitations​

  • A rule for an on-demand cluster cannot set Target vCPU to 0.
  • A rule runs only when the cluster is Running. If the cluster is paused, rebooting, or upgrading, VeloDB Cloud retries the rule for up to 30 minutes, then skips it.
  • Rules run every day. You cannot change the execution period.
  • Rule execution times must be at least one hour apart and cannot overlap. A cluster can have up to 24 rules.

Before you configure a policy​

  • Ensure that your organization has sufficient cash balance or an active cloud marketplace deduction channel for a rule to execute.
  • SaaS free-trial clusters do not support time-based scaling.
  • Disable AutoScaling before configuring a time-based policy. Auto Scaling disables manual and time-based scaling.

Configure a time-based scaling policy​

  1. Log in to the VeloDB Cloud console.
  2. In the upper-left corner, select the warehouse that contains the cluster.
  3. In the left navigation pane, under Compute, click Clusters.
  4. Click the target cluster card to open its details page.
  5. In On-Demand Resources, click Scale Out/In to open Elastic Scaling.
  6. Under Scaling Strategy, select Time-based Scaling.
  7. Click + Add to create a rule.
  8. Configure the rule:
    • Execution Period: Select Every day.
    • Execution Time: Set the time when scaling occurs (for example, 00:00).
    • Target vCPU: Enter the desired compute size.
  9. Add at least two rules with different Target vCPU values.
  10. Confirm that the Execution Time values do not overlap and are at least one hour apart.
  11. Enable the Time-based Scaling Policy toggle.

The policy takes effect at each scheduled Execution Time while the cluster is Running.

See also​