TIBCO OPE Resource Allocation

Resource allocation for TIBCO OPE services on a cloud platform

  1. Docker containers

    Modify the .env file present in the $OPE_HOME/docker directory for MinRAMPercentage and MaxRAMPercentage usage for the following values:

    min_ram_percentage=25.0
    max_ram_percentage=100.0
  2. Kubernetes

    Kubernetes users need to modify the individual Kubernetes script files as required.

    Example:

    For the configurator service, modify the kubernetes-deploy-run-configurator.yml file:

    env:
    - name: min_ram_percentage
    value: "25.0"
    - name: max_ram_percentage
    value: "100.0"
  3. Helm Charts

    Helm Charts users must change MinRAMPercentage and MaxRAMPercentage based on their requirements in the values.yaml file:

    min_ram_percentage: 25.0
    max_ram_percentage: 100.0

Resource allocation of JVM for TIBCO OPE services on a non-cloud platform (baremetal box or VM)

When any TIBCO OPE service is started from a bare-metal Linux machine, the user must set the JVM parameters for each micro-service that starts for TIBCO OPE as per the following value:

./start.sh -XX:MinRAMPercentage=25.0 -XX:MaxRAMPercentage=100.0
Note: The values for the cpu/memory resources change as per the load on a particular micro-service. If the user chooses any type of out-of-the-box caching offered along with TIBCO OPE, by default, values for the cpu/memory resources must be increased as required.