This document lists the quotas and system limits that apply to Batch.
- Quotas specify the amount of a countable, shared resource that you can use. Quotas are defined by Google Cloud services such as Batch.
- System limits are fixed values that cannot be changed.
Batch jobs run on Compute Engine resources, so Batch is also subject to Compute Engine quotas and limits. If your Batch job also uses other Google Cloud services, then it is subject to the quotas for those services too. Attempts to exceed a quota or limit return an error. For more information, see Work with quotas.
In addition to the quotas and limits from other Google Cloud services, Batch has the following quotas and limits, which cannot be changed.
Request quotas
The following limits apply to Batch requests. These limits appear as quotas–for example, in the Google Cloud console–however, they can not be increased.
| Limit | Value |
|---|---|
| Agent requests per minute per region | 30,000 |
| Mutation requests per minute per region | 6,000 |
| Read requests per minute per region | 15,000 |
Job limits
The following limits apply to Batch jobs.
| Limit | Value |
|---|---|
| Tasks per task group | 100,000 |
| Parallel tasks per job | 5,000 |
| Concurrent VMs per single-zone job* | 2,000 |
| Concurrent VMs per multi-zone job* | 4,000 |
| Run time before automatic failure | 14 days |
| Size of the job definition† | 1 MB |
* The terms single-zone job and multi-zone job here refer to the number of zones allowed for a job's VMs, which might be different than the zones for a job's location. For more information, see Batch locations.
† For example, roughly the size of the REST request to the
jobs.create method
or gcloud CLI --config file.
You can work around this limit by the dividing the tasks across multiple
jobs—for example, learn how to
schedule dependent jobs
(Preview).