gcp-cloud-run

Topics in the source

• GCP Cloud Run
• Patterns
• Cloud Run Service Pattern
• Cloud Run Functions Pattern
• 2. Set Minimum Instances
• 3. Optimize Container Image
• 4. Lazy Initialize Heavy Dependencies
• 5. Increase Memory (More CPU)

Containerized web service on Cloud Run When to use: ['Web applications and APIs', 'Need any runtime or library', 'Complex services with multiple endpoints', 'Stateless containerized workloads'] Event-driven functions (formerly Cloud Functions) When to use: ['Simple event handlers', 'Pub/Sub message processing', 'Cloud Storage triggers', 'HTTP webhooks'] Why bad: CPU is shared across concurrent requests. CPU-bound work will starve other requests, causing timeouts. Why bad: /tmp is an in-memory filesystem. Large files consume your memory allocation and can cause OOM errors. Why bad: Cloud Run throttles CPU to near-zero when not handling requests. Background tasks will be extremely slow or stall. | Issue | Severity | Solution | |-------|----------|----------| | Issue | high | ## Calculate memory including /tmp usage | | Issue | high | ## Set appropriate concurrency | | Issue | high | ## Enable CPU always allocated | | Issue | medium | ## Configure connection pool with keep-alive | | Issue | high | ## Enable startup CPU boost | | Issue | medium | ## Explicitly set execution environment | | Issue | medium | ## Set consistent timeouts |