Question

A retail analytics team runs a nightly data-aggregation workload that takes about 40 minutes to complete and does not serve HTTP traffic. It currently runs on a Cloud Run service kept alive with a minimum of one instance, and a Cloud Scheduler job hits an endpoint each night to trigger processing. Finance flags that the service is being billed for idle CPU throughout the day. You need to minimize cost while keeping the workload serverless and scheduled. What should you do?

Accepted Answer

Migrate the workload to a Cloud Run job triggered on a schedule with Cloud Scheduler, so compute is billed only for the duration of each execution.

Answer

Keep the Cloud Run service but set minimum instances to 0 and rely on the scheduled request to warm it up before processing.

Answer

Move the workload to a Compute Engine VM with an instance schedule that starts and stops the VM around the nightly window.

Answer

Increase the Cloud Run service concurrency to 1000 so the single instance processes more work per unit of billed time.