IBM BPM, V8.0.1, All platforms > Tuning

Tuning parameters

A set of performance tuning parameters can be commonly used for tuning the products.

• Tracing and logging flags
  Tracing and logging are often necessary when you are setting up a system or debugging issues. However, because tracing and logging produce significant performance issues, try to avoid using them in production environments and when you are evaluating performance.
• Java tuning parameters
  

  You can use the administrative console to change the settings for some frequently used Javaâ„¢ Virtual Machine (JVM) tuning parameters relating to garbage collection and heap sizes.

• MDB ActivationSpec
  

  You can use Java Message Service (JMS) activation specifications to bind application message-driven beans (MDBs) to the message queues that drive the MDB onMessage methods. Two activation specification parameters of particular interest are the maximum batch size and the maximum concurrent endpoints.

• Servant threads in workload profiles
  

  You can configure the number of servant threads in the workload profile for the server. To calculate the number of threads for each profile setting, you can use a formula based on the number of available processors.

• Workload manager service class
  The z/OS operating system assigns machine resources to process requests based on the workload manager service class that has been assigned. Ensure that the workload manager has been configured to classify the requests to receive an appropriate level of service.
• MDB throttle
  On WebSphere Application Server for z/OS, you can use the message-driven bean (MDB) throttle to control MDB processing. The MDB throttle prevents the z/OS WLM work queue from becoming full of messages while it is waiting to be processed by worker threads in the WebSphere Application Server servant.
• JMS connection pool sizes
  

  You can increase the maximum connection pool size to allow for greater concurrency. If that if only one deployed application is obtaining connections from a particular connection factory, there is no benefit in increasing the maximum queue connection pool size beyond the maximum concurrency, as configured within the activation specification.

• DataSource connection pool size
  

  You can adjust the minimum and maximum number of connections to DB2 for z/OS, and the wait for connection timeout value.You can adjust the minimum and maximum number of connections to the databases, and the wait for connection timeout value.

• DataSource prepared statement cache size
  The prepared statement cache optimizes the processing of prepared SQL statements and callable statements. The size of the cache can be tuned to avoid cache entries from being discarded.
• Messaging engine properties
  Two message engine custom properties can impact the messaging engine performance.
• Choose the proper level of security
  The security features of WebSphere Application Server provide important protection against unauthorized use of resources. While not advocating that security be completely disabled, there are various security mechanisms available, each of which adds additional processing.
• Run production servers in production mode
  Business Process Management servers are typically run in production mode on production servers. However, servers can also be run in development mode to reduce startup time for the server by using JVM settings to disable bytecode verification and reduce JIT compilation time.

Tuning