Tuning non-interruptible processes

Use this task to improve the performance of non-interruptible business processes.

Why and when to perform this task

Non-interruptible processes run in memory, without any user-interaction, database access, or persistent messaging support. They are synchronous and the entire processing occurs in one single transaction. The performance of non-interruptible processes depends largely on the following general server tuning parameters:

Steps for this task

  1. Tuning the JVM heap size
    Increasing the Java heap size may improve the non-interruptible processes’ throughput due to the reduction in the number of garbage collection cycles. But be cautious to keep it low enough to avoid heap swapping to disk.
  2. Tuning the EJB cache size
    This parameter is used to specify 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 will improve performance. If this value is small compared to the expected maximum number of active instances, the container will attempt to passivate some active instances resulting in lower performance.
  3. Tuning the ORB thread pool size
    If there are several clients connecting simultaneously to the server-side ORB, increasing the ORB thread pool size will improve the performance.

Results

Your non-interruptible processes will be running as fast as possible under the current environment and loading conditions.




Searchable topic ID:   t5tunenon
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/workflow/tasks/t5tunenon.html

Library | Support | Terms of Use | Feedback