CPU limits

This page describes how to specify the number of CPUs to use for each Cloud Run container instance. By default Cloud Run container instances are limited to 1 CPU instance. You can change this number.

Setting and updating CPU limits

Any configuration change leads to the creation of a new revision. Subsequent revisions will also automatically get this configuration setting unless you make explicit updates to change it.

By default, each container instance is limited to 1 CPU. You can set CPU limits using the Cloud Console, the gcloud command line, or a YAML file when you create a new service or deploy a new revision:

Console

  1. Go to Cloud Run

  2. Click Create Service if you are configuring a new service you are deploying to. If you are configuring an existing service, click on the service, then click Edit and Deploy New Revision.

  3. If you are configuring a new service, fill out the initial service settings page as desired, then click Next > Advanced settings to reach the service configuration page.

  4. Click the Container tab.

    image

  5. Select the desired CPU limit from the dropdown list. Select a value of 1, 2, or 4 vCPUs. (Note that using 4 vCPUs requires you to use a minimum of 2 GiB memory.).

  6. Click Create or Deploy.

Command line

You can update the CPU limits for a given service by using the following command:

gcloud run services update SERVICE --cpu CPU

Replace SERVICE with the name of your service and CPU with the desired CPU limit. Specify the value 1, 2, or 4 vCPUs. (Note that using 4 vCPUs requires you to use a minimum of 2 GiB memory.).

You can also set CPU during deployment using the command:

gcloud run deploy --image IMAGE_URL --cpu CPU

Replace

  • IMAGE_URL with a reference to the container image, for example, us-docker.pkg.dev/cloudrun/container/hello:latest.
  • CPU with the values described above.

YAML

You can download and view existing service configuration using the gcloud run services describe --format export command, which yields cleaned results in YAML format. You can then modify the fields described below and upload the modified YAML using the gcloud run services replace command. Make sure you only modify fields as documented.

  1. To view and download the configuration:

    gcloud run services describe SERVICE --format export > service.yaml
  2. Update the cpu attribute:

    apiVersion: serving.knative.dev/v1
    kind: Service
    metadata:
      name: SERVICE
    spec:
      template:
        spec:
          containers:
          - image: IMAGE
            resources:
              limits:
                cpu: CPU

    Replace

    • SERVICE with the name of your Cloud Run service
    • IMAGE with the URL of your container image.
    • CPU with the desired CPU limit value. Specify the value 1, 2, or 4 vCPUs. (Note that using 4 vCPUs requires you to use a minimum of 2 GiB memory.).
  3. Replace the service with its new configuration using the following command:

    gcloud run services replace service.yaml

Viewing CPU settings

To view the current CPU settings for your service:

Console

  1. Go to Cloud Run

  2. Click the service you are interested in to open the Service details page.

  3. Click the Revisions tab.

  4. In the details panel at the right, the CPU setting is listed under the Container tab.

Command line

  1. Use the following command:

    gcloud run services describe SERVICE
  2. Locate the CPU setting in the returned configuration.