Compute Requirements in Customer-Controlled Clusters
The term Allocatable CPU refers to the CPU capacity that Kubernetes clusters can provide to pods used for Solace Cloud, after accounting for system reservations. For example, an r5.xlarge instance in AWS has 4000 mCore of total CPU capacity, but approximately 3500 mCore is allocatable to pods (with the remainder reserved for system daemons and the operating system). It is important to account for this difference when planning the capacity for a Kubernetes cluster.
The tables below provide the compute resource requirements for:
Note that standalone event broker services are not available by default. Contact Solace for more information.
Compute Resources for High Availability Event Broker Services
The CPU Request and CPU Limit numbers in the table below include a 200 mCore requirement per monitoring agent. Each HA event broker service has three monitoring agents, one per broker that composes the service (primary, backup, monitoring).
| Service Class | Pod Type (HA Role) |
CPU Request (mCore) |
Total CPU Request (mCore) |
CPU Limit (mCore) |
Total CPU Limit (mCore) |
|---|---|---|---|---|---|
|
Enterprise 250 |
Primary Messaging |
1,250 |
2800 |
2,200 |
5,600 |
|
Backup Messaging |
1,250 |
2,200 |
|||
|
Monitoring |
300 |
1,200 |
|||
|
Enterprise 1K |
Primary Messaging |
1,250 |
2800 |
2,200 |
5,600 |
|
Backup Messaging |
1,250 |
2,200 |
|||
|
Monitoring |
300 |
1,200 |
|||
|
Enterprise 5K |
Primary Messaging |
3,200 |
6,700 |
4,200 |
9,600 |
|
Backup Messaging |
3,200 |
4,200 |
|||
|
Monitoring |
300 |
1,200 |
|||
|
Enterprise 10K |
Primary Messaging |
3,200 |
6,700 |
4,200 |
9,600 |
|
Backup Messaging |
3,200 |
4,200 |
|||
|
Monitoring |
300 |
1,200 |
|||
|
Enterprise 50K |
Primary Messaging |
7,200 |
14,700 |
8,200 |
17,600 |
|
Backup Messaging |
7,200 |
8,200 |
|||
|
Monitoring |
300 |
1,200 |
|||
|
Enterprise 100K |
Primary Messaging |
7,200 |
14,700 |
8,200 |
17,600 |
|
Backup Messaging |
7,200 |
8,200 |
|||
|
Monitoring |
300 |
1,200 |
Compute Resources for Enterprise-100 Standalone and Standalone Event Broker Services
The CPU Request and CPU Limit numbers in the table below include a 200 mCore requirement for the monitoring agent that is included with the standalone event broker service.
| Service Class | CPU Request (mCore) |
CPU Limit (mCore) |
|---|---|---|
|
Enterprise-100 Standalone |
1,250 |
2,200 |
|
Enterprise 250 Standalone |
1,250 |
2,200 |
|
Enterprise 1K Standalone |
1,250 |
2,200 |
|
Enterprise 5K Standalone |
3,200 |
4,200 |
|
Enterprise 10K Standalone |
3,200 |
4,200 |
|
Enterprise 50K Standalone |
7,200 |
8,200 |
|
Enterprise 100K Standalone |
7,200 |
8,200 |