Question

A team runs a stateless HTTP API on Cloud Run (fully managed). The service is CPU-light but spends most request time waiting on an external payment provider. During traffic spikes, the service scales to hundreds of instances, driving up cost, even though CPU utilization per instance stays below 15%. Latency is acceptable. Which change best reduces cost while maintaining performance?

Accepted Answer

Increase the maximum number of concurrent requests per instance (container concurrency) so each instance handles more simultaneous requests.

Answer

Increase the CPU and memory allocation per instance to speed up request processing.

Answer

Lower the maximum instance limit to cap the number of instances that can be created.

Answer

Enable CPU always-allocated (CPU is always on) instead of CPU allocated only during request processing.