Good point on the sustained usage changing the economics at the scale they're at, I didn't really factor that in.
The pricing calculation is even more complex than it seems. Cloud Run doesn't charge per request if you have "always allocated CPU" (a new feature). Also, instances can handle up to 1000 concurrent requests. So, we'd need to know processing time and work out how many instances would need to run concurrently. There's also committed usage discounts for Cloud Run.
Another factor to consider is operational cost - Cloud Run has a lower ops burden than K8s - particularly if you wanted to run multi-regional instances.
But you're right - at the sustained usage they have, the infrastructure cost of Cloud Run would almost certainly be worse than VMs in GKE, particularly if they could run on a decent percentage of preemptible instances.
Comments
Good point on the sustained usage changing the economics at the scale they're at, I didn't really factor that in.
The pricing calculation is even more complex than it seems. Cloud Run doesn't charge per request if you have "always allocated CPU" (a new feature). Also, instances can handle up to 1000 concurrent requests. So, we'd need to know processing time and work out how many instances would need to run concurrently. There's also committed usage discounts for Cloud Run.
Another factor to consider is operational cost - Cloud Run has a lower ops burden than K8s - particularly if you wanted to run multi-regional instances.
But you're right - at the sustained usage they have, the infrastructure cost of Cloud Run would almost certainly be worse than VMs in GKE, particularly if they could run on a decent percentage of preemptible instances.