Batch is available in the following regions. For more information about regions and zones, see Geography and regions.
Only the following regions can be used for a job's location, which is the region
that you are required to specify when creating a job. A job's location is used
for storing job metadata and is the default location used for creating the
Compute Engine resources that the job runs on. Optionally, if you specify the
allowed locations for a job's Compute Engine resources (allowedLocations[] field),
then the job is only allowed to run in the specified locations.
To identify an existing job's location and the allowed locations for its VMs, view the details of a job.
Regions
The following table lists the regions in the Americas where Batch is available.
| Region description | Region name | Details |
|---|---|---|
| Montréal | northamerica-northeast1 |
|
| Toronto | northamerica-northeast2 |
|
| São Paulo | southamerica-east1 |
|
| Santiago | southamerica-west1 |
|
| Iowa | us-central1 |
|
| South Carolina | us-east1 |
|
| Northern Virginia | us-east4 |
|
| Columbus | us-east5 |
|
| Dallas | us-south1 |
|
| Oregon | us-west1 |
|
| Los Angeles | us-west2 |
|
| Salt Lake City | us-west3 |
|
| Las Vegas | us-west4 |
The following table lists the regions in Europe and the Middle East where Batch is available.
| Region description | Region name | Details |
|---|---|---|
| Warsaw | europe-central2 |
|
| Finland | europe-north1 |
|
| Madrid | europe-southwest1 |
|
| Belgium | europe-west1 |
|
| London | europe-west2 |
|
| Frankfurt | europe-west3 |
|
| Netherlands | europe-west4 |
|
| Zürich | europe-west6 |
|
| Milan | europe-west8 |
|
| Paris | europe-west9 |
|
| Berlin | europe-west10 |
|
| Turin | europe-west12 |
|
| Doha | me-central1 |
|
| Dammam | me-central2 |
|
| Tel Aviv | me-west1 |
The following table lists the regions in Asia Pacific where Batch is available.
| Region description | Region name | Details |
|---|---|---|
| Taiwan | asia-east1 |
|
| Hong Kong | asia-east2 |
|
| Tokyo | asia-northeast1 |
|
| Osaka | asia-northeast2 |
|
| Seoul | asia-northeast3 |
|
| Mumbai | asia-south1 |
|
| Delhi | asia-south2 |
|
| Singapore | asia-southeast1 |
|
| Jakarta | asia-southeast2 |
|
| Sydney | australia-southeast1 |
|
| Melbourne | australia-southeast2 |
Recommended zones to obtain GPUs from Dynamic Workload Scheduler
When you create and run a job that uses GPUs and use calendar-mode reservations or Flex-start VMs, which both use Dynamic Workload Scheduler, we recommend that you use the following zones. These recommended zones have dedicated capacity for Dynamic Workload Scheduler, so using them increases the likelihood that your requests for GPU machine type from Dynamic Workload Scheduler are approved.
| GPU machine series | Recommended zones for Dynamic Workload Scheduler capacity | Details |
|---|---|---|
| A4 | asia-southeast1-b (Singapore) |
|
us-central1-b (Iowa) |
|
|
us-south1-b (Dallas) |
|
|
| A3 Ultra | asia-south1-b (Mumbai) |
|
asia-south2-c (Delhi) |
||
europe-west1-b (Belgium) |
|
|
europe-west4-a (Netherlands) |
|
|
us-central1-b (Iowa) |
|
|
us-east4-b (Northern Virginia) |
||
us-south1-b (Dallas) |
|
|
| A3 Mega | europe-west1-c (Belgium) |
|
europe-west4-b (Netherlands) |
|
|
europe-west4-c (Netherlands) |
|
|
us-central1-a (Iowa) |
|
|
us-central1-b (Iowa) |
|
|
us-central1-c (Iowa) |
|
|
us-east4-b (Northern Virginia) |
||
| A3 High | asia-east1-c (Taiwan) |
|
europe-west1-b (Belgium) |
|
|
us-central1-a (Iowa) |
|
|
us-central1-b (Iowa) |
|