You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apply self-review findings: drop unqualified recycling, fix docs drift
Worker recycling (--max-requests) is removed rather than retuned:
review analysis showed the 500-request budget recycles faster than the
~170s re-import at peak (the counter advances on cheap requests too),
jitter 100 cannot decorrelate two workers, a mid-life re-import runs
without cpu-boost and CPU-throttled at idle, and the qualifying soak
never executed a recycle. The ops doc now records why it needs its own
qualification. Also: pin assertions get boundary anchors; the ops doc's
source-of-truth section acknowledges push.yml job pins; stale cold-start
figures replaced with measured values; the changelog credits staging's
shape change; the min-instances runbook gains WHEN + verification; the
duplicated rationale comments collapse to pointers; load-generator
cleanup (single exception path, Counter, always/never cache-bust, dead
fields removed).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Configure the production Cloud Run runtime from the Stage 2 capacity qualification: two gunicorn workers, request concurrency 4, production max-instances 4, staging pinned to scale-to-zero, and worker recycling to bound memory growth.
1
+
Configure both Cloud Run services' runtime from the Stage 2 capacity qualification — two gunicorn workers and request concurrency 4 on staging and production alike — plus production max-instances 4 and explicit staging scale-to-zero pins.
0 commit comments