Download PDF (1.3 MB) - IBM Redbooks

More documents

Recommendations

Info

When running clustered applications, such as those deployed in the Business Process Choreographer in Business Process Manager V8.0, a value of more than 1000 for MAXAPPLS is possible. Such a value means that at least 4000 pages are allocated for the catalog cache, given default tuning. For the same workload, 500 pages are sufficient: db2 update db config for using catalogcache_sz 500 The default behavior assumes heterogeneous use of database connections. A clustered application typically receives more homogeneous use across connections, allowing a smaller package cache to be effective. Bounding the package cache size frees memory for other more valuable uses. To tune the catalogcache_sz database parameter manually, see the suggestions at the following website: http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc /doc/r0000338.htm 4.14.8 Sizing the database heap appropriately before DB2 9.5 DB2 9.5 and later provides the value of AUTOMATIC tuning of the database heap by default. We suggest using this value when available. To tune the dbheap database parameter manually, see the suggestions documented at the following website: http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc /doc/r0000276.htm 4.14.9 Sizing the log buffer appropriately before DB2 9.7 Before DB2 Version 9.7, the default LOGBUFSZ was only eight pages. We suggest setting this value to 256, which is the default in Version 9.7: db2 update db config for using logbufsz 256 4.14.10 Tuning for BPEL business processes The following website explains the specification of initial DB2 database settings and provides examples of creating SMS table spaces for the BPEDB. It also contains useful links for planning and fine-tuning the BPEDB: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm. websphere.bpc.doc/doc/bpc/t5tuneint_spec_init_db_settings.html The following website explains how to create DB2 databases for Linux, UNIX, and Windows for BPEL business processes. The website gives details about BPEDB creation, including pointers for creating scripts for a production environment: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm. websphere.bpc.doc/doc/bpc/t2codbdb.html 86 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices
4.14.11 Suggestions for Business Monitor This section describes ways to tune and maximize the performance of Business Monitor V8.0. Improving concurrency by setting registry variables DB2 allows you to defer row locks for cursor stability (CS) or read stability (RS) isolation scans in certain cases. This deferral can last until a record is known to satisfy the predicates of a query when row locking is performed during a table or index scan. To improve concurrency, deferring row locking until after determining that a row qualifies for a query might be possible. Usually, concurrency is improved by setting the registry variables DB2_SKIPDELETED to permit scans to unconditionally skip uncommitted deletes, and DB2_SKIPINSERTED to permit scans to unconditionally skip uncommitted inserts. Example 4-4 shows how to enable these two registry variables for the MONITOR database. Example 4-4 Enabling registry values DB2_SKIPDELETED and DB2_SKIPINSERTED db2 connect to MONITOR db2set DB2_SKIPDELETED=ON db2set DB2_SKIPINSERTED=ON Avoiding full transaction log DB2 Health Monitor (HMON) regularly captures information about the database manager, database, table spaces, and tables. It calculates health indicators based on data retrieved from database system monitor elements, the operating system, and the DB2 system. Transactions hang if HMON examines the status for the following table and the transaction occupies the entire transaction log, resulting in an error with SQLCODE 964: .SIBOWNER To prevent this error, you can disable the HMON process by using the following command: db2 update dbm cfg using HEALTH_MON OFF Setting lock timeout properly The LOCKTIMEOUT parameter specifies the number of seconds that an application waits to obtain a lock. This parameter helps avoid global deadlocks for applications. If you set this parameter to 0 (zero), the application does not wait for locks. In this situation, if the lock is unavailable at the time of the request, the application immediately receives a -911 return code. If you set this parameter to -1, lock timeout detection is turned off. A value of 30 seconds might be a good starting value; tune as necessary after setting this value. The following example shows how to set this parameter for the MONITOR database. Example 4-5 Starting value for LOCKTIMEOUT db2 -v update db cfg for MONITOR using LOCKTIMEOUT 30 Limiting event XML to 32 KB where possible Events that are small enough are persisted to a regular VARCHAR column in the incoming events table; large events are persisted to a binary large object (BLOB) column instead. In DB2, the largest VARCHAR column is 32768 bytes. Performance improves considerably when a VARCHAR column is used instead of a BLOB. Chapter 4. Performance tuning and configuration 87
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 64 and 65: ► ► ► ► Messaging and messa
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 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?