Cloud Run's CPU throttling silently freezes background tasks after HTTP response
A developer building an agent on Google Cloud Run discovered that background tasks scheduled after sending an HTTP response were silently freezing for minutes or never completing. The root cause is…
Read the full articleYou might also wanna read
Why average CPU utilization is a misleading metric for cloud-native applications
How CFS throttling works and the case against the average CPU graph.
![](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 100"><rect width="100" height="100" rx="12" fill="%23002b36"/><text x="50" y="68" font-family="system-ui,sans-serif" font-size="48" font-weight="bold" fill="%23cb4b16" text-anchor="middle">JT</text></svg>)
theocharis.dev·1mo ago
Cloudflare Discovers Race Condition Bug in Go's ARM64 Compiler
84 million requests a second means even rare bugs appear often. We'll reveal how we discovered a race condition in the Go arm64 compiler and
blog.cloudflare.com·9mo ago
Cache - BYPASS status now returned for uncacheable responses
Cloudflare now returns a BYPASS cache status whenever a response is not cacheable, instead of the previous mix of BYPASS and MISS that depen
8 production-ready features you'll find in Cloud Run fully managed
Since we launched Cloud Run at Google Cloud Next in April, developers have discovered that “serverless” and “containers” run well together.
Workers - Python cold start improvements
Python Workers now feature improved cold start performance, reducing initialization time for new Worker instances. This improvement is parti
Google Cloud revives AI agent roadshow for Cloud Run
Demand for production-ready AI agents is pushing Google to reframe Cloud Run as a platform for long-running, data-driven workloads.
Comments
Sign in to join the conversation.
No comments yet. Be the first.