Scaling resources for Concert (OCP)

You can adjust the Concert resources such as CPU and memory that are assigned to the pods to scale up and scale down based on your requirements. You can increase or decrease the amount of CPU and memory assigned to these pods to handle varying levels of workload. When you have higher workload and need better CPU and memory to run without facing issues, then you can use the scaling option. Scaling your resources, such as increasing the memory and the number of CPUs, increases the processing capacity of Concert. This helps to optimize performance and upload more data in to Concert.

Instructions

Refer the following instructions to adjust to different scaling levels. To get the details of different scaling levels, its component and property, refer to table.
  1. Use the following command to get the Concert instance details of the automation service:
    oc get automationservice -n <instance_ns>
    For example, run the following command:
    oc get automationservice -n concert-instance
    The response includes the name of the automation service and the age for the subject automation service. In the following example, the Concert instance name is automationservice-sample.
    
    NAME                       AGE
    automationservice-sample   17h
  2. Use the following command to modify the automation service instance:
     oc patch automationservice/<your_instance> --type=merge -n <your_ns> -p '{ "spec": { "componentCustomSpec":{ "scaleConfig": "<level>" }}}'
    Parameter Description
    <your_instance> The Concert instance details for the automaton service.
    <your_ns> The Concert instance name space for automation service.
    <level> Indicates the scaling configuration level. Supported values include
    • level_1 -
    • level_2 -
    • level_3 -
    • level_4 -
    Example:
     oc patch automationservice/automationservice-sample --type=merge -n concert-instance -p '{ "spec": { "componentCustomSpec":{ "scaleConfig": "level_2" }}}'
    

Scaling levels

You can use different scaling levels as follows. Each level of scaling is assigned with different resources and replicas. Level_1 is the lowest and Level_4 is the highest available for scaling. Use the scale setting for the Concert to set the scaling configuration level, the scale setting can be set to any of these levels:
  • level_1
  • level_2
  • level_3
  • level_4
Component Property Level 1 Level 2 Level 3 Level 4
ROJA_CORE Replicas 1 2 3 4
CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
PY_UTILS Replicas 1 2 3 4
CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
G_FWK Replicas 1 2 3 4
CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512Mi 512 Mi 512 Mi
ROJA_UI Replicas 1 2 5 6
CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
PORTAL_GW Replicas 1 2 5 6
CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
COMPLIANCE Replicas 1 2 3 4
CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
INGESTION Replicas 1 2 5 6
CPU limits 1536 m 1536 m 1536 m 3072 m
Memory limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
Ephemeral storage limits 2048 Mi 2048 Mi 2048 Mi 4096 Mi
CPU requests 1024 m 1024 m 1024 m 1024 m
Memory requests 512 Mi 512 Mi 512 Mi 512 Mi
Ephemeral storage requests 1024 Mi 1024 Mi 1024 Mi 1024 Mi
PIPELINE Replicas 1 2 5 6
CPU limits 1536 m 1536 m 1536 m 3072 m
Memory limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
Ephemeral storage limits 2048Mi 2048Mi 2048Mi 4096 Mi
CPU requests 1024 m 1024 m 102 4m 1024 m
Memory requests 512 Mi 512 Mi 512 Mi 512 Mi
Ephemeral storage requests 1024 Mi 1024 Mi 1024 Mi 1024 Mi
SRA Replicas 1 2 3 4
CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
MGMT Replicas 1 2 3 4
CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
PREPJOB CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
MGMTJOB CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 512 Mi 512 Mi 512 Mi 512 Mi
MINIO CPU limits 1536 m 1536 m 1536 m 3072 m
Memory limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
Ephemeral storage limits 2048 Mi 2048 Mi 2048 Mi 4096 Mi
CPU requests 1024 m 1024 m 1024 m 1024 m
Memory requests 512 Mi 512 Mi 512 Mi 512 Mi
Ephemeral storage requests 1024 Mi 1024 Mi 1024 Mi 1024 Mi
CFGDB CPU limits 1536 m 1536 m 1536 m 3072 m
Memory limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
Ephemeral storage limits 2048 Mi 2048 Mi 2048 Mi 4096 Mi
CPU requests 1024 m 1024 m 1024 m 1024 m
Memory requests 512 Mi 512 Mi 512 Mi 512 Mi
Ephemeral storage requests 1024 Mi 1024 Mi 1024 Mi 1024 Mi
APPDB CPU limits 1536 m 1536 m 1536 m 3072 m
Memory limits 1024 Mi 1024 Mi 1024 Mi 2048 Mi
Ephemeral storage limits 2048 Mi 2048 Mi 2048 Mi 4096 Mi
CPU requests 1024 m 1024 m 1024 m 1024 m
Memory requests 512 Mi 512 Mi 512 Mi 512 Mi
Ephemeral storage requests 1024 Mi 1024 Mi 1024 Mi 1024 Mi
LICENSE_CJ CPU limits 1024 m 1024 m 1024 m 2048 m
Memory limits 512 Mi 512 Mi 512 Mi 1024 Mi
Ephemeral storage limits 512 Mi 512 Mi 512 Mi 2048 Mi
CPU requests 512 m 512 m 512 m 512 m
Memory requests 256 Mi 256 Mi 256 Mi 256 Mi
Ephemeral storage requests 256 Mi 256 Mi 256 Mi 256 Mi