The CPU and memory limits that are defined for each Analytics 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 Analytics component deployment profiles have an osinit job pod that is run
on startup and completes tasks that are related to initialization. The osinit job
pod does not have any licensed containers, and its CPU/memory requests and limits are the same for
all profiles.
You can choose different storage types with the
three replica profiles, and so the pods
deployed differ depending on the storage option chosen:
OpenSearch storage type. If you choose storage
type
shared, then your analytics deployment has 1 storage pod, called
storage. If you choose storage type
dedicated, then your analytics
deployment has 2 storage pods, called
storage and
storage-os-master. The tables for the
three replica profiles indicate in
parentheses after the pod name which storage type the pod applies to, for example
storage
(shared)
.
Table 1. Analytics job
pods
| Job Name |
Pod Name |
Container Name |
CPU Requests |
CPU limits |
Memory Requests |
Memory Limits |
| <analytics-instance-name>-osinit |
<analytics-instance-name>-osinit-<podid> |
osinit |
8 m |
100 m |
128 Mi |
256 Mi |
The PVC sizes that are specified in the tables are the defaults. Review the planning and
installation documentation to decide on the sizes to allocate for your deployment: Planning your analytics deployment.
n1xc2.m16
Table 2. n1xc2.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 |
| mtls-gw |
mtls-gw |
100 m |
1000 m |
128 Mi |
256 Mi |
|
1 |
|
| ingestion |
ingestion |
275 m |
1200 m |
8 Gi |
8 Gi |
50 Gi |
1 |
Yes |
| storage |
storage |
225 m |
800 m |
6 Gi |
6 Gi |
50 Gi |
1 |
Yes |
| director |
director |
50 m |
200 m |
128 Mi |
512 Mi |
|
1 |
|
n1xc4.m32
Table 3. n1xc4.m32 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 |
| mtls-gw |
mtls-gw |
100 m |
1000 m |
256 Mi |
512 Mi |
|
1 |
|
| ingestion |
ingestion |
1300 m |
2200 m |
8 Gi |
8 Gi |
50 Gi |
1 |
Yes |
| storage |
storage |
1200 m |
1800 m |
22 Gi |
22 Gi |
50 Gi |
1 |
Yes |
| director |
director |
50 m |
200 m |
256 Mi |
512 Mi |
|
1 |
|
n1xc6.m48
Table 4. n1xc6.m48 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 |
| mtls-gw |
mtls-gw |
100 m |
1000 m |
256 Mi |
512 Mi |
|
1 |
|
| ingestion |
ingestion |
2000 m |
3200 m |
8 Gi |
8 Gi |
50 Gi |
1 |
Yes |
| storage |
storage |
1800 m |
2800 m |
37 Gi |
37 Gi |
50 Gi |
1 |
Yes |
| director |
director |
50 m |
200 m |
256 Mi |
512 Mi |
|
1 |
|
n3xc4.m16
Table 5. n3xc4.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 |
| mtls-gw |
mtls-gw |
100 m |
1000 m |
128 Mi |
256 Mi |
|
3 |
|
| ingestion |
ingestion |
1300 m |
2200 m |
8 Gi |
8 Gi |
50 Gi |
3 |
Yes |
| director |
director |
50 m |
200 m |
128 Mi |
256 Mi |
|
3 |
|
| storage (shared) |
storage |
1200 m |
1800 m |
6 Gi |
6 Gi |
50 Gi |
3 |
Yes |
| storage (dedicated) |
storage |
800 m |
1000 m |
4 Gi |
4 Gi |
50 Gi |
3 |
Yes |
| storage-os-master (dedicated) |
storage-os-master |
400 m |
800 m |
2 Gi |
2 Gi |
5 Gi |
3 |
Yes |
n3xc4.m32
Table 6. n3xc4.m32 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 |
| mtls-gw |
mtls-gw |
100 m |
1000 m |
256 Mi |
512 Mi |
|
3 |
|
| ingestion |
ingestion |
1300 m |
2200 m |
8 Gi |
8 Gi |
50 Gi |
3 |
Yes |
| director |
director |
50 m |
200 m |
256 Mi |
512 Mi |
|
3 |
|
| storage (shared) |
storage |
1200 m |
1800 m |
22 Gi |
22 Gi |
50 Gi |
3 |
Yes |
| storage (dedicated) |
storage |
800 m |
1000 m |
20 Gi |
20 Gi |
50 Gi |
3 |
Yes |
| storage-os-master (dedicated) |
storage-os-master |
400 m |
800 m |
2 Gi |
2 Gi |
5 Gi |
3 |
Yes |
n3xc6.m48
Table 7. n3xc6.m48 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 |
| mtls-gw |
mtls-gw |
100 m |
1000 m |
256 Mi |
512 Mi |
|
3 |
|
| ingestion |
ingestion |
2000 m |
3200 m |
8 Gi |
8 Gi |
50 Gi |
3 |
Yes |
| director |
director |
50 m |
200 m |
256 Mi |
512 Mi |
|
3 |
|
| storage (shared) |
storage |
1800 m |
2800 m |
37 Gi |
37 Gi |
50 Gi |
3 |
Yes |
| storage (dedicated) |
storage |
1400 m |
1800 m |
35 Gi |
35 Gi |
50 Gi |
3 |
Yes |
| storage-os-master (dedicated) |
storage-os-master |
400 m |
1000 m |
2 Gi |
2 Gi |
5 Gi |
3 |
Yes |
n3xc8.m64
Table 8. n3xc8.m64 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 |
| mtls-gw |
mtls-gw |
100 m |
1000 m |
256 Mi |
512 Mi |
|
3 |
|
| ingestion |
ingestion |
3000 m |
4200 m |
8 Gi |
8 Gi |
50 Gi |
3 |
Yes |
| director |
director |
50 m |
200 m |
256 Mi |
512 Mi |
|
3 |
|
| storage (shared) |
storage |
2800 m |
3800 m |
53 Gi |
53 Gi |
50 Gi |
3 |
Yes |
| storage (dedicated) |
storage |
2400 m |
2800 m |
49 Gi |
49 Gi |
50 Gi |
3 |
Yes |
| storage-os-master (dedicated) |
storage-os-master (dedicated) |
400 m |
1000 m |
4 Gi |
4 Gi |
5 Gi |
3 |
Yes |