Skip to content

Commit 1f912c9

Browse files
yousefi-msftyousefi-msft
committed
feedback from team
1 parent 1521a45 commit 1f912c9

File tree

2 files changed

+34
-33
lines changed

2 files changed

+34
-33
lines changed

‎articles/modeling-simulation-workbench/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,8 @@ landingContent:
8080
url: ./resources-troubleshoot.md
8181
- text: Known issues
8282
url: ./troubleshoot-known-issues.md
83+
- text: Limits and quotas
84+
url: ./limits-quotas.md
8385
- text: Business continuity
8486
url: ./disaster-recovery.md
8587
- text: Get support

‎articles/modeling-simulation-workbench/limits-quotas.md

Lines changed: 32 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -14,58 +14,57 @@ ms.date: 10/15/2024
1414

1515
The Modeling and Simulation Workbench has various quotas and limitations on deploying resources or configurations. Workbenches and chambers have overhead which might affect some of the available resource quotas. Those cases are called out in this article.
1616

17-
## About limits and quotas
18-
19-
The Modeling and Simulation Workbench resources appear in your user subscription, but are deployed into a Microsoft managed environment and subscription. Quotas applied to your own subscription don't apply to Modeling and Simulation Workbench.
17+
Resources, such as chambers and virtual machines, appear in your user subscription, but are deployed into a Microsoft managed environment and subscription. Quotas applied to your own subscription don't apply to Modeling and Simulation Workbench.
2018

2119
## Chambers
2220

23-
| Item | Quota or limit | Notes |
24-
|--------------------------------------|----------------|-----------------------------------------------------------------------------------------------|
25-
| Maximum chambers per workbench | 3 | |
26-
| Users per chamber | no limit | |
27-
| Supports parallel deployment? | No | Only one chamber can be deployed at any given time. |
28-
| Identity and Access Management (IAM) | User only | Chambers don't support Azure Groups. Only individual user assignments are supported. |
29-
| Deployment location | Same as workbench | All chambers and dependent resources (VMs, connectors) are deployed to the workbench's location, regardless of requested location. |
21+
| Item | Quota or limit | Notes |
22+
|--------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------|
23+
| Chambers per workbench | Limit 3 | |
24+
| Users per chamber | No limit | |
25+
| Supports parallel deployment? | No | Only one chamber can be deployed at any given time. |
26+
| Identity and Access Management (IAM) | Users only | Chambers don't support Azure Groups. Individual user role assignments only. |
27+
| Deployment location | Same as workbench | Chambers and dependent resources are deployed to the workbench's location, regardless of requested location. |
3028

3129
## Virtual machines
3230

3331
Virtual machines (VM) are limited by a different subscription quota than your customer quota. Requesting quota increases to your customer subscription doesn't affect your VM quota in Modeling and Simulation Workbench. Modeling and Simulation Workbench provides a select set of high-performance and general computing VMs. To learn about which offerings and families are available, see the [VM offerings](./concept-vm-offerings.md) guide. The following table lists the quota by family.
3432

3533
The table lists quota by virtual CPUs (vCPU), where each physical CPU is equivalent to two vCPUs. Consult the VM guide to determine how many vCPUs each VM has.
3634

37-
| Item | Quota or limit | Notes |
38-
|-------------------------------|--------------------|--------------------------------------------------------------------------------------|
39-
| D-series | 156 vCPUs | D-series support workbench infrastructure. Deploying more chambers reduces this limit. |
40-
| E-series | 256 vCPUs | |
41-
| F-series | 100 vCPUs | |
42-
| M-series | 128 vCPUs | |
43-
| Supports parallel deployment? | Yes | |
44-
| Deployment location | Same as workbench. | |
35+
vCPU quotas listed are initial default. More capacity can be requested.
36+
37+
| Item | Quota or limit | Notes |
38+
|-------------------------------|--------------------|--------------------------------------------------------------------------------------------------|
39+
| D-series | 156 vCPUs | D-series are used in workbench infrastructure. Creating more chambers reduces D-series quantity. |
40+
| E-series | 256 vCPUs | Initial quota, more can be requested. |
41+
| F-series | 100 vCPUs | Initial quota, more can be requested. |
42+
| M-series | 128 vCPUs | Initial quota, more can be requested. |
43+
| Supports parallel deployment? | Yes | Multiple VMs can be deployed simultaneously. |
44+
| Deployment location | Same as workbench. | |
4545

4646
## Storage
4747

48-
| Item | Quota or limit | Notes |
49-
|----------------------------------|------------------------------------------------------|-----------------------------------------------------------------------------|
50-
| Home volume quota | 200 GB | For entire volume, shared across all users. |
51-
| `datain` volume | 1 TB | |
52-
| `dataout` volume | 1 TB | |
53-
| File size limit on data pipeline | 100 GB per file | |
54-
| File name character set | alphanumeric, period (.), hyphen (-) | Any other character causes a pipeline failures and file are dropped. |
55-
| Chamber storage volumes | 4 TB minimum, increments by 4 TB up to 20 TB maximum | |
56-
| Shared storage volumes | 4 TB minimum, increments by 4 TB up to 20 TB maximum | |
48+
| Item | Quota or limit | Notes |
49+
|----------------------------------|--------------------------------------------|---------------------------------------------|
50+
| Home volume quota | 200-GB limit | For entire volume, shared across all users. |
51+
| `datain` volume | 1-TB limit | |
52+
| `dataout` volume | 1-TB limit | |
53+
| File size limit on data pipeline | 100-GB limit per file | |
54+
| Chamber storage volumes | 4 TB initial, 4-TB increments, 20-TB quota | More quota can be requested. |
55+
| Shared storage volumes | 4 TB initial, 4-TB increments, 20-TB quota | More quota can be requested. |
5756

5857
## Networking
5958

60-
| Item | Quota or limit | Notes |
61-
|------------------------------------------------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
62-
| Connectors per chamber | 1 | Only one connector per chamber, if multiple access methods are needed, the private network connector is recommended. |
63-
| Maximum number of allowlist entries in public IP connector | 200 | Upper limit on entries in the table. Subnets up to /24 are permitted and consecutive addresses should be combined to improve manageability. |
64-
| Maximum subnet mask for public connector | /24 | |
59+
| Item | Quota or limit | Notes |
60+
|----------------------------------------------------|----------------|----------------------------------------------------------------------|
61+
| Connectors per chamber | 1 | Limit one connector per chamber. |
62+
| Number of allowlist entries (public IP connector) | 200 | Max. limit on entries in the table. Subnets ranges can be specified. |
63+
| Maximum subnet mask (public IP connector) | /24 | |
6564

6665
## License service
6766

68-
* Only one license file can be uploaded to each license server at a time. Subsequent uploads overwrite the previously uploaded file.
67+
* Limit of one license file can be uploaded to each license server at a time. Subsequent uploads overwrite the current file.
6968

7069
## Related content
7170

0 commit comments

Comments
 (0)