Download PDF (1.3 MB) - IBM Redbooks

4.1 Performance tuning methodology
We suggest a system-wide approach to performance tuning the Business Process Manager
environment. System performance tuning, which requires training and experience, is not
exhaustively described here. Rather, we highlight key aspects of tuning that are important.
Tuning encompasses every element of the deployment topology:
► Physical hardware topology choices
► Operating system parameters
► Business Process Manager server, WebSphere Application Server, database, and
messaging engine settings
The methodology for tuning can be stated as an iterative loop:
1. Pick a set of reasonable initial parameter settings and run the system.
2. Monitor the system to obtain metrics that indicate where performance is being limited.
3. Use monitoring data to guide further tuning changes.
4. Repeat until done.
These steps are described next.
4.1.1 Picking a set of reasonable initial parameter settings
Use the tuning checklist in 4.2, “Tuning checklist” on page 50 for a systematic way to set
parameters.
For specific initial values, see Chapter 5, “Initial configuration settings” on page 97 for settings
of the workloads that are used in IBM internal performance evaluation. You might consider
these values for initial values.
4.1.2 Monitoring the system
Monitor the system components to determine system health and the need for further tuning
as follows:
►
►
For each physical machine in the topology, including front-end and back-end servers such
as web and database servers, monitor the following processes by using the relevant OS
tools (such as vmstat, iostat, netstat, or their operating system-specific equivalents):
– Processor core use
– Memory use
– Disk use
– Network use
Complete the following actions for each Java virtual machine (JVM) process started on a
physical machine (for example, process server, messaging engine server, and other
components):
– Use tools such as ps or their equivalents to get core and memory usage per process.
– Collect verbose garbage collection (verbosegc) statistics to obtain information about
Java memory usage.
48 IBM Business Process Manager V8.0 Performance Tuning and Best Practices