Default sizes for microservices Containers
- Ashhad Alam
Adeptia Connect allows you to configure the CPU and memory for a microservice by setting the following parameters in the values.yaml file.
CPU and Memory limit - The maximum amount of CPU and the memory a microservice can consume.
CPU and Memory Request - The minimum amount of CPU and the memory required by a microservice.
Minimum Replicas - The minimum number of replicas (pods) of a microservice that will run by default.
Maximum Replicas - The maximum number of replicas (pods) to which a microservice can scale up.
This page lists all the microservices with their default CPU and memory sizes. It also mentions the minimum and maximum number of replicas each microservice can have.
Sl. No. | Service Name | Java opts | CPU Request | CPU Limit | Memory Request | Memory Limit | Minimum Replicas | Maximum Replicas |
|---|---|---|---|---|---|---|---|---|
1 | runtime | Xms1024M -Xmx4096M -Djdk.tls.useExtendedMasterSecret=false | 1000m | 2 CPU | 3 GB | 5 GB | 2 | 4 |
2 | rabbitmq | Xms1024M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 1 GB | 3 GB | 1 | 2 |
3 | event | Xms1024M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 1 GB | 3 GB | 1 | 2 |
4 | listener | Xms1024M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 1 GB | 3 GB | 1 | 1 |
5 | api-gateway | Xms512M -Xmx1024M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 512 MB | 2 GB | 1 | 2 |
6 | soap-api | Xms512M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 512 MB | 3 GB | 1 | 2 |
7 | rest-api | Xms512M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 512 MB | 3 GB | 1 | 2 |
8 | webapp-gateway | Xms512M -Xmx1024M -Djdk.tls.useExtendedMasterSecret=false | 200m | 1 CPU | 512 MB | 2 GB | 1 | 2 |
9 | portal | Xms512M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 512 MB | 3 GB | 1 | 2 |
10 | web-runner | Xms512M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 512 MB | 3 GB | 1 | 2 |
11 | license | Xms512M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 512 MB | 3 GB | 1 | 1 |
12 | archival-and-cleanup | Xms512M -Xmx2048M -Djdk.tls.useExtendedMasterSecret=false | 500m | 1 CPU | 512 MB | 3 GB | 1 | 2 |
13 | autoscaler | Not applicable | 200m | 1 CPU | 256 MB | 512 MB | 1 | 2 |
14 | ai-map | Not applicable | 500m | 1 CPU | 512 MB | 2 GB | 1 | 2 |
| Total requirement |
| 6900m = 6.9 CPU | 15 CPU | 10.75 GB | 38.5 GB |
|
|
| Recommended Capacity |
|
| 4 CPUs x 4 Cores (16 Cores) |
| 4 x 16 GB (64 GB) |
|
|
You can set the maximum number of replicas for a microservice only after enabling its autoscaling property by setting the value for enabled to true in the values.yaml file. By default, autoscaling is disabled. After enabling the autoscaling, you can set the value for maxReplicas variable based on your requirement. Given below is an example showing autoscaling settings for the webrunner microservice.
Important
The maximum number of replicas for the listener and license microservices cannot be more than what has been specified in the table (Maximum Replicas).
Though Adeptia recommends the maximum number of replicas for each microservice, it may vary (except for the listener and license microservices) based on your requirement.