Quotas (1st gen)

This document describes the quota limits for Cloud Run functions.

Quotas for Cloud Run functions encompass 3 areas:

  • Resource Limits

    These affect the total amount of resources your functions can consume.

  • Time Limits

    These affect how long things can run.

  • Rate Limits

    These affect the rate at which you can call the Cloud Run functions API to manage your functions.

The different types of limits are described in more detail below.

Resource Limits

Resource limits affect the total amount of resources your functions can consume. The regional scope is per project, and each project maintains its own limits.

Quota Description Limit Can be increased Scope
Number of functions The total number of functions that can be deployed per region 1,000 No per region
Max deployment size The maximum size of a single function deployment 100MB (compressed) for sources.
500MB (uncompressed) for sources plus modules.
No per function
Max uncompressed HTTP request size Data sent to HTTP Functions in an HTTP request 10MB No per invocation
Max uncompressed HTTP response size Data sent from HTTP functions in an HTTP response 10MB No per invocation
Max event size for event-driven functions Data sent in events to background functions 10MB No per event
Max function memory Amount of memory each function instance can use 8GiB No per function

Time Limits

Quota Description Limit Can be increased Scope
Max function duration The maximum amount of time a function can run before being forcibly terminated 540 seconds No per invocation

Rate Limits

Quota Description Limit Can be increased Scope
API calls (READ) Calls to describe or list functions using the Cloud Run functions API 5000 per 100 seconds Yes per project
API calls (WRITE) Calls to deploy or delete functions using the Cloud Run functions API 80 per 100 seconds No 1 per project
API calls (CALL) Calls to the "call" API 16 per 100 seconds No 2 per project

Scalability

Cloud Run functions invoked by HTTP scale up quickly to handle incoming traffic, while background functions scale more gradually. A function's ability to scale up is dictated by a few factors, including:

  • 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).
  • The amount of time it takes for a function to initialize on

  • Your configuration as defined by minimum instances and maximum instances.

Quota Description Limit Can be increased Scope
Max invocation rate The maximum rate of events being handled by a single function
Example: if handling an event takes 100ms, the invocation rate will be limited to 1000 per second even if only 100 requests, on average, are handled in parallel
1000 per second No per function
Max throughput of incoming events The maximum throughput of incoming events to a single function
Example: if events are of size 1MB, then the invocation rate can be maximum 10 per second, even if functions finish within 100ms
10MB per second No per function

When you reach a quota limit

When a function consumes all of an allocated resource, the resource becomes unavailable until the quota is refreshed or increased. This may mean that your function and all other functions in the same project won't work until then. A function returns an HTTP 500 error code when one of the resources is over quota and the function cannot execute.

To increase quotas above the defaults listed here, go to the Cloud Run functions Quotas Page, 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.