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.

Deployment tuning

The BMC Release Process Management installation program automatically configures the system for average use: a load of approximately 30 concurrent users with a maximum of 10 steps per request.

For tuning the performance of the deployment, BMC suggests the following configurations:

Changes in <BRPM_HOME>\server\webapps\brpm\WEB-INF\web.xml


...

 <context-param>
   <param-name>jruby.min.runtimes</param-name>
   <param-value>1</param-value>
 </context-param>

 <context-param>
   <param-name>jruby.max.runtimes</param-name>
   <param-value>4</param-value> <!-- NOTE: value is updated -->
 </context-param>

...

 <context-param>
   <param-name>jruby.worker.thread.count</param-name>
   <param-value>2</param-value> <!-- NOTE: value is updated -->
 </context-param>

Changes in <BRPM_HOME>\server\webapps\brpm\WEB-INF\config\database.yml


production: 
  ...

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

Changes in <BRPM_HOME>\lib\tanuki\conf\wrapper.conf


...

#set.JRUBY_OPTS=-J-XX:-UseGCOverheadLimit # NOTE: Confirm that it is commented

...

wrapper.java.additional.9=-XX:MaxPermSize=256m

# Initial Java Heap Size (in MB) -- NOTE: Updated value
wrapper.java.initmemory=512

# Maximum Java Heap Size (in MB) -- NOTE: Updated value
wrapper.java.maxmemory=4096

...

 

Warning

Note

After you change the configuration, you must restart the application service.

The following table indicates verified combinations of parameters. The sets are presented in the order of increase in performance and faster response time.

 

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

BMC Release Process Management 2.5