Manually scaling resources for services

You can adjust IBM Cloud Pak® for Data services by scaling the resources that they use to support high availability or to increase processing capacity. Resources can be scaled based on predefined resource configurations.

Permissions that you need for this task
You must be either:
  • A cluster administrator
  • An administrator of the project where the software is installed, for example cpd-instance
When you need to complete this task
If a service supports scaling, you can scale the service at any time after you install it.

Scaling changes the capacity of services by adjusting the memory resource settings, the number of CPUs, and the number of pods that are available. Scaling a service from small to medium increases the processing capacity of the application.

Use the scaleConfig setting in the service custom resource (CR) to set the scaling configuration for a service.

Tip: Detailed information about the various sizes is available in the Component scaling guidance PDF document. The PDF is in the IBM® Entitled Registry. For details, see Downloading the component scaling guidance PDF from the IBM Entitled Registry.

The following table shows the services that support manual scaling. Click a service name or scroll to the procedure for manually scaling services for detailed instructions about how to scale each service.

Service name Uses the scaleConfig setting Uses a different scaling method
Cloud Pak for Data control plane  
Common core services  
IBM Cloud Pak foundational services  
AI Factsheets  
Analytics Engine powered by Apache Spark  
Cognos® Analytics  
Cognos Dashboards  
Data Privacy  
Data Refinery  
Data Replication  
DataStage®  
Db2®  
Db2 Big SQL  
Db2 Data Gate    
Db2 Data Management Console  
Db2 Warehouse  
Decision Optimization  
EDB Postgres    
Execution Engine for Apache Hadoop    
IBM Match 360 with Watson™  
Informix®  
MANTA Automated Data Lineage  
OpenPages®  
Planning Analytics  
Product Master  
RStudio® Server Runtimes    
Scheduling service  
SPSS® Modeler  
Voice Gateway  
Watson Assistant  
Watson Discovery  
Watson Knowledge Catalog  
Watson Knowledge Studio  
Watson Machine Learning  
Watson Machine Learning Accelerator  
Watson OpenScale  
Watson Pipelines  
Watson Query  
Watson Speech services  
Watson Studio  
Watson Studio Runtimes    
watsonx.data  

Before you begin

In most cases, you use the cpd-cli manage update-cr command to set the scaleConfig setting to scale services.

Some services support scaling but do not support the use of the cpd-cli manage update-cr, or do not support the use of the scaleConfig parameter.

Before you scale up a service, ensure that your cluster can support the additional workload. If necessary, contact your IBM Support representative.

When you change the scaling configuration of a service, you also must scale the related services individually. For more information about service dependencies, see Service software requirements, and then scale the services as necessary.

Best practice: You can run the commands in this task exactly as written if you set up environment variables. For instructions, see Setting up installation environment variables.

Ensure that you source the environment variables before you run the commands in this task.

Procedure

Complete the steps for the service that you are scaling:

Cloud Pak for Data control plane
Note: The Cloud Pak for Data control plane does not support the use of the cpd-cli manage update-cr command to set value of the scaleConfig setting.
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small_mincpureq (Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting. For example, you can use this setting with Express Parts installations.)
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource::
    oc patch zenservice lite-cr \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --type="json" \
    --patch '[{"op": "replace", "path":"/spec/scaleConfig", "value":'${SIZE}' }]'

Common core services
Note: The common core services does not support the use of the cpd-cli manage update-cr command to set value of the scaleConfig setting.
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small_mincpureq (Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting. For example, you can use this setting with Express Parts installations.)
    • small (default)
    • medium
    • large
  2. Run the following command to scale the common core services:
    oc patch ccs ccs-cr \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --type="json" \
    --patch '[{"op": "replace", "path":"/spec/scaleConfig", "value":'${SIZE}' }]'

    You can optionally scale the Flight service when you scale the common core services. To scale the Flight service, you must adjust the number of replicas and the amount of vCPU that is allocated to Flight service pods:

    Small
    oc patch ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS} --type merge --patch '
    {
        "spec":{
            "wdp_connect_flight_min_replicas": 1,
            "wdp_connect_flight_resources":{"requests":{"cpu": "200m", "memory": "650Mi"}, "limits":{"cpu": "2", "memory": "4Gi"}}
        }
    }
    '
    Medium
    oc patch ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS} --type merge --patch '
    {
        "spec":{
            "wdp_connect_flight_min_replicas": 4,
            "wdp_connect_flight_resources":{"requests":{"cpu": "1", "memory": "650Mi"}, "limits":{"cpu": "2", "memory": "4Gi"}}
        }
    }
    '
    Large
    oc patch ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS} --type merge --patch '
    {
        "spec":{
            "wdp_connect_flight_min_replicas": 8,
            "wdp_connect_flight_resources":{"requests":{"cpu": "2", "memory": "650Mi"}, "limits":{"cpu": "4", "memory": "4Gi"}}
        }
    }
    '

