Skip to Content
Information
    • Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Performance tuning

This topic provides recommendations for tuning the deployment of BMC Release Process Management for optimal performance

Information
Additional information

For BMC Release Process Management version 4.4, you need version 1.7 of Java Runtime Environment (JRE) for the installation. BMC recommends you to use JRE 1.7 as it provides improved performance benefits.

Configurations recommended

Use the following configurations for optimal performance of the product:

 

  • In <RLM_HOME>\Releases\<your product version>\BRPM\config\torquebox.yml, ensure that the following parameters are set:

    ...
    messaging:
     /queues/backgroundable/automation:
        AutomationHandler:
          concurrency: 3

  • In <RLM_HOME>\Releases\<your product version>\BRPM\config\database.yml, ensure that the following parameters are set:

    production: 
      ...

      pool: 10 # NOTE: Increase the connection pool size
      wait_timeout: 10

  • In <RLM_HOME>\Releases\<your product version>\BRPM\config\automation_settings.rb , ensure that the following automation parameters are set:

    ...
    $AUTOMATION_JAVA_OPTS = "-XX:PermSize=256m -Xmx512m -Xms256m -Xss2048k"
     ...

  • In <RLM_HOME>\Releases\<your product version>\BRPM\config\automation_settings.default.rb, ensure that the following automation parameters are set:

    ...
    $AUTOMATION_JAVA_OPTS = "-XX:PermSize=256m -Xmx512m -Xms256m -Xss2048k"
     ...

  • For Windows,  in <RLM_HOME>\bin\start.bat, ensure that the following application parameters are set:

    ...
    set JAVA_OPTS="%JAVA_OPTS% -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:+UseParallelGC -XX:+CMSClassUnloadingEnabled"
     ...

  • For Linux,  in <RLM_HOME>\bin\start.sh, ensure that the following application parameters are set:

    ...
    export JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:+UseParallelGC -XX:+CMSClassUnloadingEnabled"
    ...

  • For Solaris,  in <RLM_HOME>\bin\start.sh, ensure that the following application parameters are set:

    ...
    JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:+UseParallelGC -XX:+CMSClassUnloadingEnabled"
    ...
Warning

Notes

  • In application and automation parameters, specify the Java memory settings for heap size in  megabytes (m). For example: -Xms1024m -Xmx4096m -XX:PermSize=512m.
  •  In automation parameters, specify the stack size in kilobytes. For example: -Xss2048k.
  • After changing the configuration, restart the application service.

Verified parameter combinations

The following table provides a combination of verified parameters and hardware recommendations that you can use for optimal performance of the product. The sets included in the table are presented in an increasing order of performance and faster response time.

Parameter combinations

Parameter

Set 1 values

Set 2
Values

Comments

Concurrent users

< 10

30

These are simultaneous users hitting web GUI simultaneous + users triggering requests with automations.

MaxPermSize

512 MB

512 MB

None

ms

1024 MB

1024 MB

Minimum Java heap size. To improve the application performance, BMC recommends to set the same maximum Java heap size value for both minimum Java heap size and maximum Java heap size parameters.

mx

2048 MB

4096 MB

Maximum Java heap size. To improve the application performance, BMC recommends to set the same maximum Java heap size value for both minimum Java heap size and maximum Java heap size parameters.

concurency

3

3

The count presented in the sets indicate the number of parallel automated steps that can run concurrently.

pool

10

30+

Pool indicates the maximum number of database connections made by the application. This count but must be less or equal to the maximum connections configured in a database server.

Recommended hardware

Set 1 values

Set 2 values

 

CPU cores

2

4

None

Physical memory

4 GB

8 GB

None

Recommended deployment

The following table provides information about a recommended deployment scenario:

Warning

This deployment can sustain a load of 60 concurrent users in case of a High Availability (HA) environment and 30 concurrent users in case of a Non-High Availability (Non HA) environment.

Deployment scenario

Scenarios

Percentage of total concurrent users

Transaction rate 
(per user, per hour)

Users creating and executing 100% automated requests

10%

4

Users maintaining plans and handling associated requests

10%

4

Users interacting with started requests

50%

2

Users creating requests, steps, and procedures

20%

4

Users using other tabs such as the Reports tab

10%

4

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Release Process Management 4.4