Capacity planning recommendations for API and management portal machines
Applies To: Windows Azure Pack
In capacity planning for Windows Azure Pack, you should focus on each of the components individually. For more information about each component, see Windows Azure Pack components. For example, the management portal for tenants and the Windows Azure Pack Tenant API have significantly higher load requirements than the management portal for administrators and the Windows Azure Pack Admin API.
Suggested minimum machine configuration
To support up to 600 concurrent users on the management portal for tenants, at an average of 80% CPU usage, we recommend that you use the following settings.
Component |
Instances |
RAM |
Virtual machine processors |
Management portal for tenants |
1 |
4 GB |
2 |
Tenant API |
1 |
4 GB |
2 |
Highly available machine configuration
To support up to 1200 concurrent users on the management portal for tenants, at an average of 80% CPU usage, we recommend that you use the following settings.
Component |
Instances |
RAM |
Virtual machine processors |
Management portal for tenants |
2 |
4 GB |
2 |
Tenant API |
1 |
4 GB |
2 |
As load requirements increase, you can do either of the following:
Scale out by installing additional instances of the management portal for tenants and Tenant API. Performance improves linearly with additional instances.
Scale up existing management portal for tenants and instances of the Tenant API with additional CPU cores or memory.
You should also periodically evaluate the performance of the management portal for administrators and Admin API and scale these up or out as necessary.
For capacity planning information on resource providers, see the Capacity planning test environmenttopic.