Diagram

A left-to-right process flow from incoming requests through the load balancer to Cloud Run instances; when Instance 1 exceeds the 60 percent concurrency target of about 48 of 80 requests, the autoscaler starts Instance 2, and idle instances scale back in.
Traffic-Driven Scaling Triggers
Scaling triggers in Cloud Run are utilization targets that tell the autoscaler when to add instances to handle load. Cloud Run supports a streamlined set of scaling controls:
template.maxInstanceRequestConcurrency)scaling.max_instance_count and scaling.min_instance_count)template.scaling.cpuUtilization and template.scaling.concurrencyUtilization)When concurrent requests or CPU load approach the configured target, traffic flows from the load balancer to existing instances and the autoscaler provisions new instances in parallel. Cloud Run autoscales before requests start queueing, so latency spikes are avoided when capacity is sufficient. If latency still spikes, lowering maximum concurrency causes faster scale-out because each instance accepts fewer simultaneous requests.
Domain 12 of 12
24 practice questions
Practice this DomainLast updated