4 Resource Utilization
The use of resources such as CPU and RAM by the OSO services are constrained to ensure that the CPU and RAM do not consume excess resources that could be used by other applications.
During the deployment of the services, each service gets an initial CPU and RAM allocation. Each service is allowed to consume the resources to a specified upper limit while it continues to run. The initial allocation limit and the upper limit are set to the same value for services where the resource consumption limit remains the same as the initial allocation or in a case where increasing the CPU or RAM limits underneath a running application can cause service disruption. The resource requests and limits are as follows:
Table 4-1 CPU and RAM Resource Requests and Limits
| Service | CPU Initial Request(m) | CPU Limit(m) | RAM Initial Request(Mi) | RAM Limit(Mi) | Instances |
|---|---|---|---|---|---|
| Prometheus | 2000 | 2000 | 4096 | 4096 | 2 |
| Prometheus AlertManager | 20 | 20 | 64 | 64 | 2 |
The overall observability services resource usage varies on each worker node. The observability services listed in the table are distributed evenly across all worker nodes in the Kubernetes cluster.