3 documented GCP Cloud Run cost inefficiencies, each with how to detect it and how to fix it.
GCP Cloud RunCER-0179
In Cloud Run, each revision is deployed with a fixed memory allocation (e.g., 512MiB, 1GiB, 2GiB, etc.). These settings are often overestimated during initial development or copied from templates. Unlike auto-scaling platforms that adapt...
GCP Cloud RunCER-0470
Cloud Run services run under one of two billing settings. Request-based billing, the default, charges CPU and memory only while an instance is starting, shutting down or processing at least one request, and adds a per-request fee....
GCP Cloud RunCER-0471
Cloud Run scales to zero by default, but the minimum instances setting keeps a number of instances started and warm so requests avoid cold starts. Those instances are billed whether or not traffic arrives. Minimums are often raised for a...
