[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-22。"],[[["\u003cp\u003eCloud Run functions have various quota limits spanning resource, time, rate, and networking categories, which define the operational boundaries for these functions.\u003c/p\u003e\n"],["\u003cp\u003eResource limits, such as the number of functions, deployment size, memory, and CPU, constrain the total resources a project's functions can use, with some differences between 1st and 2nd generation functions.\u003c/p\u003e\n"],["\u003cp\u003eTime limits, such as the maximum function duration, dictate how long a function can run before being forcibly terminated, with different limits for HTTP and event-driven functions in 2nd generation.\u003c/p\u003e\n"],["\u003cp\u003eRate limits regulate the frequency of API calls for managing Cloud Run functions, with different limits for read, write, and call operations, and while write and call API quotas cannot be increased, it is possible for 1st gen to increase the READ quota.\u003c/p\u003e\n"],["\u003cp\u003eNetworking limits, including outbound connections, DNS resolutions, and data transfer rates, set the parameters for how Cloud Run functions can interact with external networks, and they vary between 1st and 2nd generation functions.\u003c/p\u003e\n"]]],[],null,["# Quotas\n======\n\nThis document describes the quota limits for Cloud Run functions.\n| To increase quotas above the defaults listed here, go to the [Cloud Run functions Quotas Page](https://console.cloud.google.com/iam-admin/quotas?service=cloudfunctions.googleapis.com&usage=ALL&project=_), select the quotas you want to modify, click **Edit quotas**, supply your user information if prompted, and enter the new quota limit for each quota you selected.\n\nQuotas for Cloud Run functions encompass 4 areas:\n\n- Resource Limits\n\n These affect the total amount of resources your functions can consume.\n- Time Limits\n\n These affect how long things can run.\n- Rate Limits\n\n These affect the rate at which you can call the Cloud Run functions API\n to manage your functions.\n- Networking Limits\n\n These affect outbound connection and instance limits.\n\nThe different types of limits are described in more detail below.\nDifferences between limits for Cloud Run functions (1st gen) and\nCloud Run functions (2nd gen) are noted where applicable.\n\nResource Limits\n---------------\n\nResource limits affect the total amount of resources your functions can consume.\nThe regional scope is per project, and each project maintains its own limits.\n\n| **Note:** If you are triggering a function using Pub/Sub, either via [event-driven functions](/functions/docs/writing#event-driven_functions) or as the [HTTP target](/functions/docs/writing#http_functions) of a push subscription, be aware that Pub/Sub messages are base64-encoded. A 10 MB Pub/Sub message - the [maximum size](/pubsub/quotas) supported - is larger than 10 MB once it is encoded, and can thus exceed the Cloud Run functions max size limit.\n\nTime Limits\n-----------\n\nRate Limits\n-----------\n\n| ^1^ You cannot increase the WRITE quota. Insufficient quota generally occurs due to one of the following:\n|\n| - Use of a CI/CD system that deploys many functions concurrently or sequentially at a high rate.\n| - Use of the Firebase CLI to deploy multiple functions simultaneously.\n|\n| In each case, you can avoid hitting this quota by changing the rate of\n| deployments. For example, if you are deploying using the Firebase CLI,\n| [use\n| the `--only` flag to deploy individual functions](https://firebase.google.com/docs/cli/#deploy_specific_functions).\n| ^2^ The CALL API only applies to Cloud Run functions (1st gen). You cannot increase the CALL quota. Insufficient quota generally occurs if you mistakenly use this API to invoke your functions in production. Please keep in mind that this API is meant for testing with the Google Cloud console or [`gcloud functions call`](//cloud.google.com/sdk/gcloud/reference/functions/call) CLI, and it cannot handle heavy traffic.\n\nNetworking limits\n-----------------\n\nFor information about Cloud Run functions (2nd gen) networking request and\nbandwidth limits, see [Networking limits](https://cloud.google.com/run/quotas#networking_limits).\n\nThe following networking limits apply to Cloud Run functions (1st gen):\n\n- Outbound connections per second per instance: 500 (cannot be increased)\n- Outbound DNS resolutions per second per instance: 100 (cannot be increased)\n- Maximum packets per second per instance: 80,000\n- Maximum bits per second per instance: 100,000,000\n\nScalability\n-----------\n\nCloud Run functions invoked by HTTP scale up quickly to handle incoming traffic,\nwhile background functions scale more gradually. A function's ability to scale\nup is dictated by a few factors, including:\n\n- The amount of time it takes for a function's execution to complete (short-running functions can generally scale up to handle more concurrent requests).\n- The amount of time it takes for a function to initialize on [cold start](/functions/docs/bestpractices/tips#use_dependencies_wisely).\n- Your function's error rate.\n- Transient factors, such as regional load and data center capacity.\n\n- Your configuration as defined by\n [minimum instances](/functions/docs/configuring/min-instances),\n [maximum instances](/functions/docs/configuring/max-instances), and\n [concurrency](/functions/docs/configuring/concurrency) (concurrency is 2nd gen\n only).\n\n[Background functions](/functions/docs/writing/background) have additional limits, as explained below. These limits do not apply to 1st gen [HTTP\nfunctions](/functions/docs/writing/http). The default [maximum instances limit](/functions/docs/configuring/max-instances) for 2nd gen HTTP functions is 100 and can be increased to 1,000. There is no default maximum instances limit for 1st gen HTTP functions. To avoid unbounded scaling events with 1st gen HTTP functions, we recommend [setting a limit](/functions/docs/configuring/max-instances#setting_maximum_instances_limits), for example, 3000.\n\n\u003cbr /\u003e\n\n### Additional quotas for background functions\n\nWhen you reach a quota limit\n----------------------------\n\nWhen a function consumes all of an allocated resource, the resource becomes\nunavailable until the quota is refreshed or increased. This may mean that your\nfunction and all other functions in the same project will not work until then.\nA function returns an HTTP 500 error code when one of the resources is\nover quota and the function cannot execute.\n\nTo increase quotas above the defaults listed here, go to the\n[Cloud Run functions Quotas page](https://console.cloud.google.com/iam-admin/quotas?service=cloudfunctions.googleapis.com&usage=ALL&project=_), select the quotas you want to modify, click\n**Edit quotas**, supply your user information if prompted, and enter the new\nquota limit for each quota you selected."]]
