Configure CPU limits for jobs Stay organized with collections Save and categorize content based on your preferences.
This page describes how to specify the number of vCPUs to use for eachCloud Run instance. By default, Cloud Run container instancesare limited to 1 vCPU. You can increase or decrease thisvalue as described in this page.
Set and update vCPU limits
By default, each instance is limited to 1 vCPU.You can change this to any of the values shown in the following table.
vCPU and memory table
The following are memory requirements for vCPUs:
| CPUs | Memory required |
|---|---|
| 1 vCPU | 128 MiB to 4 GiB |
| 2 vCPU | 128 MiB to 8 GiB |
| 4 vCPU | 2 to 16 GiB |
| 6 vCPU | 4 to 24 GiB |
| 8 vCPU | 4 to 32 GiB |
Alternatively, if you want to use less than 1 vCPU, you can select any valuebetween 0.08 and 1, in increments of 0.001. Values greater than 1 must be integervalues.If you use less than 1 vCPU, the following requirements are enforced:
| Setting | Requirement |
|---|---|
| Memory | A minimum of 0.5 vCPU is needed to set amemory limit greater than 512MiB. A minimum of 1 vCPU is needed to set a memory limit greater than 1GiB. |
| Concurrency | Maximum concurrency must be set to1. |
| Billing | Thebilling settings must be set to request-based billing. |
| Containers | You mustdeploy multiple containers (sidecars). |
Maximum amount of vCPU
The maximum amount of vCPU you can configure is 8 vCPU.
Minimum amount of vCPU
The minimum vCPU setting is 0.08 vCPU.
Required roles
To get the permissions that you need to configure Cloud Run jobs, ask your administrator to grant you the following IAM roles:
- Cloud Run Developer (
roles/run.developer) on the Cloud Run job - Service Account User (
roles/iam.serviceAccountUser) on the service identity
For a list of IAM roles and permissions that are associated withCloud Run, seeCloud Run IAM rolesandCloud Run IAM permissions.If your Cloud Run job interfaces withGoogle Cloud APIs, such as Cloud Client Libraries, see theservice identity configuration guide.For more information about granting roles, seedeployment permissionsandmanage access.
Configure CPU limits
You must set a minimum of 1 CPU for a Cloud Run job.
To specify CPU for a Cloud Run job:
Console
In the Google Cloud console, go to the Cloud RunJobs page:
ClickDeploy container to fill outthe initial job settings page. If you are configuring an existing job,select the job, then clickView and edit job configuration.
ClickContainer(s), Volumes, Connections, Security to expand the job properties page.
Click theGeneral tab.

- Select the desired CPU limit from the dropdownlist. Select a value of
1,2,4,6, or8CPUs. Jobs require a minimum of 1 CPU. (See the table underSetting and updating CPU limits for required settings.)
- Select the desired CPU limit from the dropdownlist. Select a value of
ClickCreate orUpdate.
gcloud
Update the CPU limitsof a given job by using the following command:
gcloudrunjobsupdateJOB_NAME--cpuCPUReplace
- JOB_NAME with the name of your job
- CPU with the desired CPU limit. Specify the value
1,2,4,6, or8CPUs. Jobs require a minimum of 1 CPU. (See the table underSetting and updating CPU limits for required settings.)
You can also set CPU when youcreate a job using the command:
gcloudrunjobscreateJOB_NAME--imageIMAGE_URL--cpuCPUReplace
- JOB_NAME with the name of your job.
- IMAGE_URL: a reference to thecontainer image—forexample,
us-docker.pkg.dev/cloudrun/container/job:latest. - CPU with the desired CPU limit. Specify the value
1,2,4,6, or8CPUs. Jobs require a minimum of 1 CPU. (See the table underSetting and updating CPU limits for required settings.)
YAML
If you are creating a new job, skip this step.If you are updating an existing job, download itsYAML configuration:
gcloudrunjobsdescribeJOB_NAME--formatexport>job.yaml
Update the
cpuattribute:apiVersion:run.googleapis.com/v1kind:Jobmetadata:name:JOBspec:template:spec:template:spec:containers:-image:IMAGEresources:limits:cpu:CPU
ReplaceCPU with the desired CPU limit. Specify the value
1,2,4,6, or8CPUs. Jobs require a minimum of 1 CPU. (See the table underSetting and updating CPU limits for required settings.)You can also specify more configuration such as environment variables ormemory limits.
Update the existing job configuration:
gcloudrunjobsreplacejob.yaml
Terraform
To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.
Add the following to agoogle_cloud_run_v2_job resource in your Terraform configuration:resource"google_cloud_run_v2_job""default"{name="cloudrun-job"location="REGION"deletion_protection=falsetemplate{template{containers{image="us-docker.pkg.dev/cloudrun/container/job"resources{limits={cpu="CPU"}}}}}}Replace:
- REGION with the Google Cloud region. For example,
europe-west1. - CPU with your service's required memory limit.Specify the value
1,2,4,6, or8CPUs. Jobs require a minimum of 1 CPU. (See the table underSetting and updating CPU limits for required settings.)
View CPU settings
To view the current CPU settings for yourCloud Run job:
Console
In the Google Cloud console, go to the Cloud Run jobs page:
Click the job you are interested in to open theJob details page.
ClickView and Edit job configuration.
Locate the CPU setting in the configurationdetails.
gcloud
Use the following command:
gcloudrunjobsdescribeJOB_NAMELocate the CPU setting in the returnedconfiguration.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.