Cloud Run configuration shift for low‑traffic workloads cost reduction

Goal

Lower the ongoing cost of running a low‑traffic workload on Google Cloud while keeping the service responsive to occasional requests.

Context

The Well‑Architected Framework’s cost‑optimization pillar recommends granular control of performance and cost parameters to maximize business value.

It is unclear which Cloud Run‑specific setting (for example, CPU allocation, concurrency limit, or minimum instances) should be changed first to achieve the greatest cost saving without hurting latency for sporadic traffic.

• Which Cloud Run configuration should be adjusted first to reduce cost for a workload that receives only a few requests per day?
• How does changing that setting affect cold‑start latency compared with the current configuration?
• Are there any compatibility constraints (such as minimum CPU or secret‑volume access) when applying the chosen setting?