Tuning microflows

Use this task to improve the performance of microflows.

Why and when to perform this task

Microflows run in memory, without any user-interaction or persistent messaging support. Database access is required only to retrieve template data and if audit logging is enabled for the microflow. Microflows are synchronous, and the entire processing occurs in a single transaction. The performance of microflows depends largely on the following general server tuning parameters:

Steps for this task

  1. Tune the JVM heap size.

    By increasing the Java™ heap size, you can improve the throughput of microflows, because a larger heap size reduces the number of garbage collection cycles that are required. Keep the value low enough to avoid heap swapping to disk. For guidelines on the size of the server heap, see the relevant step in Tuning the application server.

  2. Tune the Enterprise JavaBeans™ (EJB) cache size.

    This parameter specifies the number of buckets in the active instance list within the EJB container. Setting this parameter equal to the maximum expected number of active instances improves performance. If this value is small compared with the expected maximum number of active instances, the container attempts to passivate some active instances, resulting in lower performance.

  3. Tune the thread pool size of the object request broker (ORB).

    If several clients are to be able to connect simultaneously to the server-side ORB, increase the ORB thread pool size to improve performance.

Result

Your microflows are running as fast as possible under the current environment and loading conditions.
Related tasks
Tuning long-running processes

Terms of use | | Broken links

Last updated: Tue Dec 06 04:14:41 2005

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)