The CPU and memory limits that are defined for each Portal deployment
profile.
The tables in this topic also show which containers require license
entitlement. The sum of the CPU limits of the licensed containers, multiplied by the number of
replicas determine what you are charged. The formula is: <total licensed CPU limit> =
<total CPU limits of all licensed containers> * <number of replicas>
All Portal component deployment profiles have a
sync-backup
job pod that
completes tasks that are related to scheduled portal backups. The
sync-backup
job
pod does not have any licensed containers, and its CPU/memory requests and limits are the same for
all profiles.
Table 1. Portal job pods
resource and licensing requirements
Job Name |
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
<portal-instance-name>-sync-backup |
<portal-instance-name>-sync-backup-<jobuuid> |
sync-ptl-backup-schedule |
1m |
1m |
100Mi |
100Mi |
n1xc2.m8
Table 2. n1xc2.m8 profile resource and
licensing requirements
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
db |
db |
200m |
2000m |
3Gi |
8Gi |
6Gi |
1 |
|
db |
dbproxy |
100m |
1000m |
128Mi |
512Mi |
15Gi |
1 |
|
www |
web |
150m |
2000m |
1Gi |
5Gi |
8Gi |
1 |
Yes |
www |
admin |
200m |
2000m |
1Gi |
8Gi |
6Gi + 15Gi |
1 |
|
nginx |
nginx |
20m |
500m |
512Mi |
512Mi |
1Gi |
1 |
|
Table 3. n1xc2.m8 Containers for
optional features, resource and licensing requirements
Feature |
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
2DCDR |
db-remote |
tunnel |
75m |
150m |
160Mi |
256Mi |
1Gi |
1 |
|
www-remote |
tunnel |
75m |
150m |
160Mi |
256Mi |
1Gi |
1 |
|
tunnel |
server |
100m |
500m |
256Mi |
512Mi |
1Gi |
1 |
|
Note: For 2DCDR deployments, if the
remote site is deployed with a three replica profile, the
db-remote
and www-remote
pods have three replicas to match the
remote site.
n1xc4.m16
Table 4. n1xc4.m16 profile resource
and licensing requirements
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
db |
db |
500m |
3000m |
6Gi |
8Gi |
6Gi |
1 |
|
|
dbproxy |
450m |
1000m |
256Mi |
1Gi |
15Gi |
1 |
|
www |
web |
600m |
4000m |
3Gi |
8Gi |
8Gi |
1 |
Yes |
|
admin |
800m |
4000m |
3Gi |
8Gi |
6Gi + 15Gi |
1 |
|
nginx |
nginx |
20m |
500m |
512Mi |
512Mi |
1Gi |
1 |
|
Table 5. n1xc4.m16 Containers for
optional features, resource and licensing requirements
Feature |
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
2DCDR |
db-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
1 |
|
www-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
1 |
|
tunnel |
server |
100m |
500m |
256Mi |
512Mi |
1Gi |
1 |
|
Note: For 2DCDR deployments, if the
remote site is deployed with a three replica profile, the
db-remote
and www-remote
pods have three replicas to match the
remote site.
n1xc8.m16
Table 6. n1xc8.m16 profile resource
and licensing requirements
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
db |
db |
1300m |
5000m |
6Gi |
8Gi |
6Gi |
1 |
|
|
dbproxy |
1000m |
1000m |
256Mi |
1Gi |
15Gi |
1 |
|
www |
web |
1300m |
8000m |
3Gi |
8Gi |
8Gi |
1 |
Yes |
|
admin |
2300m |
4000m |
3Gi |
8Gi |
6Gi + 15Gi |
1 |
|
nginx |
nginx |
100m |
500m |
512Mi |
512Mi |
1Gi |
1 |
|
Table 7. n1xc8.m16 Containers for
optional features, resource and licensing requirements
Feature |
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
2DCDR |
db-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
1 |
|
www-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
1 |
|
tunnel |
server |
100m |
500m |
256Mi |
512Mi |
1Gi |
1 |
|
Note: For 2DCDR deployments, if the
remote site is deployed with a three replica profile, the
db-remote
and www-remote
pods have three replicas to match the
remote site.
n3xc3.m8
Table 8. n3xc3.m8 profile resource and
licensing requirements
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
db |
db |
400m |
2000m |
3Gi |
8Gi |
12Gi |
3 |
|
|
dbproxy |
150m |
1000m |
128Mi |
512Mi |
30Gi |
3 |
|
www |
web |
450m |
3000m |
1Gi |
5Gi |
12Gi |
3 |
Yes |
|
admin |
650m |
3000m |
1Gi |
8Gi |
12Gi + 30Gi |
3 |
|
nginx |
nginx |
20m |
500m |
512Mi |
512Mi |
1Gi |
3 |
|
Table 9. n3xc3.m8 Containers for
optional features, resource and licensing requirements
Feature |
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
2DCDR |
db-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
3 |
|
www-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
3 |
|
tunnel |
server |
100m |
500m |
256Mi |
512Mi |
1Gi |
3 |
|
Note: For 2DCDR deployments, if the
remote site is deployed with a one replica profile, the
db-remote
and www-remote
pods have one replica, to match the
remote site.
n3xc4.m8
Table 10. n3xc4.m8 profile resource and
licensing requirements
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
db |
db |
500m |
3000m |
3Gi |
8Gi |
12Gi |
3 |
|
|
dbproxy |
450m |
1000m |
128Mi |
512Mi |
30Gi |
3 |
|
www |
web |
600m |
4000m |
1Gi |
5Gi |
12Gi |
3 |
Yes |
|
admin |
800m |
4000m |
1Gi |
8Gi |
12Gi + 30Gi |
3 |
|
nginx |
nginx |
20m |
500m |
512Mi |
512Mi |
1Gi |
3 |
|
Table 11. n3xc4.m8 Containers for
optional features, resource and licensing requirements
Feature |
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
2DCDR |
db-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
3 |
|
www-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
3 |
|
tunnel |
server |
100m |
500m |
256Mi |
512Mi |
1Gi |
3 |
|
Note: For 2DCDR deployments, if the
remote site is deployed with a one replica profile, the
db-remote
and www-remote
pods have one replica, to match the
remote site.
n3xc8.m16
Table 12. n3xc8.m16 profile resource
and licensing requirements
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
db |
db |
1300m |
5000m |
6Gi |
8Gi |
6Gi |
3 |
|
|
dbproxy |
1000m |
1000m |
256Mi |
1Gi |
15Gi |
3 |
|
www |
web |
1300m |
8000m |
3Gi |
8Gi |
8Gi |
3 |
Yes |
|
admin |
2300m |
4000m |
3Gi |
8Gi |
6Gi + 15Gi |
3 |
|
nginx |
nginx |
100m |
500m |
512Mi |
512Mi |
1Gi |
3 |
|
Table 13. n3xc8.m16 Containers for
optional features, resource and licensing requirements
Feature |
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
PVC Size |
Number of replicas |
License entitlement required |
2DCDR |
db-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
3 |
|
www-remote |
tunnel |
75m |
500m |
160Mi |
256Mi |
1Gi |
3 |
|
tunnel |
server |
100m |
500m |
256Mi |
512Mi |
1Gi |
3 |
|
Note: For 2DCDR deployments, if the
remote site is deployed with a one replica profile, the
db-remote
and www-remote
pods have one replica, to match the
remote site.