Stay organized with collections
Save and categorize content based on your preferences.
Learn how to set the maximum number of requests that can be processed
simultaneously by a given container instance in Knative serving.
Learn more about concurrency.
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.
You can configure concurrency settings using the Google Cloud console,
or the Google Cloud CLI when you deploy a new
service or update an existing service and
deploy a revision:
Console
Go to Knative serving in the Google Cloud console:
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 & Deploy New Revision.
Under Advanced settings, click Container.
Set the desired concurrency value in the text box Maximum requests per container.
Click Next to continue to the next section.
In the Configure how this service is triggered section,
select which connectivity you would like to use to invoke the service.
Click Create to deploy the image to Knative serving and wait
for the deployment to finish.
Command line
For existing services, set the maximum number of concurrent requests by
running the gcloud run services update command with the
--concurrency
parameter:
CONCURRENCY with the maximum number of
concurrent requests per container instance. Specify default to clear
any concurrency settings: --concurrency default.
For new services, set the maximum number of concurrent requests by running
the gcloud run deploy command with the
--concurrency
parameter:
IMAGE_URL with a reference to the container image, for
example, gcr.io/myproject/my-image:latest.
CONCURRENCY with the maximum number of
concurrent requests per container instance. Specify default to clear
any concurrency settings: --concurrency default.
YAML
You can download the configuration of an existing service into a
YAML file with the gcloud run services describe command by using the
--format=export flag.
You can then modify that YAML file and deploy
those changes with the gcloud beta run services replace command.
You must ensure that you modify only the specified attributes.
Download the configuration of your service into a file named
service.yaml on local workspace:
SERVICE with the name of your Knative serving service
CONCURRENCY with the maximum number of concurrent
requests per container instance. Specify default to clear the
concurrency settings: --concurrency default.
Replace the service with its new configuration using the following command:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eKnative serving allows you to set the maximum number of requests a container instance can handle simultaneously, referred to as concurrency.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring concurrency settings results in a new revision of your service, and subsequent revisions inherit these settings unless explicitly changed.\u003c/p\u003e\n"],["\u003cp\u003eConcurrency can be configured for new or existing services via the Google Cloud console or using the \u003ccode\u003egcloud\u003c/code\u003e command-line tool.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egcloud run services update\u003c/code\u003e or \u003ccode\u003egcloud run deploy\u003c/code\u003e commands with the \u003ccode\u003e--concurrency\u003c/code\u003e parameter are used to set the concurrency from the command line.\u003c/p\u003e\n"],["\u003cp\u003eYou can set the concurrency setting by editing the \u003ccode\u003econtainerConcurrency\u003c/code\u003e attribute in a YAML file, but be cautious since this will overwrite the existing settings of your service.\u003c/p\u003e\n"]]],[],null,["# Setting concurrency\n\nLearn how to set the maximum number of requests that can be processed\nsimultaneously by a given container instance in Knative serving.\n[Learn more about concurrency](/anthos/run/archive/docs/concurrency).\n\nAny configuration change leads to the\ncreation of a new revision. Subsequent revisions will also automatically get\nthis configuration setting unless you make explicit updates to change it.\n\nYou can configure concurrency settings using the Google Cloud console,\nor the Google Cloud CLI when you deploy a new\n[service](/anthos/run/archive/docs/deploying#service) or update an existing service and\ndeploy a [revision](/anthos/run/archive/docs/deploying#revision): \n\n### Console\n\n\n1. Go to Knative serving in the Google Cloud console:\n\n [Go to Knative serving](https://console.cloud.google.com/kubernetes/run)\n2. Click **Create Service** if you are configuring a\n new service you are deploying to. If you are configuring an\n existing service, click on the service, then click\n **Edit \\& Deploy New Revision**.\n\n3. Under *Advanced settings* , click **Container**.\n\n4. Set the desired concurrency value in the text box *Maximum requests per container*.\n\n5. Click **Next** to continue to the next section.\n\n6. In the **Configure how this service is triggered** section,\n select which connectivity you would like to use to invoke the service.\n\n7. Click **Create** to deploy the image to Knative serving and wait\n for the deployment to finish.\n\n### Command line\n\n- For existing services, set the maximum number of concurrent requests by\n running the `gcloud run services update` command with the\n [`--concurrency`](/sdk/gcloud/reference/run/services/update#--concurrency)\n parameter:\n\n ```bash\n gcloud run services update SERVICE --concurrency CONCURRENCY\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your service.\n - \u003cvar translate=\"no\"\u003eCONCURRENCY\u003c/var\u003e with the maximum number of concurrent requests per container instance. Specify `default` to clear any concurrency settings: `--concurrency default`.\n- For new services, set the maximum number of concurrent requests by running\n the `gcloud run deploy` command with the\n [`--concurrency`](/sdk/gcloud/reference/run/deploy#--concurrency)\n parameter:\n\n ```bash\n gcloud run deploy SERVICE --image=IMAGE_URL --concurrency CONCURRENCY\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your service.\n - \u003cvar translate=\"no\"\u003eIMAGE_URL\u003c/var\u003e with a reference to the container image, for example, `gcr.io/myproject/my-image:latest`.\n - \u003cvar translate=\"no\"\u003eCONCURRENCY\u003c/var\u003e with the maximum number of concurrent requests per container instance. Specify `default` to clear any concurrency settings: `--concurrency default`.\n\n### YAML\n\n| **Caution:** Deploying configuration changes using YAML files replaces the configuration of your existing services. Since a YAML file completely overwrites all configurations, you should avoid using multiple methods to modify your services. For example, do not use YAML files in conjunction with the Google Cloud console or `gcloud` commands.\n\nYou can download the configuration of an existing service into a\nYAML file with the `gcloud run services describe` command by using the\n[`--format=export`](/sdk/gcloud/reference/run/services/describe) flag.\nYou can then modify that YAML file and deploy\nthose changes with the `gcloud beta run services replace` command.\nYou must ensure that you modify only the specified attributes.\n\n1. Download the configuration of your service into a file named\n `service.yaml` on local workspace:\n\n ```bash\n gcloud run services describe SERVICE --format export \u003e service.yaml\n ```\n\n Replace \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your\n Knative serving service.\n2. In your local file, update the `containerConcurrency` attribute:\n\n ```yaml\n apiVersion: serving.knative.dev/v1\n kind: Service\n metadata:\n name: SERVICE\n spec:\n template:\n spec:\n containerConcurrency: CONCURRENCY\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your Knative serving service\n - \u003cvar translate=\"no\"\u003eCONCURRENCY\u003c/var\u003e with the maximum number of concurrent requests per container instance. Specify `default` to clear the concurrency settings: `--concurrency default`.\n3. Replace the service with its new configuration using the following command:\n\n ```bash\n gcloud beta run services replace service.yaml\n ```"]]
