ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Cloud Run Concurrency Behavior Under Sustained Traffic Cloud Run allows configuring request concurrency from 1 to 1000 using the --concurrency flag during deployment. When traffic arrives, instances scale from zero and handle requests up to the configured concurrency limit before additional instances are spawned. This scaling mechanism should distribute load
Goal is to configure autoscaling for a Scalingo web container with a defined min and max container count driven by a metric such as RPM or resource usage. The configuration requires choosing a target value and an aggregation window for the metric, plus bounds to limit cost and capacity. Statelessness is assumed for horizontal scaling, and database connection
Goal: Determine whether enabling Heroku autoscaling for a low‑traffic application yields lower monthly cost than running a single hobby dyno (with free dyno hours) when the app experiences intermittent requests. Constraints: Free dyno hours provide ≈550 h/month but cause the dyno to sleep after 30 minutes of inactivity, adding latency on wake‑up; autoscaling
Cluster Autoscaler Default Threshold Behavior Gardener supports cluster autoscaling through the Cluster Autoscaler addon, which can be enabled in the Cluster spec. The addon uses provider-specific default configurations that may not align with a cluster's actual workload characteristics. The decision to enable or disable the autoscaler rests with the cluster
cloudrun
scalingo
heroku
gardener