Performance tuning
This topic provides recommendations for tuning the deployment of BMC Release Process Management for optimal performance.
Configurations recommended
You can use the following configurations for optimal performance of the product:
Ensure that the following lines exist in <RLM_HOME>\Releases\<your product version>\BRPM\WEB-INF\web.xml
<context-param>
<param-name>jruby.min.runtimes</param-name>
<param-value>1</param-value> <!-- NOTE: value should be confirmed -->
</context-param>
<context-param>
<param-name>jruby.max.runtimes</param-name>
<param-value>1</param-value> <!-- NOTE: value should be confirmed -->
</context-param>
...
Changes needed in <RLM_HOME>\Releases\<your product version>\BRPM\WEB-INF\config\database.yml
...
pool: 50 # NOTE: Increase the connection pool size
wait_timeout: 10
Changes needed in <RLM_HOME>\bin\start.sh (UNIX) or <RLM_HOME>\bin\start.bat (Windows)
JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:+UseParallelGC"
JRUBY_OPTS=" ... "
...
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:
Parameter combinations
Parameter | Set 1 | Set 2 | Comments |
|---|---|---|---|
Concurrent users | < 10 | 30 | These are simultaneous users hitting web GUI simultaneous + users triggering requests with automations. |
jruby.min.runtimes | 1 | 1 | With BMC Release Process Management version 2.6.00 and later, the value for this parameter must be 1. |
jruby.max.runtimes | 1 | 1 | With BMC Release Process Management version 2.6.00 and later, the value for this parameter must be 1. |
MaxPermSize | 256 MB | 512 MB | None |
ms | 256 MB | 1024 MB | None. Minimum java heap size. |
mx | 1,024 MB | 2048 MB | None. Maximum java heap size. |
jruby.worker.thread.count | Any | 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. |
JRUBY_OPTS | - | -J-Xms64m | This is an optional configuration that can further increase the capacity of a single virtual machine. However, if you find that your automation fails with this setting, you can skip this configuration. |
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:
Deployment scenario
Scenarios | Percentage of total concurrent users | Transaction rate |
|---|---|---|
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 |