Autoscaling schedules: reduce cold-start delays for predictable traffic

From the source

Use autoscaling schedules to start replicas before your traffic arrives, so requests don’t wait on cold starts. Authors Published October 30, 2026 Share Published October 30, 2026 Autoscaling schedules reduce cold-start delays by raising the minimum number of replicas before predictable traffic arrives.

You can set a schedule to recur (e.g., weekday mornings) or to run once (e.g., ahead of a product launch). Configure up to 10 schedules per environment through the dashboard, CLI, or Management API. Autoscaling adjusts the number of replicas to match incoming traffic.

When demand increases, new replicas need time before they can handle requests. This is their cold-start time , which includes allocating compute resources, starting the serving software, and loading the model. Requests that wait during a cold start have longer end-to-end response times.

Autoscaling schedules help avoid cold-start delays by starting additional replicas before traffic arrives. You can set a schedule to recur (e.g., every weekday morning) or to run once (e.g., ahead of a launch). Schedule autoscaling around demand Many workloads have predictable traffic. …

baseten.co