Size | CPU | Memory (GB) | Disk (GB) | AWS* | Azure* | Users | Groups | Managed Servers | Concurrent Builds (UI)* | Concurrent Builds (API)* | Blueprint Capacity (UI) |
|---|---|---|---|---|---|---|---|---|---|---|---|
Trial* | 2 | 4 | 40 | t3.medium | Standard_A2_v2 | - | - | 25-50 | 50 | 50 | 10 |
Small* | 2 | 8 | 40 | m5.large | Standard_D2a_v4 | 5000 | 300 | 20,000* | 100 | 200 | 25 |
Medium | 4 | 16 | 40 | m5.xlarge | Standard_D4a_v4 | 7500 | 500 | 40,000* | 250 | 500 | 50 |
Large | 8 | 32 | 40 | m5.2xlarge | Standard_D8a_v4 | 10,000 | 800 | 60,000* | 500 | 1000 | 75 |
Trial: Limited to 25 servers and burstable to 50
Small: Standard deployment size
Managed Servers: Max tested amount with 24 hour VM sync cycle. Can exceed if the sync cycle is increased. Additional Job Engine servers will increase capacity.
Concurrent Builds: Single order with X number of VMs
AWS / Azure: Instance Type listed is just an example and not the one you have to use
Disclaimer: The values below are not hard limits, nor are they maximum values. These are meant to give an idea of how to optimally size your environment based on your expected Managed Servers, Concurrent builds, and number of Blueprints. Many factors can contribute to performance and capacity including age and sizing of underlying virtualization hardware, storage, as well as other factors in the environment such as security and firewall measures and network speed/integrity.
Additional Details:
High Availability
HA is only recommended to scale horizontally
Trial/Small (Standalone)
1 server running all services
Medium (HA)
2 Database Servers
2 Web Servers
2 Job Engine Servers
Large (HA)
2 Database Servers
3 Web Servers
3 Job Engine Servers
0 Comments