Process choreographer tuning tips
Use the following tuning suggestions to improve performance to the process
engine:
- Tune the database using a tuning wizard such as DB2's Performance Wizard.
- Use a faster disk, or use RAID volumes and distribute the MQ logs, MQ
data, DB2 logs, DB2 data and WebSphere Application Server transaction logs
across separate disks.
- Tune the WebSphere Application Server runtime to efficiently handle data
and messages, and use maximum capacity with the following configuration settings:
- Increase the Java Message Service (JMS) Listener port Max sessions parameter
to higher than the default value by Configuring a listener port.
Increasing the value enables efficient message handling by the flow message-driven
beans. Based on the amount of work and the resources available, a value between
15 and 25 gives best performance and scaling on enterprise systems.
- Increase the database connection pool size as described inConnection pool settings and the Statement cache size as described
in Data source settings to optimize the data handling.
In performance tests, when using a value of 50 for both settings on a NetFinity
5500 machine with an enterprise workload on long running processes, best performance
is achieved.
- Increase the JMS provider connection pool size as explained in Generic JMS connection factory settings and session pool settings to improve message handling
efficiency. In performance tests, both pool values were set to 600 on a NetFinity
5500 machine to increase message handling efficiency.
Searchable topic ID:
rprf_BPCtips
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/ae/rprf_BPCtips.html