IBM Cloud Pak foundational servicesFor information about how to scale IBM Cloud Pak foundational services, see Configuring IBM Cloud Pak foundational services by using the CommonService custom resource.

AI Factsheets
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=factsheet \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Analytics Engine powered by Apache Spark
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=analyticsengine \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Cognos Analytics
When you provision a Cognos Analytics service instance, you choose a size for the instance. The following sizes are supported:
  • fixed minimum (no scale)
  • small
  • medium
  • large

For detailed information about scaling a service instance, see Provisioning the Cognos Analytics service.

You can also change the size of the instance after it is already provisioned. For more information, see Changing the plan size of the Cognos Analytics service instance.


Cognos Dashboards
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=dashboard \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Data Privacy
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=dp \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Data Refinery

Data Refinery does not support the cpd-cli manage update-cr command to set value of the scaleConfig setting.

  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    oc patch DataRefinery datarefinery-sample \
    -n ${PROJECT_CPD_INST_OPERANDS} \
    --type=merge
    -p '{"spec":{"scaleConfig":"size"}}'

    If you changed the default name of the Data Refinery custom resource, replace datarefinery-sample in the command.


Data Replication
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    oc patch replicationservice  replicationservice-cr \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch '{"spec":{"scaleConfig":"${SIZE}"}}' \
    --type=merge

    If you changed the default name of the Data Replication custom resource, replace replicationservice-cr in the command.


DataStage
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=datastage_ent \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Db2

To scale Db2, work with your IBM Sales representative to size your cluster.

For more information about scaling Db2, see Scaling up Db2.


Db2 Big SQL

You can scale a Db2 Big SQL service instance from the instance details page in the Cloud Pak for Data web client.

For information about scaling Db2 Big SQL, see Updating instance configuration.


Db2 Data Management Console
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    oc patch dmc <dmcs_cr_name> \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch '{"spec":{"scaleConfig":"${SIZE}"}}' \
    --type=merge

    Replace <dmcs_cr_name> with the name of the Db2 Data Management Console custom resource.


Db2 Warehouse

To scale Db2 Warehouse, work with your IBM Sales representative to size your cluster.

For more information about scaling Db2 Warehouse, see Scaling Db2 Warehouse.


Decision Optimization
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=dods \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

IBM Match 360 with Watson

Work with your IBM Sales representative to get accurate sizing based on your expected workload.

  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>

    The following sizes are supported:

    • x-small (demonstration use only)
    • small_mincpureq (Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting.)
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    oc patch mdm mdm-cr \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch '{"spec":{"scaleConfig":"${SIZE}"}}' \
    --type=merge

Informix

Informix does not support the cpd-cli manage update-cr command to scale the service.

You can run the following commands to adjust the amount of CPU and memory that are allocated to an Informix service instance:

  1. From the Informix instance details page in the Cloud Pak for Data web client.
    1. Get the deployment ID of the instance.
    2. Review the current configuration to determine the number of nodes, the number of cores, and the amount of memory allocated to the instance.
  2. Set the INSTANCE_ID environment variable:
    export INSTANCE_ID=<instance-id>
  3. To scale the number of Informix servers in the service instance, run:
    oc patch Informixes informix-${INSTANCE_ID} \
    --namespace ${PROJECT_CPD_INST_OPERANDS}
    --patch '{"spec":{"replicas":2}}' \
    --type=merge
  4. To increase the CPU or memory that the service instance can use, run the appropriate command:
    Increase memory limits

    The following example sets the memory limits to 4 GiB.

    oc patch Informixes informix-${INSTANCE_ID}-server \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch '{"spec":{"resources":{"limits":{"memory":"4Gi"}}}}' \
    --type=merge
    Increase memory

    The following example sets the memory requests to 2 GiB.

    oc patch Informixes informix-${INSTANCE_ID}-server \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch '{"spec":{"resources":{"requests":{"memory":"2Gi"}}}}' \
    --type=merge
    Increase CPU limits

    The following example sets the CPU limits to 4 CPU.

    oc patch Informixes informix-${INSTANCE_ID}-server \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch '{"spec":{"resources":{"limits":{"cpu":"4"}}}}' \
    --type=merge
    Increase CPU

    The following example sets the CPU requests to 2 CPU.

    oc patch Informixes informix-${INSTANCE_ID}-server \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch '{"spec":{"resources":{"requests":{"cpu":"2"}}}}' \
    --type=merge
  5. Delete the StatefulSet for the changes to take effect:
    oc delete sts informix-${INSTANCE_ID}-server

