Quotas

This document describes the quota limits for Google Cloud Functions.

Quotas for Google Cloud 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 Functions API and/or the rate at which resources can be used. You can think of rate quotas as "resources over time."

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

Resource Limits

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

Time Limits

Quota Description Limit Can be increased
Max function duration The maximum amount of time a function can run before it's forcibly terminated 540 seconds No
Max build time The maximum time allowed for all builds. Function builds happen at deploy time. 200 minutes per day No

Rate Limits

Quota Description Limit Can be increased
Function invocations per second The number of function invocations in a second. If exceeded, all functions will be paused until the next quota period 1,000,000 per 100 seconds Yes
GHz-seconds per second The number of GHz-seconds consumed per second. For example a function with 256MB memory, which corresponds to 400MHz CPU (see pricing for compute time), will consume 0.4 GHz-seconds if is running for 1 second. The time of a running function is rounded up to a multiple of 100ms.
Note: there is an additional quota of 10M GHz-seconds per day, which can also be increased on request
100,000 per 100 seconds Yes
API calls (READ) Calls to describe or list functions via the Cloud Functions API 1000 per 100 seconds Yes
API calls (WRITE) Calls to deploy or delete functions via the Cloud Functions API 80 per 100 seconds Yes
API calls (INVOKE) Calls to the "call" API 16 per 100 seconds Yes
Inbound Socket Data Data transfer into all running functions. For example, data used by a function downloading a file from Google Cloud Storage would count towards this limit. 10 GB per 100 seconds Yes
Outbound Socket Data Data transfer out of all running functions, excluding HTTP response data 10 GB per 100 seconds Yes
Socket connections The attempts to establish a new outbound socket connection 4,000 per 100 seconds Yes
DNS resolutions The attempts to resolve a domain name in DNS 40,000 per 100 seconds Yes
Max concurrent invocations for a background function The maximum concurrent invocations of a single function that is not triggered by HTTP requests
Example: if handling each event takes 100 seconds, the invocation rate will be limited to 10 per second on average
1,000 No
Max invocation rate for a background function The maximum rate of events being handled by a single function that is not triggered by HTTP requests
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
Max concurrent event data size for a background function The maximum total size of incoming events to concurrent invocations of a single function that is not triggered by HTTP requests
Example: if events are of size 1MB and processing them takes 10 seconds, the average rate will be 1 event per second, because the 11th event will not be processed until processing one of the first 10 events finishes
10MB No
Max throughput of incoming events for a background function The maximum throughput of incoming events to a single function that is not triggered by HTTP requests
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

Scalability

Cloud Functions invoked by HTTP scale quickly to the desired invocation rate, while background functions scale more gradually. In the latter case, scalability depends on the duration of functions, and longer functions will scale slightly slower.

For any function type, the maximum scalability is limited by the Rate Limits described above. Note that some of the limits apply to each individual function and can be dealt with by deploying multiple functions, while others apply to the entire project.

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 will not work until then. By default, a function returns an HTTP 500 error code when a required resource is over quota and the function cannot execute.

To increase quotas above the defaults listed in this document, submit a request using the Cloud Functions Quotas Page.

Send feedback about...

Cloud Functions Documentation