This is Cloud Run: Configuration

This is Part 3 of the "This is Cloud Run" series. In Part 1, we covered what Cloud Run is and when to choose it. In Part 2, we walked through the deployment options and revision management. Now let's tune it. Cloud Run's defaults are good. We covered that in Part 1. But every workload has its own needs, and Cloud Run gives you the knobs to tune for them. This article covers the settings you'll reach for most often. CPU and Memory Every Cloud Run instance gets a share of CPU and memory. The defaults (1 vCPU, 512 MiB) are reasonable for a lightweight API, but you'll want to adjust them as you understand your workload's needs. CPU ranges from 0.08 vCPU (less than a tenth of a core) to 8 vCPUs. Memory ranges from 128 MiB to 32 GiB. The two are linked: higher CPU allocations require minimum memory thresholds, and some memory configurations require minimum CPU. But the more important decision is the CPU allocation mode: Request-only (default). CPU is only allocated while your instance is act