MANTA Automated Data Lineage
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=mantaflow \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

OpenPages
When you provision an OpenPages service instance, you choose a size for the instance. The following sizes are supported:
  • Extra Small (XS)
  • Small
  • Medium
  • Large

For more information about scaling a service instance, see Scaling OpenPages.


Planning Analytics

When you provision a Planning Analytics service instance, you choose a size for the instance.

  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small_mincpureq (Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting. For example, you can use this setting with Express Parts installations.)
    • small (default)
    • medium
    • large
  2. Set the INSTANCE_NAME environment variable to the appropriate value for your environment.
    export INSTANCE_NAME=<instance-name> 
  3. Run the following command to scale the component by updating the custom resource:
    oc patch PAServiceInstance ${INSTANCE_NAME} \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch '{"spec":{"scaleConfig":"'${SIZE}'"}}' \
    --type=merge

For more information about scaling a service instance, see Provisioning the Planning Analytics service.


Product Master
When you provision a Product Master service instance, you choose a size for the instance. The following sizes are supported:
  • Small
  • Medium
  • Large
  • Extra large (XLarge)

For more information about scaling a service instance, see Scaling Product Master instances.


Scheduling service
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>

    The following sizes are supported:

    • small: Up to 50 worker nodes.
    • medium: Up to 100 worker nodes. One standby pod is created.
    • large: More than 100 worker nodes. One standby pod is created.
  2. Run the following command to scale the component by updating the custom resource:
    Workstations with olm-utils-v2:4.7.2 or later
    cpd-cli manage update-cr \
    --component=scheduler \
    --cluster_component_ns=${PROJECT_SCHEDULING_SERVICE } \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"
    Workstations with olm-utils-v2:4.7.0 or olm-utils-v2:4.7.1
    oc patch scheduling ibm-cpd-scheduler \
    -n ${PROJECT_SCHEDULING_SERVICE} \
    --type merge \
    -p "{\"spec\":{\"scaleConfig\": \"${SIZE}\"}}"

SPSS Modeler
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=spss \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Voice Gateway

You can scale Voice Gateway by changing the number of replicas.

  1. Get the list of Voice Gateway instances in the ${PROJECT_CPD_INST_OPERANDS} project:
    oc get voicegateway --namespace ${PROJECT_CPD_INST_OPERANDS}
  2. Set the INSTANCE_NAME environment variable to the instance of Voice Gateway that you want to scale:
    export INSTANCE_NAME=<instance-name>
  3. Get the current number of replicas for the instance:
    oc get voicegateway ${INSTANCE_NAME} \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    -o=jsonpath='{..status.replicas}'

    Use the output of this command to determine the appropriate number of replicas for the instance.

  4. Set the REPLICAS environment variable to the number of replicas to use for the instance:
    export REPLICAS=<number-of-replicas>
  5. Scale the instance:
    oc scale voicegateway ${INSTANCE_NAME} \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --replicas=${REPLICAS}

Watson Assistant
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small

      You can specify either small or Starter

    • medium (default)

      You can specify either medium or Production

    • large
  2. Run one of the following commands to scale the component by updating the custom resource:
    • cpd-cli manage update-cr \
      --component=watson_assistant \
      --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
      --patch="{\"size\":\"${SIZE}\"}"
      
    • oc project ${PROJECT_CPD_INST_OPERANDS}
      export INSTANCE=`oc get wa -n ${PROJECT_CPD_INST_OPERANDS} |grep -v NAME| awk '{print $1}'`
      oc patch wa ${INSTANCE} --namespace ${PROJECT_CPD_INST_OPERANDS} --patch "{\"spec\":{\"size\":\"${SIZE}\"}}" --type=merge

