08.06.2014 Views

Download PDF (1.3 MB) - IBM Redbooks

Download PDF (1.3 MB) - IBM Redbooks

Download PDF (1.3 MB) - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

►<br />

►<br />

Ensure that database statistics are the most current.<br />

If database utilization is running at high throughput rates, consider disabling some or all<br />

database auto-maintenance tasks to avoid impacting peak throughput. However, if you<br />

disable these capabilities, be sure to perform runstats regularly to update database<br />

statistics.<br />

Use your database vendor’s tool to obtain recommendations for indexes to create; this<br />

step is necessary because different applications often require unique indexes. Create the<br />

indexes that are suggested by the database vendor’s tool.<br />

4.5.2 Tune the Event Manager<br />

This section offers tuning suggestions for the Event Manager.<br />

Tune BPD queue size and worker thread pool size<br />

To optimize throughput and scaling, a necessary step is often to set the BPD Queue Size and<br />

Worker Thread Pool parameters to larger values than their defaults. These values are defined<br />

in the file 80EventManager.xml file in the configuration directory for the Process Server. The<br />

specific configuration directory is as follows:<br />

%BPM%/profiles//config/cells//nodes//servers/<br />

server1/process-center or process-server/config/system<br />

To change the values, directly edit that file. Here are several guidelines for tuning these<br />

parameters:<br />

►<br />

►<br />

Start with a BPD Queue Size (bpd-queue-capacity) of 10 per physical processor core (for<br />

example, 40 for a four-processor core configuration), with a maximum value of 80. Tune as<br />

needed after that, based on the performance of your system.<br />

Start with a Worker Thread Pool Size (max-thread-pool-size) of 30 + 10 per physical<br />

processor core (for example, 70 for a four-processor core configuration), with a maximum<br />

value of 110. Tune as needed after that, based on the performance of your system.<br />

Tune the Number of Timer Events<br />

For BPDs with many timers, reduce the amount of Event Manager activity by reducing the<br />

number of timer events that are held in memory through the following change to the<br />

80EventManager.xml file in the profiles directory (the full path to this file is in “Tune BPD queue<br />

size and worker thread pool size” on page 58); the default is 60000:<br />

5000<br />

4.5.3 Optimize business data search operations<br />

If slow response times, or high database usage, are observed when performing business data<br />

searches, do the following tasks:<br />

►<br />

►<br />

Ensure that no more than 10 business data variables are defined. If there are more than<br />

10 of these variables, examine your business requirements to determine if all the variables<br />

are required. Our experience shows that 10 or less is generally sufficient.<br />

Enable Process Search optimizations through the Saved Search Accelerator Tools for the<br />

Process Server. This technique is often much faster, and uses fewer database resources,<br />

than the default mechanism. The Process Search optimizations can be enabled by using<br />

command-line tools, as described at the following location:<br />

http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0m1/index.jsp?topic=%2Fcom.ibm.wb<br />

pm.main.doc%2Ftopics%2Fctuneprocportal.html<br />

58 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!