Setting maximum concurrency (services)

To understand the maximum concurrency setting, read the Concurrency concept document.

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.

For Cloud Run services, you can set maximum concurrency using the Cloud console, the gcloud command line, or using a .yaml file when you create a new service or deploy a new revision:

Console

Go to Cloud Run
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.
If you are configuring a new service, fill out the initial service settings page as desired, then click Next > Container, Variables & Secrets, Connections, Security to reach the service configuration page.
Click the Container tab.
Set the desired maximum concurrency value in the text box Maximum requests per container.
Click Create or Deploy.

Command line

To set maximum concurrency, use the following command:

gcloud run services update SERVICE --concurrency CONCURRENCY

Replace

SERVICE with the name of your service.
CONCURRENCY with the maximum number of concurrent requests per container instance. For example the following sets a maximum of 40 concurrent requests:
```
gcloud run services update SERVICE --concurrency 40
```

Changing the maximum concurrency of a given service will capture this setting in a new revision.

To revert to the default maximum concurrency (80), use the command

gcloud run services update SERVICE --concurrency default

Replace SERVICE with the name of the service you are configuring.

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.

To view and download the configuration:

gcloud run services describe SERVICE --format export > service.yaml

Update the containerConcurrency attribute:
```
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: SERVICE
spec:
  template:
    metadata:
      name: REVISION
    spec:
      containerConcurrency: CONCURRENCY
```
Replace
- SERVICE with the name of your Cloud Run service
- IMAGE_URL with a reference to the container image, for example, us-docker.pkg.dev/cloudrun/container/hello:latest
- CONCURRENCY with the maximum number of concurrent requests per container instance.
- REVISION with a new revision name or delete it (if present). If you supply a new revision name, it must meet the following criteria:
  - Starts with SERVICE-
  - Contains only lowercase letters, numbers and -
  - Does not end with a -
  - Does not exceed 63 characters
Replace the service with its new configuration using the following command:
```
gcloud run services replace service.yaml
```

View concurrency settings

To view the current concurrency settings for your Cloud Run service:

Console

Go to Cloud Run
Click the service you are interested in to open the Service details page.
Click the Revisions tab.
In the details panel at the right, the concurrency setting is listed under the Container tab.

Command line

Use the following command:
```
gcloud run services describe SERVICE
```
Locate the concurrency setting in the returned configuration.