Question

A customer-facing checkout API runs on Cloud Run. During business hours, users occasionally report multi-second delays on the first request after periods of low traffic, and traces confirm these are cold-start latencies while container instances initialize. Traffic is steady during the day but drops to near zero overnight. The team wants to eliminate the daytime cold-start delays while keeping cost as low as possible. Which configuration best meets both goals?

Accepted Answer

Set a minimum number of instances on the service, sized to the typical daytime baseline, and leave the maximum instance limit for scaling under load.

Answer

Increase the per-instance concurrency to the maximum so a single instance can absorb all requests and no scaling occurs.

Answer

Set minimum instances to match the peak daytime instance count so no scaling event ever triggers a cold start.

Answer

Allocate more CPU and memory per instance so containers initialize faster when a cold start happens.