Watson Discovery
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • xsmall
    • _default
    • medium
    • large
      Important: Scaling Watson Discovery from medium to large significantly increases the number of replicas. Be sure that you want to make this change because it is not recommended that you scale backwards.
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=watson_discovery \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"
Alternatively, you can scale Watson Discovery by editing the custom resource. For more information, see Scaling Watson Discovery.

Watson Knowledge Catalog
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=wkc \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"
Restriction: Legacy features always use one replica.

For more information on scaling the Db2 database that is associated with Watson Knowledge Catalog, see Scaling up Db2 for Watson Knowledge Catalog.


Watson Knowledge Studio
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small
    • medium
  2. Run the following command to scale the component by updating the custom resource:
    oc -n ${PROJECT_CPD_INST_OPERANDS} patch --type=merge KnowledgeStudio \
    wks -p "{\"spec\":{\"global\":{\"size\":\"${SIZE}\"}}}"

Watson Machine Learning
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small_mincpureq (Use this setting when you want to use minimal reserved CPU resources without removing the CPU pod setting. For example, you can use this setting with Express Parts installations.)
    • small (default)
    • medium
  2. Run the following command to scale the component by updating the custom resource:
    oc patch wmlbase wml-cr \
    --namespace ${PROJECT_CPD_INST_OPERANDS} \
    --patch "{\"spec\":{\"scaleConfig\":\"${SIZE}\"}}" \
    --type=merge

    If you changed the default name of the Watson Machine Learning custom resource, replace wmlbase in the command.


Watson Machine Learning Accelerator
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=wml_accelerator \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Watson OpenScale
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small
    • medium
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=openscale \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Watson Pipelines
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=ws_pipelines \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Watson QueryWatson Query does not use the spec.scaleConfig value in the custom resource for scaling. Work with your IBM Sales representative to get an accurate sizing based on your expected workload. IBM Sales can help you estimate the total demand for Watson Query.

For more information about the process for scaling Watson Query, see Scaling Watson Query.


Watson Speech services
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • xsmall
    • small
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:

    For Watson Speech to Text:

    cpd-cli manage update-cr \
    --component=watson_speech \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":{\"stt\":{\"size\":\"${SIZE}\"}}}"

    For Watson Text to Speech:

    cpd-cli manage update-cr \
    --component=watson_speech \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":{\"tts\":{\"size\":\"${SIZE}\"}}}"
Note: For detailed information about how to scale Watson Speech to Text and Watson Text to Speech, see Scaling up your Watson Speech services installation.

Watson Studio
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
  2. Run the following command to scale the component by updating the custom resource:
    cpd-cli manage update-cr \
    --component=ws \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
    --patch="{\"scaleConfig\":\"${SIZE}\"}"

Watson Studio Runtimes

Watson Studio Runtimes are started with the requested resources. You cannot scale up the started runtime. Every runtime is user and project bound.


watsonx.data
  1. Set the SIZE environment variable to the appropriate value for your environment.
    export SIZE=<size>
    The following sizes are supported:
    • small (default)
    • medium
    • large
    • xlarge
  2. Run the following command to scale the addon components UI, API, and Nodeclient:
    oc patch wxdAddon wxdaddon \ 
      --type=merge \ 
       -n ${PROJECT_CPD_INST_OPERANDS} \ 
       -p '{ "spec": { "scaleConfig": "$SIZE" } }'
  3. Run the following command to scale the instance components Postgres, Hive-metastore, and MinIO:
    oc patch wxd lakehouse \
      --type=merge \
       -n ${PROJECT_CPD_INST_OPERANDS} \
       -p '{ "spec": { "scaleConfig": "$SIZE" } }'
  4. Follow the steps to scale Presto engine components Presto, Presto-coordinator, and Presto-worker:
    1. Run the following command to get the Presto engine name:
      oc get wxdengine
      oc get wxdengine
      NAME                  AGE
      lakehouse-presto-01   75m
    2. Run the following command to scale Presto components in the pods:
      oc patch wxdengine/lakehouse-presto-01 \
        --type=merge \
         -n ${PROJECT_CPD_INST_OPERANDS} \
         -p '{ "spec": { "scaleConfig": "small", "lakehouseDeploymentType": "multinode" } }'