Download PDF (1.3 MB) - IBM Redbooks

More documents

Recommendations

Info

► ► ► ► Messaging and message bindings – Optimize activation specification (JMS, MQJMS, WebSphere MQ). – Optimize queue connection factory (JMS, MQJMS, WebSphere MQ). – Configure connection pool size (JMS, MQJMS, WebSphere MQ). – Configure service integration bus data buffer sizes. Database – Place database table spaces and logs on a fast disk subsystem. – Place logs on a separate device from the table space containers. – Maintain current indexes on tables. – Update database statistics. – Set log file sizes correctly. – Optimize buffer pool size (DB2) or buffer cache size (Oracle). For example, if file system caching is disabled (the is, direct I/O), set the buffer pool/cache size to at least 2GB. Java – Set the heap and nursery sizes to manage memory efficiently. – Choose the appropriate garbage collection policy (generally, -Xgcpolicy:gencon). – Enable verbosegc to obtain Java memory statistics for later analysis. There is essentially no overhead attributable to enabling verbosegc. Business Monitor – Configure Common Event Infrastructure. – Set message consumption batch size. – Enable key performance indicator (KPI) caching. – Use table-based event delivery. – Enable the data movement service. 4.3 Common tuning parameters This section lists performance tuning parameters commonly used for tuning Business Process Manager solutions, for both BPMN and BPEL business processes. 4.3.1 Tracing and logging flags Tracing and logging are often necessary when setting up a system or debugging issues. However, these capabilities require performance resources that are often significant. Minimize their use when evaluating performance or in production environments. This section lists tracing parameters used in the products covered in this paper. Some settings are common to all or a subset of the products; others are specific to a particular product. Unless stated otherwise, you can set all of these parameters using the administrative console. To enable or disable tracing, click Troubleshooting Logs and Trace in the properties of the subscription. Select the server on which you want to change the log detail levels and click Change Log Detail Levels. Set both the Configuration and Runtime fields to the following value: * =all=disabled To change the Performance Monitoring Infrastructure (PMI) level, click Monitoring and Tuning Performance Monitoring Infrastructure Select the server on which you want to change the log detail levels and click none. 52 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices
In addition, Cross-Component Tracing (XCT) is useful for problem determination, enabling correlation of Service Component Architecture (SCA) component information with log entries. However, do not use XCT in production or while obtaining performance data. Two levels of XCT settings are possible: ► Enable ► Enable with data snapshot Both incur significant performance resource usage. Enable with data snapshot is costly because of the additional I/O involved in saving snapshots in files. To enable or disable XCT, click Troubleshooting Cross-Component Trace. Select the XCT setting from three options under the Configuration or Runtime tab: ► Enable ► Disable ► Enable with data snapshot Changes made on the Runtime tab take effect immediately. Changes made on the Configuration tab require a server restart to take effect. Further information is provided in the “Managing Log Level Settings in TeamWorks” technote: http://www.ibm.com/support/docview.wss?uid=swg21439659 4.3.2 Java memory management tuning parameters This section lists several frequently used Java virtual machine (JVM) memory management tuning parameters. For a complete list, see the JVM tuning guide offered by your JVM supplier. To change the JVM parameters, complete the following steps: 1. Go to the JVM administrative window by first clicking Servers Application Performance Monitoring Infrastructure 2. Select the server on which you want to change the JVM tuning parameters. 3. Click Server Infrastructure Java and Process Management Process Definition Additional Properties Java Virtual Machine. 4. Change the JVM parameters on this panel. Java garbage collection policy The default garbage collection (GC) algorithm on platforms with an <strong>IBM</strong> JVM is a generational concurrent collector (specified with -Xgcpolicy:gencon under the Generic JVM arguments on the JVM administrative console panel). Our internal evaluation shows that this garbage collection policy usually delivers better performance with a tuned nursery size, as described in the next section. Java heap sizes To change the default Java heap sizes, set the initial heap size and maximum heap size explicitly on the JVM window in the administrative console. The 64-bit JVMs (the suggested mode for Business Process Manager servers) support much larger heap sizes than 32-bit JVMs. Use this capability to relieve memory pressure in the Java heap, but always ensure that there is sufficient physical memory to back the JVM heap size and all other memory requirements. Chapter 4. Performance tuning and configuration 53
Page 1:
IBM ® WebSphere ® Front cover IBM
Page 4 and 5:
Note: Before using this information
Page 6 and 7:
3.1.8 Preventing WSDL validation fr
Page 8 and 9:
4.15.4 Sizing log files appropriate
Page 10 and 11:
Trademarks IBM, the IBM logo, and i
Page 12 and 13:
Now you can become a published auth
Page 14 and 15: 1.1 Products covered in this public
Page 16 and 17: 4 IBM Business Process Manager V8.0
Page 18 and 19: 2.1 Top tuning and deployment guide
Page 20 and 21: Two individuals with the following
Page 22 and 23: Turn off auto-tracking in business
Page 24 and 25: Avoid use of anonymous derived type
Page 26 and 27: ► ► Independent Disks (RAID) ad
Page 28 and 29: that can process 10 requests per se
Page 30 and 31: 2.4.2 Use a high-performing browser
Page 32 and 33: Batched inputs: Sending large objec
Page 34 and 35: 2.7 Business Monitor This section d
Page 36 and 37: 3.1 Process Designer development be
Page 38 and 39: 3.1.5 Use sequential system lane ac
Page 40 and 41: 3.2 Integration Designer best pract
Page 42 and 43: 3.2.4 Business object parsing mode
Page 44 and 45: Applications benefiting from lazy p
Page 46 and 47: Business object instance validator
Page 48 and 49: 3.2.6 Business Process Execution La
Page 50 and 51: Client systems that follow a page-f
Page 52 and 53: 3.2.10 Invocation style considerati
Page 54 and 55: If a number of services in a FanOut
Page 56 and 57: Aggregation blocks (FanOut and FanI
Page 58 and 59: ► ► ► - The generated BPEL fl
Page 60 and 61: 4.1 Performance tuning methodology
Page 62 and 63: This information is useful for obta
Page 66 and 67: If you click Generational Concurren
Page 68 and 69: 4.3.7 Messaging engine properties T
Page 70 and 71: ► ► Ensure that database statis
Page 72 and 73: 4.5.8 Define Authentication Alias w
Page 74 and 75: 4.6 Process Center tuning Because a
Page 76 and 77: peak throughput, so if an adapter i
Page 78 and 79: esources (for example, a DB2 databa
Page 80 and 81: Use the following steps to place al
Page 82 and 83: 4.7.5 Clustered topology tuning One
Page 84 and 85: To check the Business Space target
Page 86 and 87: In addition, you can customize the
Page 88 and 89: 4.9.2 Disabling event distribution
Page 90 and 91: This processing and reporting mode
Page 92 and 93: 4.13 General database tuning This s
Page 94 and 95: 4.14 DB2-specific database tuning P
Page 96 and 97: Increasing the primary log file siz
Page 98 and 99: When running clustered applications
Page 100 and 101: Using materialized query tables Whe
Page 102 and 103: 4.15.8 Special considerations for l
Page 104 and 105: 4.16.1 Monitoring garbage collectio
Page 106 and 107: Increasing the maximum size of the
Page 108 and 109: 96 IBM Business Process Manager V8.
Page 110 and 111: 5.1 Business Process Manager server
Page 112 and 113: Tuning variations Microflow: Number
Page 114 and 115:
DB2 database server in three-tiered
Page 116 and 117:
► Set the Maximum Connections pro
Page 118 and 119:
106 IBM Business Process Manager V8
Page 120:
► ► ► ► ► Understanding a
show all

Download PDF (1.3 MB) - IBM Redbooks

Create successful ePaper yourself

Delete template?

Save as template?