You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/batch/batch-quota-limit.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.workload: big-compute
13
13
ms.tgt_pltfrm: na
14
14
ms.devlang: na
15
15
ms.topic: article
16
-
ms.date: 05/13/2019
16
+
ms.date: 05/28/2019
17
17
ms.author: lahugh
18
18
ms.custom: seodec18
19
19
@@ -29,19 +29,22 @@ You can run multiple Batch workloads in a single Batch account, or distribute yo
29
29
30
30
If you plan to run production workloads in Batch, you may need to increase one or more of the quotas above the default. If you want to raise a quota, you can open an online [customer support request](#increase-a-quota) at no charge.
31
31
32
-
> [!NOTE]
33
-
> A quota is a credit limit, not a capacity guarantee. If you have large-scale capacity needs, please contact Azure support.
If you created a Batch account with pool allocation mode set to **user subscription**, quotas are applied differently. In this mode, Batch VMs and other resources are created directly in your subscription when a pool is created. The Azure Batch cores quotas do not apply to an account created in this mode. Instead, the quotas in your subscription for regional compute cores and other resources are applied. Learn more about these quotas in [Azure subscription and service limits, quotas, and constraints](../azure-subscription-service-limits.md).
42
43
43
44
## Pool size limits
44
45
46
+
Pool size limits are set by the Batch service. Unlike [resource quotas](#resource-quotas), these values cannot be changed. Only pools with inter-node communication and custom images have restrictions different from the standard quota.
47
+
45
48
|**Resource**|**Maximum Limit**|
46
49
| --- | --- |
47
50
|**Compute nodes in [inter-node communication enabled pool](batch-mpi.md)**||
@@ -55,6 +58,8 @@ If you created a Batch account with pool allocation mode set to **user subscript
55
58
56
59
## Other limits
57
60
61
+
Additional limits set by the Batch service. Unlike [resource quotas](#resource-quotas), these values cannot be changed.
62
+
58
63
|**Resource**|**Maximum Limit**|
59
64
| --- | --- |
60
65
|[Concurrent tasks](batch-parallel-node-tasks.md) per compute node | 4 x number of node cores |
| Azure Batch accounts per region per subscription | 1-3 |50 |
16
-
| Dedicated cores per Batch account |10-100|N/A<sup>1</sup>|
17
-
| Low-priority cores per Batch account | 10-100 |N/A<sup>2</sup>|
18
-
| Active jobs and job schedules<sup>3</sup> per Batch account | 100-300 | 1,000<sup>4</sup> |
19
-
| Pools per Batch account | 20-100 | 500<sup>4</sup> |
16
+
| Dedicated cores per Batch account |90-900|Contact support|
17
+
| Low-priority cores per Batch account | 10-100 |Contact support|
18
+
|**[Active](https://docs.microsoft.com/rest/api/batchservice/job/get#jobstate)** jobs and job schedules per Batch account (**completed** jobs have no limit) | 100-300 | 1,000<sup>1</sup> |
19
+
| Pools per Batch account | 20-100 | 500<sup>1</sup> |
20
20
21
21
> [!NOTE]
22
-
> Default limits vary depending on the type of subscription you use to create a Batch account. Cores quotas shown are for Batch accounts in Batch service mode. [View the quotas in your Batch account](../articles/batch/batch-quota-limit.md#view-batch-quotas).
22
+
> Default limits vary depending on the type of subscription you use to create a Batch account. Cores quotas shown are for Batch accounts in Batch service mode. [View the quotas in your Batch account](../articles/batch/batch-quota-limit.md#view-batch-quotas).
23
23
24
-
<sup>1</sup>The number of dedicated cores per Batch account can be increased, but the maximum number is unspecified. To discuss increase options, contact Azure Support.
25
-
26
-
<sup>2</sup>The number of low-priority cores per Batch account can be increased, but the maximum number is unspecified. To discuss increase options, contact Azure Support.
27
-
28
-
<sup>3</sup>Completed jobs and job schedules aren't limited.
29
-
30
-
<sup>4</sup>To request an increase beyond this limit, contact Azure Support.
24
+
<sup>1</sup>To request an increase beyond this limit, contact Azure Support.
0 commit comments