Performance tuning goals Some of the goals we want to accomplish through performance tuning include: Remove a bottleneck. Increase existing throughput: Processing a larger or more demanding workload without additional processing cost such as adding new hardware or upgrade existing software. Increase response time: Obtaining faster system response times without additional processing cost. Increase system availability: Extending the availability of a system, thereby increasing productivity of the system. Reduce processing cost: Reducing the number of users or the length of their working hours needed to process existing workload. Performance tuning is a complex and iterative process. It involves establishing quantitative objectives, constant system monitoring, and selective and careful tuning to ensure that the objectives are met over time.
Publication references Many publications have been written about performance tuning for Content Manager, DB2, WebSphere, and AIX. These guides are well written and contain very useful information. Most of the materials presented in this chapter are extractions from and summaries of these publications. The publications are: Database Performance Tuning on AIX, SG24-5511 IBM DB2 Universal Database Version 8.2 Administration Guide: Performance, SC09-4821 DB2 UDB/WebSphere Performance Tuning Guide, SG24-6417 IBM Content Manager v8.3 Performance Tuning Guide http://www.ibm.com/support/docview.wss?uid=swg27006452 CMv8.3 Performance Monitoring and Monitoring Guide http://www.ibm.com/support/docview.wss?uid=swg27006451 CMv8.3 Performance Troubleshooting Guide http://www.ibm.com/support/docview.wss?uid=swg27006450 We include what we think is important for a quick overall view of the performance tuning basics for the Content Manager system. If time allows, we recommend that you read these publications because we found them extremely helpful.
Chapter 3. Performance tuning basics
79