Depending on the size of the environment, combining certain services reduces the total number of management servers required for the ePO - On-prem environment.
Depending on the size of your environment, running multiple services on the same physical server require increased CPU, RAM, disk, and network resources.
Use this table as a starting point. Your calculations will depend on your environment.
Total node count | Services being added | Size |
|---|---|---|
< 10,000 | ePO - On-prem + DXL Broker | 6 cores, 16-GB RAM, 350-GB disk |
< 10,000 | ePO - On-prem + DXL Broker + SQL | 10 cores, 24-GB RAM, 1.5-TB disk |
10,000–25,000 | ePO - On-prem + DXL Broker | Not recommended |
10,000–25,000 | Agent Handler + DXL Broker | 8 cores, 16-GB RAM, 200-GB disk |
25,000–75,000 | ePO - On-prem + DXL Broker | Not recommended |
25,000–75,000 | Agent Handler + DXL Broker | 8 cores, 16-GB RAM, 200-GB disk |
75,000–150,000 | Agent Handler + DXL Broker | 8 cores, 16-GB RAM, 200-GB disk |
150,000 + | Agent Handler + DXL Broker | 8 cores, 16-GB RAM, 200-GB disk |
Other | SuperAgent + DXL Broker < 10,000 systems per server | 8 cores, 16-GB RAM, 120-GB disk |
When sharing SQL resources with another service, you must configure SQL Server to only use the resources it would be allocated if run as a separate server. Otherwise, the SQL Server will consume all available system memory and CPU capacity for itself.
For large environments with 75,000 or more systems, don't share resources on the ePO - On-prem server to maximize the performance of the ePO - On-prem console.
Combining DXL and repository resources, such as a SuperAgent, lowers the total number of systems that can be served by the shared resource. Each service requires many network connections.