Analytics component deployment profile limits

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.

Note: The sizing guidance in this topic is designed for analytics workloads. However, one AnalyticsCluster resource can also act as the backend for Federated API Management and the Developer Portal. Running these additional workloads on the same cluster reduces the capacity available for analytics. If your cluster supports Federated API Management and the Developer Portal along with analytics, plan for extra resources. For example, choose a larger deployment profile and allocate more disk space. For more information about Federated API Management and Developer Portal profile limits, see Federated API Management component deployment profile limits, and Developer Portal component deployment profile limits.
You can choose different storage types with the three replica profiles, and so the pods deployed differ depending on the storage option chosen: Analytics 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
<analytics-instance-name>-oscron <analytics-instance-name>-oscron-<jobid>-<podid> oscron 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.

Note:

The c1 profiles (n1xc1.m16 and n3xc1.m16) do not support analytics data collection. Do not enable analyticsMode when you use c1 profiles. These profiles are designed for Developer Portal, Federated API Management, and API Agent mode without analytics ingestion.

The analyticsMode is set to false by default for c1 profiles

If you require analytics data collection and ingestion, use c2, c4, c6, or c8 profiles instead. For example, use n1xc2.m16 or n3xc4.m32.

The operator enforces the following validation rules for c1 profiles:

  • Do not enable ingestion for c1 profiles.
  • Enable at least one supported mode: federatedAPIManagementMode, devPortalMode, apiAgentMode, or apiSecurityMode.
  • Do not enable analyticsMode because of resource constraints.

The c1 profiles support the following modes (at least one must be enabled):

  • federatedAPIManagementMode: Use Federated API Management.
  • devPortalMode: Host the Developer Portal.
  • apiAgentMode: Use API Agent functionality.
  • apiSecurityMode: Use API Security functionality.

Not supported:

  • analyticsMode: Do not enable for c1 profiles.

n1xc1.m16

Table 2. n1xc1.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 50 m 1000 m 128 Mi 256 Mi 1 No
ingestion* ingestion 100 m 400 m 1 Gi 1 Gi 50 Gi 1 (only if enabled) Yes (only if enabled)
storage storage 225 m 800 m 3 Gi 3 Gi 200 Gi 1 Yes
director director 50 m 200 m 128 Mi 512 Mi 1 No
warehouse warehouse 50 m 1000 m 512 Mi 1 Gi 150 Gi 1 No
warehouse forklift 50 m 1000 m 128 Mi 1 Gi   1 No

*Note: Ingestion is disabled by default (enabled: false, replicas: 0) but can be enabled when federatedAPIManagementMode: true for audit event routing. When enabled, replicaCount becomes 1.

n1xc2.m16

Table 3. 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 7 Gi 7 Gi 50 Gi 1 Yes
storage storage 225 m 800 m 6 Gi 6 Gi 200 Gi 1 Yes
stunnel 20 m 200 m 64 Mi 128 Mi NA 1 Yes
director director 50 m 200 m 128 Mi 512 Mi 1
warehouse warehouse 100 m 1000 m 512 Mi 1 Gi 150 Gi 1  
warehouse forklift 100 m 1000 m 128 Mi 1 Gi   1  

n1xc4.m32

Table 4. 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 256Mi 512Mi 1
ingestion ingestion 1200 m 2200 m 7 Gi 7 Gi 50 Gi 1 Yes
storage storage 1200 m 1800 m 22 Gi 22 Gi 200 Gi 1 Yes
stunnel 20 m 200 m 64 Mi 128 Mi NA 1 Yes
director director 50 m 200 m 256Mi 512 Mi 1
warehouse warehouse 100 m 1000 m 512 Mi 2 Gi 150 Gi 1  
warehouse forklift 100 m 1000 m 128 Mi 2 Gi   1  

n1xc6.m48

Table 5. 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 7 Gi 7 Gi 50 Gi 1 Yes
storage storage 1800 m 2800 m 37 Gi 37 Gi 200 Gi 1 Yes
stunnel 20 m 200 m 64 Mi 128 Mi NA 1 Yes
director director 50 m 200 m 256 Mi 512 Mi 1
warehouse warehouse 100 m 1000 m 512 Mi 4 Gi 150 Gi 1  
warehouse forklift 100 m 1000 m 128 Mi 4 Gi   1  

n3xc1.m16

Table 6. n3xc1.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 50 m 1000 m 128 Mi 256 Mi 3 No
ingestion* ingestion 100 m 400 m 1 Gi 1 Gi 50 Gi 1 (only if enabled) Yes (only if enabled)
director director 50 m 200 m 128 Mi 512 Mi 3 No
storage (shared) storage 1200 m 1800 m 3 Gi 3 Gi 200 Gi 3 Yes
storage-os-master (dedicated) storage-os-master 400 m 800 m 2 Gi 2 Gi 5 Gi 3 Yes
storage (dedicated) storage 800 m 1000 m 4 Gi 4 Gi 200 Gi 3 Yes
warehouse warehouse 50 m 1000 m 512 Mi 1 Gi 150 Gi 1 No
warehouse forklift 50 m 1000 m 128 Mi 1 Gi   1 No

*Note: Ingestion is disabled by default (enabled: false, replicas: 0) but can be enabled when federatedAPIManagementMode: true for audit event routing. When enabled, replicaCount becomes 1 and ingestion requires license entitlement (400m CPU).

n3xc4.m32

Table 7. 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 128 Mi 256 Mi 3
ingestion ingestion 1200 m 2200 m 7 Gi 7 Gi 50 Gi 3 Yes
director director 50 m 200 m 128 Mi 512 Mi 3
storage (shared) storage 1200 m 1800 m 6 Gi 6 Gi 200 Gi 3 Yes
storage stunnel 20 m 200 m 64 Mi 128 Mi NA 3 Yes
storage (dedicated) storage 800 m 1000 m 20 Gi 20 Gi 200 Gi 3 Yes
storage-os-master (dedicated) storage-os-master 400 m 800 m 2 Gi 2 Gi 5 Gi 3 Yes
warehouse warehouse 100 m 1000 m 512 Mi 1 Gi 150 Gi 1  
warehouse forklift 100 m 1000 m 128 Mi 1 Gi   1  

n3xc6.m48

Table 8. 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 7 Gi 7 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 200 Gi 3 Yes
storage stunnel 20 m 200 m 64 Mi 128 Mi NA 3 Yes
storage (dedicated) storage 1400 m 1800 m 35 Gi 35 Gi 200 Gi 3 Yes
storage-os-master (dedicated) storage-os-master 400 m 1000 m 2 Gi 2 Gi 2 Gi 3 Yes
warehouse warehouse 100 m 1000 m 512 Mi 4 Gi 150 Gi 1  
warehouse forklift 100 m 1000 m 128 Mi 4 Gi   1  

n3xc8.m64

Table 9. 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 7 Gi 7 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 200 Gi 3 Yes
storage stunnel 20 m 200 m 64 Mi 128 Mi NA 3 Yes
storage (dedicated) storage 2400 m 2800 m 49 Gi 49 Gi 200 Gi 3 Yes
storage-os-master (dedicated) storage-os-master (dedicated) 400 m 1000 m 4 Gi 4 Gi 5 Gi 3 Yes
warehouse warehouse 100 m 1000 m 512 Mi 8 Gi 150 Gi 1  
warehouse forklift 100 m 1000 m 128 Mi 8 Gi   1