ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The goal is to configure a Cloud Run service so that its outbound connection pool never exceeds the per‑instance socket limit (approximately 1000 sockets) while still allowing the requested level of concurrency. Cloud Run’s max concurrency setting controls how many request instances can run simultaneously inside a container, but it does not constrain how man
Goal: ensure that a Cloud Run service processing at-least-once messages does not perform duplicate writes when the invoking service retries delivery. Constraint: Cloud Run itself does not retry; the caller (e.g., Pub/Sub push or Cloud Tasks) may redeliver the same request with a potentially different value for the platform‑provided X‑Cloud‑Run‑Request‑ID hea
When optimizing a low-traffic workload on Cloud Run, setting min-instances to 0 and selecting "CPU allocated only during request processing" is the standard approach to eliminate idle costs. However, this configuration introduces a specific risk during the transition from zero to one active instance. If a container requires a heavy initialization phase—such
A low-traffic workload is currently configured with a minimum instance count greater than zero to prevent cold-start latency. To reduce monthly spend, the goal is to transition to a scale-to-zero configuration where CPU is only allocated during request processing. The primary constraint is the trade-off between the continuous billing of warm instances and th
Goal Safely recover from a Cloud Run revision that fails health checks after an upgrade, ensuring minimal service disruption and preserving request integrity. Constraints & Uncertainty Cloud Run’s traffic‑splitting feature allows a new revision to receive a percentage of traffic, but the platform does not automatically revert traffic to the previous revi
Goal Determine whether increasing Cloud Run maximum request concurrency reduces tail latency when many requests arrive at the same time, or whether it mainly moves queuing from Cloud Run scale-out into the container instance. Constraints and uncertainty Cloud Run fully managed routes multiple concurrent requests to one container instance up to the configured
Cloud Run Request Termination Signal After Client Cancellation Goal: determine whether Cloud Run exposes a distinguishable termination signal when an HTTP client cancels a request before the configured request timeout expires, versus when the platform itself enforces the timeout (2nd generation default five minutes, maximum sixty minutes). Constraint: a clie
Goal: choose the lower-cost Google Cloud option for an infrequently invoked HTTP endpoint. Cloud Run fully managed bills per request plus vCPU and memory during processing, with configurable concurrency and scale-to-zero. Cloud Functions 2nd generation bills per invocation plus compute time and memory, with no idle-instance charge but per-instance concurrenc
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
cloudrun
google