IBM DB2 Content Manager V8.3 Performance Tuning Guide

IBM DB2 Content Manager V8.3 Enterprise EditionPerformance Tuning Guide

Supporting DB2 and Oracle on AIX, Windows, and Solaris

Content Management PerformanceShelton Reese

IBM Executive Services2021 Spring Road #200

Oak Brook, Illinois 60523

© IBM Corporation 2007

Content Manager V8.3 Performance Tuning Guide

ContentsCONTENTS...............................................................................................................................................................2

ABOUT THIS DOCUMENT.......................................................................................................................................4

1. INTRODUCTION.................................................................................................................................................5

1.1 UNDERSTANDING THE CONTENT MANAGER ENVIRONMENT..........................................................................................................51.2 CM PERFORMANCE METHODOLOGY.......................................................................................................................................................6

2. PERFORMANCE TUNING BEST PRACTICES........................................................................................8

2.1 KNOW YOUR PRODUCTION ENVIRONMENT..........................................................................................................................................82.2 THINGS TO CONSIDER FOR SOLUTION ARCHITECTS.........................................................................................................................9

3. CM DATABASE SERVER TUNING..........................................................................................................10

3.1 IBM DB2 ENTERPRISE EDITION PARAMETER TUNING.................................................................................................................103.1.1 Library Server Database.....................................................................................................................103.1.2 Resource Manager Database..............................................................................................................12

3.2 ORACLE 9I DATABASE PARAMETER TUNING....................................................................................................................................143.2.1 Library Server Database.....................................................................................................................143.2.2 Resource Manager Database................................................................................................................17

3.3 OPTIMIZE DATABASES...............................................................................................................................................................................173.3.1 DB2 runstats, rbind, and reorgchk Commands.....................................................................173.3.2 Oracle DBMS_STATS package............................................................................................................18

4. WEB SPHERE APPLICATION SERVER TUNING FOR CM.................................................................19

4.1 RESOURCE MANAGER APPLICATION SERVER TUNING..................................................................................................................194.2 ECLIENT APPLICATION SERVER TUNING.............................................................................................................................................21

5. IBM HTTP SERVER TUNING FOR CM..................................................................................................23

6. OPERATING SYSTEM SPECIFIC............................................................................................................24

6.1 NETWORK TUNING.......................................................................................................................................................................................246.1.1 AIX Network Tuning............................................................................................................................246.1.2 Windows Network Tuning....................................................................................................................246.1.3 Solaris Network Tuning......................................................................................................................28

6.2 DISK I/O AND FILE SYSTEM TUNING....................................................................................................................................................296.2.1 Use External Storage When Possible....................................................................................................296.2.2 Tune UNIX File Systems for External Storage......................................................................................30

6.3 CPU, MEMORY, OS KERNEL AND OTHER SYSTEM RESOURCES...............................................................................................316.3.1 AIX ulimit, maxuproc, and EXTSHM.....................................................................................316.3.2 Windows 2003 Enterprise Edition /3GB, /PAE, and Services...........................................................326.3.3 Solaris ulimit, maxuprc, and kernel parameters...........................................................................36

7. PERFORMANCE MONITORING TOOLS...............................................................................................40

7.1 UNIX MONITORING TOOLS......................................................................................................................................................................407.1.1 CPU Performance..............................................................................................................................407.1.2 I/O Performance..................................................................................................................................417.1.3 Network Performance..........................................................................................................................427.1.4 Memory Usage..................................................................................................................................43

7.1.5 nmon - Automating Resource Monitoring on UNIX..................................................................................................................................................................................................................................................................................................................................................................................................................................................................... 43

of 75



7.2 WINDOWS 2003 MONITORING TOOL - PERFMON................................................................................................................................457.3 WEBSPHERE JVM VERBOSEGC............................................................47

8. TUNING DOWN FOR A DEMO INSTALLATION.........................................................................................49

APPENDIX A. REFERENCES..................................................................................................................................51

APPENDIX B. WORKLOAD AND HARDWARE DESCRIPTION........................................................................52

APPENDIX C. DDL CUSTOMIZATION................................................................................................................53

APPENDIX D. SAMPLE SETTINGS.......................................................................................................................55

APPENDIX E: THANKS.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... 74

of 75



About This DocumentThis publication is intended to help Content Management solution designers and system administrators understand the factors that impact the performance of Content Management applications running on the officially supported platforms. This document provides guidelines for parameter and application tuning for IBM DB2 Content Manager V8.3 Enterprise Edition for DB2 and Oracle on AIX, Windows, and Solaris platforms. Performance tunings for other platforms including z/OS and Linux are included in separate papers. Please visit http://www.ibm.com/support/us for more information.

Performance tuning is affected by many factors, including the workload scenario and the system environment. You should not simply copy the exact values described here, which represent the parameters that had the most performance impact in our testing of IBM DB2 Content Manager V8.3 Enterprise Edition on specific hardware (see Appendix B for the hardware specifications). When tuning your individual systems, remember that it is important to begin with a baseline test and monitor the performance statistics to see if any parameters have made an impact and should be changed.

Shelton Reese (312-635-0198) is a senior consultant for DB2 UDB Servers. In this role, he has worked in a DB2 services consultant role with IBM for a number of years. He has provided on-site assistance with DB2 database and application planning, project planning and execution, large complex OLTP and Decision Support system design, database and application design, and performance tuning, as well as client/server and legacy system integration.

The information contained in this publication was derived under specific operating and environmental conditions. While IBM has reviewed the information for accuracy under the given conditions, the results obtained in your operating environments may vary significantly. Accordingly, IBM does not provide any representations, assurances, guarantees, or warranties regarding performance. Any information about non- IBM ("vendor") products, in this document, has been supplied by the vendor and IBM assumes no responsibility for its accuracy or completeness.

of 75

http://www.ibm.com/support/us



1. Introduction

1.1 Understanding the Content Manager Environment

IBM DB2 Content Manager V8.3 Enterprise Edition is the core of DB2 Content Management software. It manages all types of digitized content including HTML and XML Web content, document images, electronic office documents, printed output, audio, and video.

The system diagram below shows the major components and tools in the Content Manager V8.3 architecture. The servers offer replication to store and manage objects in multiple locations. The Windows Client is the desktop client for high-volume, high-performance applications. The eClient is a browser client, supporting the multi-tier and distributed architecture.

DB2 Content Manager V8.3 Enterprise Edition offers improved scalability to grow from a single department to a geographically dispersed enterprise, openness to support multiple operating systems (including Linux®), databases (including Oracle®), applications and resources, and a powerful and expressive XML-ready data model.

Figure 1. CM V8.3 High-level Architecture

For maximum performance, the different mid-tier and backend servers (i.e., eClient, Library Server and Resource Manager servers) should all reside on separate systems. The primary benefit of having such a configuration is to avoid resource contention from multiple servers residing on a single server. Allowing Content Manager servers to reside on a single machine, though technically feasible, would impact the amount of throughput achieved depending on your workload.

of 75

Windows desktop clients

DB2 Content Manager v8 architecture

Web browser clients

DM__Client

browsers

Windows desktop clients

Middle-tier server(s)

Middle-tier server(s)

Document ___ Manager

Client_for __ Windows

ICM C++ __ API

eClient / portlets

ICM Java API

ICM_____C+

WebSphere

Beans

RMdatabas

LS DB2/ORA database

Migrator

DB2 _________ / _____________ORA_________

Resource Manager(s)

TSMOptical storage

Library Server

WebSphereRM__ servlet

e

_ RM _

filesyste

Replicator

m



The servers for IBM DB2 Content Manager V8.3 Enterprise Edition in our performance test configurations are:

1. A CM V8.3 Library Server machine

2. A CM V8.3 Resource Manager machine

3. A mid-tier server machine with CM V8.3 eClient, for the multi-tier testing

In addition, external storage is used for enhanced disk I/O performance. For a list of hardware used for our testing, please refer to Appendix B for details. An example Windows setup is shown in the following diagram:

Figure 2. Sample Performance Test Setup

1.2 CM Performance Methodology

Performance and scalability cannot be achieved by performance tuning alone, but tuning is one key element of a Content Management application's lifecycle. To build and maintain high performance and scalability requires a full life-cycle performance methodology, from pre-sales through installation to production, with the primary goal of avoiding surprises.

Briefly, the CM Performance Methodology has a five-stage lifecycle. By setting objectives early, performance tuning before going into production, and by establishing processes that monitor key performance metrics, the methodology will help ensure achievement of initial scalability objectives and will also provide information for capacity planning as workloads change and grow.

Planning for performance and scalabilityDocument the projected system topology, the projected workload, and define measurable performance and scalability objectives. Perform initial capacity planning and sizing estimates.

of 75

1Gbps Network

Mid-tier Server

· Windows / AIX / Solaris· WebSphere Application Server 5.1.1· IBM HTTP Server 1.3.28· II4C v8.3 Java OOAPI· eClient or custom mid-tier application

Library Server

· Windows / AIX / Solaris /· DB2 v8.2· CM v8.3 Enterprise Edition

2Gbps SAN

Storage Server

· Windows / AIX / Solaris· WebSphere Application Server 5.1.1· IBM HTTP Server 1.3.28· DB2 v8.2· CM v8.3 Enterprise Edition

· LS database· LS db indexes· LS db logs· RM database· RM db indexes· RM db logs· RM LBOSDATA· RM Staging· Backups

Resource Manager



Solution design choices and performance tradeoffsUnderstand topology choices (types of client, eClient, Document Manager, Client for Windows, custom client), feature choices (e.g. replication, High Availability, text search, versioning, etc) and their performance implications.

Performance tuningPlan for an initial tuning period to maximize confidence and reduce risk, using the tools and techniques from the Monitoring and Troubleshooting phases to meet the objectives set in the Planning phase. Focus on effective tuning of CM server calls, memory, disk I/O, and network bandwidth. The sections that follow provide key parameters in various CM components that will give you the greatest performance impact.

Monitoring and maintaining performanceMaintain a "performance profile" of the workload metrics and resource utilizations on your CM servers. Monitor over time to observe trends before they become a problem. For more information, see the CM V8.3 Performance Monitoring Guide at http://www.ibm.com/support/docview.wss?uid=swg27006451.

Performance troubleshootingWhen performance issues arise, use a disciplined and organized approach to solve the problem using the "performance profile" data and performance tuning guidelines. For more information, see the CM V8.3 Performance Troubleshooting Guide at http://www.ibm.com/support/docview.wss?uid=swg27006450.

of 75

http://www.ibm.com/support/docview.wss?uid=swg27006450.

http://www.ibm.com/support/docview.wss?uid=swg27006451.



2. Performance Tuning Best Practices

2.1 Know Your Production EnvironmentDB2 Content Manager v8.3 Enterprise Edition sets many "production ready" performance tuning parameters right out of the box, especially for the Library Server. But additional tuning will often be required to maximize the performance and scalability of a production system, and you should plan for an initial tuning period to maximize confidence and reduce risk. Performance tuning for a DB2 Content Manager system depends on a coordinated and interdependent tuning of the operating system - the system memory usage, disk I/O activity, CPU usage, and network usage. Library Server, Resource Manager, and middle-tier servers may each have different tuning specifications. Always remember that that performance tuning involves tradeoffs; appropriate tuning techniques and parameter values depend on the unique circumstances of your configuration and workload.

Important: Do not ever simply apply the exact values listed in this Tuning Guide to your production system without first understanding the effect of those parameters and choosing values appropriate for your system, nor make a large number of parameter changes at one time. Effective performance tuning requires a disciplined and organized process:

· Educate yourself by reading this Tuning Guide and the other References, especially the white papers on Performance Troubleshooting and Performance Monitoring and Maintenance.

· Document your tuning objectives with specific and measurable metrics. Stop tuning when the objectives are met.

· If possible, use automated test tools to drive a multi-user test load based on your projected workload.

· Monitor workload (throughput, response times), system resource metrics (CPU, memory, network, I/O), and key CM component performance counters. Review the captured metrics and this Tuning Guide to identify candidate tunings. Focus on tunings appropriate for the current system bottleneck.

· Iterate running the test workload, changing only one tuning parameter at a time. Evaluate the effect before making additional changes. Always document all changes in tuning parameters beyond the product defaults.

The Performance Troubleshooting white paper contains sample worksheets that you can use to organize and document this performance tuning process.

Here are a few examples of commonly applicable performance tuning recommendations:

· Effective use of the CM APIs (for custom clients)o Whenever possible, avoid "stateless" mid-tier clients which log on and off of the CM

backend server for each end-user action, as this can generate a large number of redundant calls to the CM Library Server. Instead, build a mid-tier pool of connections.

· Effective use of memoryo If your Library Server has more than 1GB RAM, consider increasing its bufferpool

sizes o Keep eClient mid-tier and Resource Manager JVM heap sizes limited; if system CPU utilization permits, use multiple JVMs ("cloning”) to fully utilize memory.

· Effective use of disk I/Oo Use external storage devices with large numbers of physical drives, when possible. o Distribute LS database tablespaces, LS database indexes, LS database logs, RM

database, RM database log, RM "lbosdata", RM "staging area", JFS logs (for AIX), andCM log files onto separate striped physical disks.

of 75



o If migrating content to TSM optical backup, migrate to TSM disk and let TSM manage the migration to optical disk.

• Effective use of network bandwidtho In general, set all machines to full duplex, and the MTU size to the maximum.o In geographically distributed environments, consider using LanCache Resource

Managers to keep frequently-accessed objects closer to their users.

2.2 Things To Consider For Solution ArchitectsFor Content Manager solution architects, the following table lists high level solution configuration choices and their performance tradeoffs:

of 75



3. CM Database Server TuningAs shown in Figure 1, in IBM DB2 Content Manager V8.3 Enterprise Edition, two backend database servers are required for core functionality. These servers include database server for the Library Server, and a database server for the Resource Manager. The Library Server is a database application, and the Resource Manager is a WebSphere application requiring its own database. In V8.3, both the Library Server and the Resource Manager databases support DB2 and Oracle.

3.1 IBM DB2 Enterprise Edition Parameter Tuning

For our testing, we used IBM DB2 Enterprise Edition V8.1 Fixpack 7a as our database server on the AIX, Windows, and Solaris platforms. Below are the specified parameters and values used in our environment for both the Library Server and the Resource Manager databases (default database names are icmnlsdb and rmdb, respectively). There are two sets of configuration parameters for tuning DB2. The Database Manager Configuration, or DBM, parameters that apply to the database instance. The Database Configuration, DB, parameters apply to the overall database configuration. The settings are shown here as actual DB2 commands you can run in a shell. You also must save the changes and restart the affected server for some tuning parameters to take effect.

In general, a production database should turn off monitoring switches (e.g., DB2's DFT_MON_BUFPOOL), increase bufferpool sizes, and make sure number of agent processes (e.g., DB2's MAXAGENTS in the database manager, and MAXAPPLS in the database) is set to a greater number than your anticipated number of concurrent users. In a multi-tier environment, the number of database agent processes should be set to a greater number than the sum of all JDBC connection pool sizes. You will see the exact database parameters and the values set in the tested configuration. For exact meanings of these tuning parameters that follow, please refer to the DB2 InfoCenter at http://publib.boulder.ibm.com/infocenter/db2help/index.jsp.

3.1.1 Library Server DatabaseAIX and Solaris

Run the following commands to update dbm parameters:

update dbm cfg using NUMDB 4update dbm cfg using DFT _MON _BUFPOOL OFF update dbm cfg using DFT _MON _LOCK OFF update dbm cfg using DFT _MON _SORT OFF update dbm cfg using DFT _MON _STMT OFF update dbm cfg using DFT _MON _TABLE OFF update dbm cfg using DFT _MON _UOW OFFupdate dbm cfg using DFT _MON _TIMESTAMP OFF update dbm cfg using MON _HEAP _SZ 1000 update dbm cfg using UDF_MEM_SZ 256update dbm cfg using JAVA _HEAP _SZ 256 update dbm cfg using SHEAPTHRES 10000 update dbm cfg using DIR_CACHE YES update dbm cfg using ASLHEAPSZ 150 update dbm cfg using RQRIOBLK 65535 update dbm cfg using QUERY _HEAP _SZ 16384 update dbm cfg using DRDA_HEAP_SZ 128 update dbm cfg using MAXAGENTS 2000

of 75

http://publib.boulder.ibm.com/infocenter/db2help/index.jsp.



update dbm cfg using NUM POOLAGENTS 600update dbm cfg using NUM_INITAGENTS 600

Run the following commands to update the icmnlsdb database parameters:

update db cfg for icmnlsdb using DFT _QUERYOPT 2 update db cfg for icmnlsdb using DBHEAP 1200update db cfg for icmnlsdb using CATALOGCACHE_SZ 64 update db cfg for icmnlsdb using LOGBUFSZ 128 update db cfg for icmnlsdb using UTIL_HEAP_SZ 5000 update db cfg for icmnlsdb using LOCKLIST 1000update db cfg for icmnlsdb using APP_CTL_HEAP_SZ 1000 update db cfg for icmnlsdb using APPGROUP_MEM_SZ 60000 update db cfg for icmnlsdb using SORTHEAP 32update db cfg for icmnlsdb using STMTHEAP 4096 update db cfg for icmnlsdb using APPLHEAPSZ 4096 update db cfg for icmnlsdb using PCKCACHESZ 5000 update db cfg for icmnlsdb using STAT _HEAP _SZ 4384 update db cfg for icmnlsdb using MAXLOCKS 25 update db cfg for icmnlsdb using LOCKTIMEOUT 60 update db cfg for icmnlsdb using CHNGPGS_THRESH 60 update db cfg for icmnlsdb using NUM_IOCLEANERS 4 update db cfg for icmnlsdb using NUM_IOSERVERS 6 update db cfg for icmnlsdb using MAXAPPLS 2000 update db cfg for icmnlsdb using AVG _APPLS 1update db cfg for icmnlsdb using MAXFILOP 64 update db cfg for icmnlsdb using LOGFILSIZ 1000 update db cfg for icmnlsdb using LOGPRIMARY 10 update db cfg for icmnlsdb using LOGSECOND 20

Windows 2003

In the tested Windows 2003 environment, the amount of physical memory limits how many DB2 agent processes can be created. Each agent process occupies a certain number of megabytes of physical memory, so total amount of memory used by all DB2 processes can be roughly calculated as the sum of memory used by the db2syscs.exe and db2fmp processes. So the number is not unlimited.

However, DB2 provides a server-side connection pooling feature called Connection Concentrator. The feature allows a fixed number of agent processes to be defined less than the actual number of database connections, therefore creating a pool of agent processes that are reusable. This feature is used for the high number of concurrent users in the tested environment, and is recommended for any workload.For more information on Connection Concentrator, please visit http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/conn/c0006169.htm.

Update DB2 registry parameters:

db2 set DB2_EVALUNCOMMITTED=YES db2set DB2_FMP_COMM_HEAPSZ=120000 db2set DB2NTMEMSIZE=APLD:30000000 db2set DB2 _HASH _JOIN=NOdb2set DB2_RR_TO_RS=YESdb2 set DB2_GRP_LOOKUP=LOCAL

Update DB2 dbm parameters:

of 75

http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/conn/c0006169.htm.



db2 update dbm cfg using FEDERATED NO db2 update dbm cfg using NUMDB 4db2 update dbm cfg using DFT _MON _BUFPOOL OFF db2 update dbm cfg using DFT _MON _LOCK OFFdb2 update dbm cfg using DFT _MON _SORT OFF db2 update dbm cfg using DFT _MON _STMT OFF db2 update dbm cfg using DFT _MON _TABLE OFF db2 update dbm cfg using DFT _MON _UOW OFFdb2 update dbm cfg using DFT _MON _TIMESTAMP OFF db2 update dbm cfg using MON _HEAP _SZ 1000db2 update dbm cfg using UDF_MEM_SZ 256 db2 update dbm cfg using JAVA _HEAP _SZ 512 db2 update dbm cfg using SHEAPTHRES 10000 db2 update dbm cfg using DIR_CACHE YES db2 update dbm cfg using ASLHEAPSZ 15db2 update dbm cfg using RQRIOBLK 65535db2 update dbm cfg using QUERY _HEAP _SZ 32768 db2 update dbm cfg using DRDA_HEAP_SZ 128 db2 update dbm cfg using MAXAGENTS 230db2 update dbm cfg using NUM_POOLAGENTS -1 db2 update dbm cfg using NUM_INITAGENTS 0 db2 update dbm cfg using MAX _CONNECTIONS 1400

Update DB2 icmnlsdb database parameters:

db2 connect to icmnlsdb user icmadmin using password db2 update db cfg for icmnlsdb using database_memory -1db2 update db cfg for icmnlsdb using appgroup_mem_sz 40000 db2 update db cfg for icmnlsdb using app_ctl_heap_sz 512

(set to 20000 if Connection Concentrator is off) db2 update db cfg for icmnlsdb using applheapsz 2560 db2 update db cfg for icmnlsdb using BUFFPAGE 250db2 update db cfg for icmnlsdb using DFT_PREFETCH_SZ 16 db2 update db cfg for icmnlsdb using SORTHEAP 256db2 update db cfg for icmnlsdb using MAXAPPLS 1400

3.1.2 Resource Manager DatabaseAIX and Solaris

Update dbm parameters:

UPDATE DBM CFG USING NUMDB 4;UPDATE DBM CFG USING DFT _MON _TIMESTAMP OFF HEALTH_MON OFF ;UPDATE DBM CFG USING DFTDBPATH /d04/cm83_db264 ;UPDATE DBM CFG USING MON _HEAP _SZ 1000; UPDATE DBM CFG USING JAVA _HEAP _SZ 256; UPDATE DBM CFG USING SHEAPTHRES 10000; UPDATE DBM CFG USING RQRIOBLK 65535 ; UPDATE DBM CFG USING QUERY _HEAP _SZ 32768;

of 75



UPDATE DBM CFG USING MAXAGENTS 500 NUM_POOLAGENTS 100 NUM_INITAGENTS 100 MAX COORDAGENTS 500 ;

Update rmdb database parameters:

update db cfg for rmdb using DFT _QUERYOPT 2 update db cfg for rmdb using DBHEAP 1200update db cfg for rmdb using CATALOGCACHE_SZ 64 update db cfg for rmdb using LOGBUFSZ 128 update db cfg for rmdb using UTIL_HEAP_SZ 5000 update db cfg for rmdb using LOCKLIST 1000update db cfg for rmdb using APP_CTL_HEAP_SZ 1000 update db cfg for rmdb using SORTHEAP 32update db cfg for rmdb using STMTHEAP 4096 update db cfg for rmdb using APPLHEAPSZ 4096 update db cfg for rmdb using PCKCACHESZ 2000 update db cfg for rmdb using STAT _HEAP _SZ 4384 update db cfg for rmdb using MAXLOCKS 25 update db cfg for rmdb using MINCOMMIT 1 update db cfg for rmdb using LOCKTIMEOUT 60 update db cfg for rmdb using CHNGPGS _THRESH 60 update db cfg for rmdb using NUM_IOCLEANERS 4 update db cfg for rmdb using NUM_IOSERVERS 3 update db cfg for rmdb using MAXAPPLS 600 update db cfg for rmdb using AVG _APPLS 1

Windows 2003Update DB2 registry parameters:

db2 set DB2_EVALUNCOMMITTED=YESdb2set DB2_FMP_COMM_HEAPSZ=60000db2set DB2NTMEMSIZE=APLD:30000000db2set DB2 _HASH _JOIN=NO db2set DB2_RR_TO_RS=YES db2 set DB2_GRP_LOOKUP=LOCAL

Update DB2 dbm parameters:

db2 update dbm cfg using FEDERATED NO db2 update dbm cfg using NUMDB 4db2 update dbm cfg using DFT _MON _BUFPOOL OFF db2 update dbm cfg using DFT _MON _LOCK OFFdb2 update dbm cfg using DFT _MON _SORT OFF db2 update dbm cfg using DFT _MON _STMT OFF db2 update dbm cfg using DFT _MON _TABLE OFF db2 update dbm cfg using DFT _MON _UOW OFFdb2 update dbm cfg using DFT _MON _TIMESTAMP OFF db2 update dbm cfg using MON _HEAP _SZ 1000db2 update dbm cfg using UDF_MEM_SZ 256 db2 update dbm cfg using JAVA _HEAP _SZ 512 db2 update dbm cfg using SHEAPTHRES 10000 db2 update dbm cfg using DIR_CACHE YES db2 update dbm cfg using ASLHEAPSZ 15

of 75



db2 update dbm db2 update dbm db2 update dbm db2 update dbm db2 update dbm db2 update dbm db2 update dbm

cfgcfgcfg

usingusingusing

RQRIOBLK 65535QUERY _HEAP _SZ 32768DRDA_HEAP_SZ 128

cfg using MAXAGENTS 230cfg using NUM_POOLAGENTS 230cfg using NUM_INITAGENTS 0cfg using MAX _CONNECTIONS 500

Update DB2 rmdb database parameters:

db2 connect to rmdb user rmadmin using passworddb2 update db cfg for rmdb using appgroup_mem_sz 40000 db2 update db cfg for rmdb using app _ctl _heap _sz 20000 db2 update db cfg for rmdb using applheapsz 4096db2 update db cfg for rmdb using BUFFPAGE 250db2 update db cfg for rmdb using DFT_PREFETCH_SZ 16 db2 update db cfg for rmdb using SORTHEAP 256db2 update db cfg for rmdb using MAXAPPLS 500

3.2 Oracle 9i Database Parameter TuningFor our Oracle performance testing, we used Oracle Release 9.2.0.6 with the latest operating system and application patches applied on the AIX, Windows, and Solaris platforms. Below are the specified parameters and values used in our environment for both the Library Server and the Resource Manager databases (default database names are icmnlsdb and rmdb, respectively). The settings are shown as modifications to the Oracle parameter file called initicmnlsdb. ora. You also must save the changes and restart the affected server for some tuning parameters to take effect.

3.2.1 Library Server DatabaseAIX and Solaris

Update the parameters in the initicmnlsdb.

#SGA memory and buffer pool parameters

db _block _size = 4096 large_pool_size = 0 java_pool_size = 0pga_aggregate_target = 1500Mdb _cache _size = 600Mshared_pool_size = 600M

#Process limits parameters

enqueue _resources= 180000

processesdb _files = 1024 sessions

=

=

1500

1000



# Optimizer related parameters.

optimizer_index_caching = 99optimizer_index_cost_adj = 15optimizer_max_permutations = 1999

#Cursor related parameters

cursor_sharing = SIMILARsession_cached_cursors = 500open _cursors = 3000cursor_space_for_time = TRUE

#Undo and rollback related parameters.

undo_retention = 7200undo _tablespace = UNDO01

# Logging and tracing parametersbackground_dump_dest = /d17/oradb83/icmnlsdb/bdump user_dump_dest = /d17/oradb83/icmnlsdb/udump core_dump_dest = /d17/oradb83/icmnlsdb/cdump max_dump_file_size = unlimitedlog_checkpoint_interval = 0log_checkpoint_timeout = 0log_buffer = 524288log_parallelism = 4

# Statisticstimed_statistics = true # Misc

compatible = 9.2.0

Windows 2003

Update the parameters in the initicmnlsdb. ora file normally located in D : \ oracle\ ora92\ database:

# Instancedb _block _size = 4096 db _cache _size = 500Mshared_pool_size = 125M large_pool_size = 0 java_pool_size = 0pre _page _sga = true pga_aggregate_target = 500MWORKAREA_S I ZE_PO LI CY=AUTOdb _files = 1024open _cursors = 500 processes = 1000log_checkpoint_interval = 10000log_buffer = 1048576 # Optimizer

of 75



cursor sharing = similarcursor_space_for_time = truelog_checkpoint_interval = 0# Logging to external storagebackground_dump_dest = i :\ icmnlsdb\ icmnlsdb\bdump user_dump_dest = i:\icmnlsdb\icmnlsdb\udump core_dump_dest = i :\ icmnlsdb\ icmnlsdb\ cdump max_dump_file_size = 10240# OracleTextjob_queue_processes = 1# Misccompatible = 9.2.0# cmperf tunedundo_retention = 7200

Additionally for Windows, to allocate more memory for additional extproc.exe processes (spawned by oracle.exe), lower the oras tack values for oracle.exe and the listener.

When memory is low, you may get “04030, 00000, out of process memory when trying to allocate %s bytes (%s,%s) . // Cause: Operating system process private memory has been exhausted.” To help solve this problem, lower the stack memory allocation for oracle.exe and the listener by running the following command:

of 75

To set:

To query:

C:\ oracle9i\bin\ orastack oracle .exe C:\oracle9i\bin\orastack tnslsnr.exe Expect output as follows:

C:\oracle9i\bin\orastack oracle.exe 500000 C:\oracle9i\bin\orastack tnslsnr.exe 500000

(Default is 1MB)



3.2.2 Resource Manager DatabaseFor AIX and Solaris, apply the same settings for Library Server. See the sections above. For Windows, start with default settings. If your workload is causing performance issues on the Resource Manager's Oracle database, apply the same tunings shown in Library Server in the section above.

3.3 Optimize Databases

3.3.1 DB2 runstats, rbind, and reorgchk Commands

The DB2 runs tats command updates statistics that profile the physical characteristics of a database table, along with its associated indexes. Dynamic SQL statements will automatically use these updated statistics, but static SQL statements built inside CM require the DB2 rbind command be run as well. Execution of runstats/rbind should be done on a regular basis as part of regular database maintenance. As your Library Server and Resource Manager databases grow and change, recalculating table statistics is critical to improving database performance and should be done regularly (manually using scripts below or using a cron job). Along with runs tats/rbind, the DB2 reorgchk command should also be run to check to see if a reorganization of certain tables and/or indexes may be warranted.

The following are commands that, first, dynamically determine Library Server database tables that runs tats can run on, and second, a Windows batch file that actually runs the runs tats/rbind commands:

db2 connect to icmnlsdb user <uid> using <password>db2 -x select tabname from syscat.tables where type='T' and tabschema='ICMADMIN' | sed -e "s/ *.$//" | sed -e "s/^/@db2 runstats on table ICMADMIN./" | sed -e "s/$/ with distribution and detailed indexes all/" > .\my_runstats.batecho @db2 connect reset >> .\dostats.batecho @db2rbind icmnlsdb -l .\log.txt all -u <uid> -p <password >>.\my_runstats .bat

The my _runstats .bat file should contain lines similar to the following:

@db2 runstats on table ICMADMIN.ICMSTWORKLISTS with distribution and detailed indexes all @db2 runstats on table ICMADMIN.ICMSTXDOOBJECTS with distribution and detailed indexes all @db2 runstats on table ICMADMIN.ICMSTXDOOBJFACTORY with distribution and detailed indexes all @db2 runstats on table ICMADMIN.ICMUT00200001 with distribution and detailed indexes all

@db2 runstats on table ICMADMIN.ICMUT00201001 with distribution and detailed indexes all

Each line is a runstats command on a table or index. By running the my_runstats.bat program, performance statistics on all Library Server tables will be profiled. The db2rbind command at the end revalidates all packages in the database.

To run DB2 reorgchk command, do the following:

db2 connect to icmnlsdb user <uid> using <password> db2 reorgchk current statistics on table all

The similar commands above apply to the Resource Manager database. Simply change the tabs chema value to 'RMADMIN’. You may also modify the commands slightly to make them work on UNIX. Details are left to the system administrator.

of 75



3.3.2 Oracle DBMS_STATS packageIn Oracle 8.1.5 and higher the DBMS_STATS packages is used for gathering statistics and analyzing tables, and indexes which can optimize database performance. For the CM V8.3 Library Server database, create a text file with the following dbms _stats commands.

File analyze _ls.sql:

execute dbms _stats.gather _schema _stats (ownname=>'ICMADMIN',method_opt=>'FOR ALL COLUMNS SIZE 1', granularity=>'ALL', options=>'GATHER', cascade=>TRUE, degree => 16) ;execute dbms _stats.gather _schema _stats (ownname=>'SYS',method_opt=>'FOR ALL COLUMNS SIZE 1', granularity=>'ALL', options=>'GATHER', cascade=>TRUE, degree => 16) ;execute dbms _stats.gather _schema _stats (ownname=>'SYSTEM',method_opt=>'FOR ALL COLUMNS SIZE 1', granularity=>'ALL', options=>'GATHER', cascade=>TRUE, degree => 16) ;

The three dbms_stats commands above will gather statistics for objects owned by Oracle users SYS, SYSTEM, and ICMADMIN as reflected by the ownname argument. These three commands will gather statistics on all objects. The script shown is specifically for the Library Server where the owner is ICMADMIN. A similar script could be used for the Resource Manager by replacing the ownname argument with the owner of the Resource Manager, typically RMADMIN.

The script can be run from a command line as shown below.

set oracle_sid=icmnlsdb

echo @analyze_ls | sqlplus "/ as sysdba"

of 75



4. WebSphere Application Server Tuning for CMBoth Resource Manager and eClient are WebSphere applications, hence tuning the IBM DB2 Content Manager V8.3 Resource Manager and eClient application servers primarily entails tuning WebSphere Application Server. Below are recommendations of WebSphere parameter tuning for the Resource Manager and eClient application servers, respectively.

For more information on all WebSphere tuning parameters and the meaning of each, see the Tuning Section of the I nfoCenter located at http://www-3.ibm.com/software/webservers/appserv/was/library.

4.1 Resource Manager Application Server Tuning

For our testing, we used WebSphere Application Server V5.1 .1 as the mid-tier server on the AIX, Windows, and Solaris platforms. Here are the specified parameters and values, and how to set them for the Resource Manager application server (default name is icmrm).

Table 1. CM Resource Manager Application Server Tuning

Tuning Parameter Values used for AIX Values used for Solaris Values used for Windows

JVM Settings (WebSphere Administrative Console -> Servers -> Application Servers -> icmrm -> Process Definition -> Java Virtual Machine)

Initial heap size (MB) 1280 1024 1024

Maximum heap size (MB) 1280 1024 1024

Garbage collection options -Xgcpolicy:optavgpause NA -Xgcpolicy:optavgpause

Generic JVM arguments -Xnoclassgc -Xnoclassgc -Xnoclassgc

-server-XX:NewSize=200M-XX:MaxNewSize=200M-XX:SurvivorRatio=1 2

Web Container Service Settings WebSphere Administrative Console -> Servers -> Application Servers -> icmrm -> Web Container - > Thread Pool)

Minimum active threads (in pool) 70 threads 35 threads 75 threads

Maximum active threads (in pool) 70 threads 35 threads 75 threads

Allow threads allocated beyond maximum No no no

Thread inactivity timeout 100 sec. 100 sec. 100 sec.

Maximum (connections) keep alive 135 conn. 25 conn. 25 conn.

Connection backlog 500 conn. 500 conn. 500 conn.

Session (WebSphere Administrative Console -> Servers -> Application Servers -> icmrm -> Web Container -> Session Management)

Session Timeout 10 min 10 min 10 min

Special environmental variables (WebSphere Administrative Console -> Servers -> Application Servers -> icmrm -> Process Definition -> Environment Entries -> New)

of 75

http://www-3.ibm.com/software/webservers/appserv/was/library.




LDR_CNTRL MAXDATA=0x40000000 (None) (None)

Setting the JVM heap size larger than 256MB For the best and most consistent throughput, set the (- Xms) starting minimum and (-Xmx) maximum the same size. Also, remember that the value for the JVM heapsize is directly related to the amount of physical memory for the system. Never set the JVM heap size larger than the physical memory on the system to avoid disk I/O caused by swapping.

Session timeout 10 minutes The default value of Session Timeout is 30 minutes. Reducing this value to a lower number can help reduce memory consumption requirements, allowing a higher user load to be sustained for longer periods of time. Reducing the value too low can interfere with the user experience. Please determine this based on your end user requirements: if they mostly have quick tasks to finish, set this low; if they have long tasks to finish, set this higher.

Class Garbage Collection -Xnoclassgc Using the "-Xnoclassgc" parameter will allow for more class reuse, thus causing less garbage collections to occur.

Servlet engine thread pool size 70 In our testing, we used 70 for both the minimum and maximum settings. Ideally, set this value and monitor the results using the Tivoli Performance Viewer. Increase this value if all the servlet threads are busy most of the time.

Solaris-specific tuning parameters

HotSpot option -server The "server" mode offers higher throughput than the "client" mode, at an expense of slightly longer startup times. We recommend using "server" mode for higher throughput.

Garbage collection tuning: NewSize and MaxNewSize 200M To help optimize Java garbage collection duration and frequency, we set the parameters -XX:NewSize and -XX:MaxNewSize to 200 MB.

Garbage collection tuning: SurvivorRatio 12 To help optimize Java garbage collection duration and frequency, we set the parameter -XX: SurvivorRatio to 12.

The above two Solaris-specific parameters are especially helpful if garbage collection is showing high frequency and takes several seconds to finish under heavy workloads.

AIX-specific tuning parameters

By default, the application server will not start on AIX with a heap size larger than 1GB. To allow larger a JVM heap size, set the environment variable LDR_CNTRL=MAXDATA=0xn0000000 where n is the number of segments you need. For a 2GB heap, use n=2. For 1792MB, use n = 3 and so on. Set it to 0 for 1 .3.x to go to 2560MB. For example, for a 1.5 GB heap:

LDR_CNTRL=MAXDATA=0x4 0000000

The application server will fail to start if this parameter is not set properly (i.e., a 1536MB heap size for JVM without the parameter will not allow you to start the eClient_Server on AIX).

This environment variable is available in AIX 4.3.3.10 and later. If you are using an older 4.3.3 version, you must upgrade to get this support.

of 75



4.2 eClient Application Server Tuning

Table 2. CM eClient Application Server Tuning


JVM Settings (WebSphere Administrative Console -> Servers -> Application Servers -> eClient_Server -> Process Definition -> Java Virtual Machine)

Initial heap size (MB) 1280 1024 1024

Maximum heap size (MB) 1280 1024 1024

Garbage collection options -Xgcpolicy:optavgpause NA -Xgcpolicy:optavgpause

Generic JVM arguments -Xnoclassgc -Xnoclassgc -Xnoclassgc

-XX:NewSize=1 28M-XX:MaxNewSize=1 28M-XX:SurvivorRatio=2-XX:TargetSurvivorRatio=90

Web Container Service Settings:

Minimum active threads (in pool) 140 threads 20 threads 50 threads

Maximum active threads (in pool) 140 threads 30 threads 75 threads

Allow threads allocated beyond maximum no No no

Thread inactivity timeout (sec) 100 100 100

Maximum (connections) keep alive 135 25 25

Connection backlog 500 500 500

Minimum connections 80 for LS DB 25 for LS DB 20 for LS DB45 for Fed DB 25 for Fed DB 20 for Fed DB

Maximum connections 80 for LS DB 25 for LS DB 30 for LS DB45 for Fed DB 25 for Fed DB 30 for Fed DB

Statement cache size 1000 1000 1000

of 75

CM Connection Pooling Settings (WebSphere Administrative Console -> Resources -> JDBC Providers -> eClientJDBC -> Data Sources -> icmnlsdb -> Connection Pools)

JDBC Driver DB2 - db2java.zip; DB2Legacy CL I-based Type 2

Oracle - ojdbc14.jar; Oracle JDBC Driver; URL must be defined in custom properties as, for example, jdbc:oracle:thin:@myhost.stl .i bm.com:1521 :icmnlsdb

DB2 - db2java.zip; DB2 Legacy CL I-based Type 2

Oracle - ojdbc14.jar; Oracle JDBC Driver; URL must be defined in custom properties as, for example, jdbc:oracle:thin:@myhost.stl .i bm.com:1521 :icmnlsdb

DB2 - db2java.zip; DB2 Legacy CL I-based Type 2

Oracle - ojdbc14.jar; Oracle JDBC Driver; URL must be defined in custom properties as, for example, jdbc:oracle:thin:@myhost. stl.ibm.com:1 521 :icmnlsdb

of 75

http://myhost.stl.ibm.com:1/






update cmbpool.ini file JavaPool=DKPoolWAS JavaPool=DKPoolWAS JavaPool=DKPoolWAS(default location JDBCPrefix=jdbc/ JDBCPrefix=jdbc/ JDBCPrefix=jdbc/

DBRepType=ORACLE or DBRepType=ORACLE or DBRepType=ORACLE orUnix: DB2 DB2 DB2

/home/ibmcmad m/cmgmt/connectors

of 75




Windows: c:\IBM\db2cmv8\cmgmt\connectors

Special environmental variables (WebSphere Administrative Console -> Servers -> Application Servers -> eClient_Server -> Process Definition -> Environment Entries -> New)

LDR_CNTRL MAXDATA=0x40000000 (None) (None)

The thread pool parameter "Allow threads allocated beyond maximum" specifies whether the number of threads can increase beyond the maximum size configured for the thread pool. Leaving this parameter "off' puts an upper limit on number of threads can be created per JVM, allowing the system administrator to control the use of system resources. This setting is especially important when multiple application clones are created on a single system.

Statement cache size Increase the Statement Cache Size used by the icmnlsdb (and ICMNLSDB) data sources. Set this value to 500-1000. The statement cache can be monitored using the Tivoli Performance Viewer, to check if it is large enough. Important note: The statement cache size means differently for version 5 data source and for version 4 data source, both supported in WebSphere V5. The recommended values here are for version 4 data source used by eClient, and it is the total number of cached statements for all connections. In version 5 data source, the cache value is this number of unique statements.WebSphere then creates one cache of this size for each connection. The memory usage for version 5 data source can be really large if the number of connection pool is large. See this URL for more information: http://www - 1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=statement+cache&uid=swg21108496&loc=e n US&cs=utf-8&lang=en.

For meaning and impact of other parameters, see the previous section, or refer to the WebSphere InfoCenter for more details:http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/wel come base.html.

of 75

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/wel

http://1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=statement+cache&uid=swg21108496&loc=e



5. IBM HTTP Server Tuning for CMTwo components of the IBM DB2 Content Manager V8.3 architecture include IBM HTTP Server: Resource Manager and eClient Server, see Figure 1. Tuning IBM HTTP Server is to increase throughput while balancing the system resources. IBM HTTP Server in both Resource Manager and eClient Server share the same system in our test, though they can be configured to use a separate system if needed.

IBM HTTP Server settings are set in the configuration file called httpd. conf, normally located on Unix under /usr/IBMHttpServer/conf directory, and on Windows under <installed drive>:\IBM\IBMHttpServer\conf directory. The definition of each parameter is described in the httpd. conf file itself. For more detailed description, visit section 9.4 of the Performance Tuning for Content Manager at http://www.redbooks.ibm.com/redbooks/pdfs/sg246949.pdf.

The tuning parameters apply to both IBM HTTP Server in Resource Manager and eClient Server. Make a backup of the original httpd. conf file, and apply the appropriate parameters listed in the following table:

Table 3. IBM Http Server Tuning for AIX, Solaris, and Windows

MaxClients (UNIX) ThreadsPerChild (Windows)

1000 1000 800 Set this value to the number ofconcurrent users expected. Monitor your system during normal workload to see if this value needs to be changed. Use lower for simple but CPU intensive applications, and higher for more complex, database- intensive applications with more wait time.

KeepAlive NA NA on Enables HTTP persistent connections.Used with MaxKeepAliveRequests.

KeepAliveTimeout (seconds) 10 10 15 Set this parameter similar to theaverage think time for your workload. Higher Keep-Alive Timeout may increase contention for HTTP server processes. If you see "running out of HTTP processes" in the http error log, you may want to decrease this value.

MaxKeepAliveRequests 0 0 0 This allows an unlimited number ofrequests on a single TCP connection.

MaxRequestsPerChild 0 0 0 Do not force a server to exit after ithas served certain number of requests. If your version of Apache and Apache library has no known memory leaks, set this to 0. But if you wish to force the server to exit and be re-created, set this to a relatively high number, e.g., 25000.

StartServers 10 10 NA This makes a pool of servers ready onstartup. Specify this number to match the MaxSpareServersparameter.

MaxSpareServers 10 10 NA This sets the desired maximumnumber of idle child server processes that are ready to take of if the request- taking child dies. The parent process will kill off the excess processes if the number is more thanMaxSpareServers.

of 75

Tuning Parameter Value for AIX Value for Solaris Value for Windows Description of impact

http://www.redbooks.ibm.com/redbooks/pdfs/sg246949.pdf.



6. Operating System Specific

6.1 Network Tuning

Based on the tested private switched 1GB Ethernet, the following network parameters are modified. Please note that, the following is not to suggest that all network parameters are set to these values, but merely make the reader aware that the network is also an entity in the performance environment and bottleneck resolution process.

6.1.1 AIX Network TuningFor AIX, use the no command to set the following TCP layer parameters. These will take effect immediately, improving the network layer performance in high volume environments.

To display a list of current values, use /usr/sbin/no –a. To make these changes permanent, add the following statements to the /etc/rc . net file.

AIX network tuning parameters and values for Library Server and Resource Manager:

/usr/sbin/no -o sb_max=6192000/usr/sbin/no -o tcp_sendspace=4096000 /usr/sbin/no -o tcp_recvspace=4096000 /usr/sbin/no -o udp_sendspace=65536 /usr/sbin/no -o udp_recvspace=655360 /usr/sbin/no -o rfc1323=1/usr/sbin/no -o ipqmaxlen=150/usr/sbin/no -o clean _partial _conns=true

6.1.2 Windows Network TuningFor Windows servers, use the both the network adapter properties and Windows registry to update the TCP layer parameters. If your environment is uniformly Windows platform, make sure all these parameters are set to the same values across all your servers (i.e., Library Server, Resource Manager server, and eClient Server) to optimal network throughput. It is recommended that you restart your server for all these changes to take effect.

of 75



Table 4. Windows 2003 TCP Tuning for CMRegistry Entry Parameter and Value

HKEY _LOCAL _MACHINE\ SYSTEM\ CurrentControlSet\ Services\ T CPIP\Parameters

TcpTimedWaitDelay= 30 (decimal)MaxUserPort= 32768 (dec)KeepAliveInterval= 1 (dec)

HKEY _LOCAL _MACHINE\ SYSTEM\ CurrentControlSet\ Services\ T cpip\ Parameters\ Interfaces\

TcpAckFrequency= 1

Tcpip\ Parameters\ Interfaces\ ID TcpMaxDataretranmissions= 5 (dec)

HKEY _LOCAL _MACHINE\ SYSTEM\ CurrentControlSet\ Services\A FD\ Parameters

"EnableDynamicBacklog"=dword: 00000001 "MinimumDynamicBacklog"=dword: 00000020 "MaximumDynamicBacklog"=dword: 00001000 "DynamicBacklogGrowthDelta"=dword: 00000010

The description of the tuned TCP parameters is as follows:

TcpTimedWaitDelay Determines the time (in seconds) that must elapse before TCP/IP can release a closed connection and reuse its resources. This interval between closure and release is known as the TIME_WAIT state or twice the maximum segment lifetime (2MSL) state. During this time, reopening the connection to the client and server costs less than establishing a new connection. By reducing the value of this entry, TCP/IP can release closed connections faster and provide more resources for new connections. Adjust this parameter if the running application requires rapid release, the creation of new connections, or an adjustment because of a low throughput caused by multiple connections in the TIME_WAIT state.

MaxUserPort Determines the highest port number that TCP/IP can assign when an application requests an available user port from the system.

KeepAliveInterval Determines how often TCP repeats keep-alive transmissions when no response is received.

TcpAckFrequency TCP/IP can be the source of some significant remote method delays. You can increase TCP performance by immediately acknowledging incoming TCP segments, in all situations.

TcpMaxDataretranmissions Determines how many times TCP retransmits an unacknowledged data segment on an existing connection.

MaxConnect Backlog If many connection attempts are received simultaneously, increase the default number of pending connections that are supported by the operating system. Set all four parameters according to the table above, EnableDynamicBacklog, MinimumDynamicBacklog, MaximumDynamicBacklog, and DynamicBacklogGrowthDelta.

of 75



An example of Windows regedit screen is shown as follows:

Figure 3. Windows regedit Screen

Network adapter that implements Network Driver Interface Specification (NDIS) task offload allows offloading checksum calculation to the network adapter hardware. Because checksum calculation is the most expensive function in the networking stack, doing so offers a significant performance advantage by reducing the number of system CPU cycles required per byte. Offload as many tasks shown in your network adapter. The following screen shows an example offloading task configured for our test system:

of 75



Figure 4. Sample Network Adapter Device Driver Settings

of 75



Additionally, for the optimal network throughput for all CM V8.3 servers, the tested environment set the Jumbo MTU to 1500 (to match the Jumbo frames settings in the gigabit network switch), as shown:

Figure 5. Sample Network MTU Setting

Please visit http://www.microsoft.com/whdc/device/network/taskoffload.mspx#EEAA for more network driver information.

6.1.3 Solaris Network TuningFor Solaris, use the ndd command to set the following TCP layer parameters. These will take effect immediately, improving the network layer performance in high volume environments.

To query the value of one or more parameters, give the parameter name(s) to the ndd command, for example:

ndd /dev/udp udp _smallest _anon _port32768ndd /dev/hme link_status link_speed link_mode 1

The following is a list of tuned network parameters and their values:

Solaris network tuning parameters and values for Library Server:

/usr/sbin/ndd -set /dev/tcp tcp_mss_def_ipv4 9216 /usr/sbin/ndd -set /dev/tcp tcp _time _wait _interval 60000/usr/sbin/ndd -set /dev/tcp tcp _fin _wait_2 _flush _interval 67500/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q 65536 /usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q0 65536 /usr/sbin/ndd -set /dev/tcp tcp_xmit_hiwat 65536 /usr/sbin/ndd -set /dev/tcp tcp_recv_hiwat 65536 /usr/sbin/ndd -set /dev/tcp tcp_max_buf 655360 /usr/sbin/ndd -set /dev/udp udp_xmit_hiwat 65536

of 75

http://www.microsoft.com/whdc/device/network/taskoffload.mspx#EEAA



/usr/sbin/ndd -set /dev/udp udp recv hiwat 65536 /usr/sbin/ndd -set /dev/udp udp_max_buf 65536 /usr/sbin/ndd -set /dev/ce adv _1000fdx _cap 1 /usr/sbin/ndd -set /dev/ce adv _1000hdx _cap 0 /usr/sbin/ndd -set /dev/ce adv _100fdx _cap 0 /usr/sbin/ndd -set /dev/ce adv _100hdx _cap 0 /usr/sbin/ndd -set /dev/ce instance 0 /usr/sbin/ndd -set /dev/ce adv _10fdx _cap 0 /usr/sbin/ndd -set /dev/ce adv _10hdx _cap 0

Add the following additional tuning parameters for Resource Manager & eClient Server:

/usr/sbin/ndd -set /dev/tcp tcp _rexmit _interval _initial 500 /usr/sbin/ndd -set /dev/tcp tcp _rexmit _interval_min 200 /usr/sbin/ndd -set /dev/tcp tcp _rexmit _interval_max 4000 /usr/sbin/ndd -set /dev/tcp tcp_ip_abort_interval 60000 /usr/sbin/ndd -set /dev/tcp tcp _keepalive _interval 300000 /usr/sbin/ndd -set /dev/tcp tcp _smallest_anon_port 1024 /usr/sbin/ndd -set /dev/tcp tcp _slow _start _initial 2 /usr/sbin/ndd -set /dev/tcp tcp _deferred _ack _interval 50

To make these changes permanent, add these statements to the /etc/rc.2/S69inet file.

6.2 Disk I/O and File System Tuning

6.2.1 Use External Storage When PossibleExternal storage device delivers disk performance and reliability (RAID-protected) for demanding applications in data-intensive computing environments. Internal built-in disks should be used only for operating systems and program object files. In the tested CM V8.3 environment, fibre channel disk storage is used for the following application files:

· Library Server database· Library Server database indexes· Library Server database log files· Resource Manager database· Resource Manager database indexes· Resource Manager log files· Resource Manager LBOSDATA directory· Resource Manager Staging directory· Backup directories

In the IBM DS4500 (formerly FAStT900) storage used in the tested environment, set the recommended properties in the Storage Manager Client to match the purpose of your server - database for Library Server and Resource Manager databases, and file system for Resource Manager LOBSDATA files and other log files. You may also choose "Custom" if you have set your database file segment size to numbers other than the default value shown:

of 75



Figure 6. IBM FastT 900 Logical Drive Definition Screen

In addition, ensure the cache settings in FAStT900 from the default values to the recommend values below:

Setting Default RecommendedStart Flushing 80 51Stop Flushing 80 0Cache Block Size 4K 16K

6.2.2 Tune UNIX File Systems for External StorageThe following lists several available UNIX file system parameters that should be modified according to your expected workload and the dynamics of your environment. These settings allow you to take advantage of caching, throughput optimization, and performance of UNIX attached external storage device.

File system tuning parameter and value for AIX Direct I/O: dio

Update the /etc/filesystems as in the example file system called /lsdb:

/ ls db:

dev = /dev/lsvolvfs = jfs2log = INLINEmount = trueoptions = dio,rw account = false

of 75



Similarly for Solaris, update the /etc/vfstab file and apply the forcedirectio and noatime parameters. For example:

/dev/dsk/c8t2d2s0 /dev/rdsk/c8t2d2s0 /d07 ufs 2 yes noatime,forcedirectio

Enabling file system direct I/O, on AIX or Solaris, allows the file system buffer cache to be bypassed which eliminates the double buffering of data which can adversely affect file system I/O performance.

For changes to take effect, you may run mount –a, if the file system you are modifying is not mounted. If the file system is mounted it will need to be unmounted and then remounted or a system reboot will need to be executed.

If I/O performance is of the utmost importance, then the utilization of raw devices for database files should be considered.

The –noatime mount option can improve I/O performance in some cases, for example directories with many files, by not updating the access time of the file. When –noatime is not specified; every time a file is accessed the files inode information is updated to reflect the last access time which incurs a write to the file system metadata.

6

.3 CPU, Memory, OS Kernel and Other System Resources

6.3.1 AIX ulimit, maxuproc, and EXTSHM

6.3.1.1 File Descriptors ulimitThis specifies the number of open files permitted. If this value is set too low, a memory allocation error will occur on AIX and a too many files open will be logged to the to the stderr log file. Set this value higher than the default system value. For large SMP machines, set to unlimited.

To display the current value, use the command:

ulimit –a

To change to a different value, use the command, and use -1 for unlimited:ulimit –n <new _value> ulimit –n -1<must reboot the system>

You may also change the settings in the /etc/security/limits file. But changes in the file are system wide limits, not just limits taken on by a user (e.g., db2inst1).

6.3.1.2 Maximum Number of Processes Per User maxuprocTo displays max number of processes per user:

lsattr -D -l sys0 -a maxuproc

To set it to a different value:

of 75

chdev -l sys0 -a maxuproc='4096' <must reboot the system>

of 75



With a low number of maxuproc setting, you may get DB2 error "SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command." For a production system that handles a high number of concurrent users, it is recommended to set this parameter to at least 4096.

6.3.1.3 Shared Memory Segments EXTSHMUnder a large workload, the DB2 process running on AIX may run out of memory segments. It is highly recommended for users on AIX version 4.2.1 or newer, to set the environment variable EXTHSM to ON to increase the number of shared memory segments to which a single process can be attached.

If the EXTHSM environment variable is missing, a severe error reported by the DB2 database manager in the db2diag. log is shown below:

RETCODE : ECF=0x90000049=-1879048119=ECF _MEM _EXCEED _MAX _SEGMENTSThe number of shared memory segments attached to the calling process

exceeds the system-imposed limit

2005-04-19-11.07.47.353763-420 I71007716C393 LEVEL: SeverePID : 113308 TID : 12357 PROC : javaINSTANCE: db2inst1 NODE : 000FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr2, probe:201 DATA #1 : Hexdump, 20 bytes0x68EFB790 : FFFF FFFF FFFF FFFF 0000 0000 5CD2 000E \0x68EFB7A0 : 0004 0000

To set the EXTHSM environment variable, add the following line to file ~db2inst1/sqllib/userprofile:

EXTSHM=ON export EXTHSM

Then set the DB2 registry variable DB2ENVLIST to include the variable:

db2set DB2ENVLIST=EXTSHM

6.3.2 Windows 2003 Enterprise Edition /3GB, /PAE, and Services

6.3.2.1 The /3GB boot.ini parameter

By default, the 32-bit editions of Windows can address a total of 4 GB of virtual address space. This is the limitation of the 32-bit architecture. Normally, 2 GB of this is reserved for the operating system kernel requirements (privileged-mode) and the other 2 GB is reserved for application (user-mode) requirements. Under normal circumstances, this creates a 2 GB per-process address limitation. For Content Manager for DB2, the user-mode process affected is db2syscs .exe, and for Oracle, the affected process isoracle .exe.

Windows provides a /3GB parameter to be added to the BOOT.INI file that reallocates 3 GB of memory to be available for user-mode applications and reduces the amount of memory for the system kernel to 1 GB.Both DB2 and Oracle can derive performance benefits from having large amounts of addressable memory available for creating agent processes that handle a large number of concurrent database connections.

To edit the BOOT.INI file to make this change, complete the following steps:

1. Open the System Control Panel.

of 75



2. Select the Advanced tab.3. In the Startup and Recovery frame, click the Settings button.4. Click Edit. Notepad opens to edit the current BOOT.INI file.5. Edit the current ARC path to include the /3GB switch in the same line that has /fastdetect.6. Restart the server for the change to take affect.

Figure 7. Windows 2003 boot.ini Settings

6.3.2.2 The /PAE boot. ini parameterMany SMP servers come with more than 4GB RAM, but the Windows operating system may not "see" the total RAM if the /PAE switch is not set in the boot.ini.

The native 32-bit architecture of the x86 processor allows a maximum addressable memory space of 4 GB. The Intel Physical Address Extension (PAE) is a 36-bit memory addressing mode that allows 32-bit systems to address memory above 4 GB. PAE requires appropriate hardware and operating system support to be implemented. Intel introduced PAE 36-bit physical addressing with the Intel Pentium® Pro processor. Windows supported PAE since Windows NT Server 4.0 Enterprise Edition, and it is supported with the Advanced and Datacenter Editions of Windows Specify "/PAE" in boot.ini to allow full use of 8GB physical RAM.

To edit the BOOT.INI file to make this change, complete the following steps:

1. Open the System Control Panel.2. Select the Advanced tab.3. In the Startup and Recovery frame, click the Settings button.4. Click Edit. Notepad opens to edit the current BOOT.INI file.

of 75



5. Edit the current ARC path to include the /PAE switch in the same line that has /fastdetect.6. Restart the server for the change to take affect.

You should see the amount of RAM to be 8GB in the System Properties settings, as in the following example:

Figure 8. Windows 2003 System Summary

6.3.2.3 Disable Unnecessary Windows servicesWhen Windows is first installed, many services are enabled that may not be necessary for a particular server. Inexperienced users may also inadvertently add additional services that are not actually required for a given system. Each service requires system resources and as a result it is best to disable non-required services to improve performance.

To view the services running in Windows, complete the following steps:

1. Right-click My Computer and select Manage.2. Expand the Services and Applications icon.3. Select the Services icon.

of 75



Figure 9. Sample Display of Disabled Windows Services

You may sort the Services by clicking on the "Startup… " column. The table below is a list of recommended services to disable or set to manual startup.

Table 5. Recommended Windows Services and Startup Settings

Service Default Startup Setting Recommended Setting

Alerter Automatic Disabled

of 75

Distributed file system Automatic Disabled

Distributed link tracking client Automatic Disabled

Distributed transaction coordinator Automatic Manual

DNS Client Automatic Disabled

Application Management Manual Disabled

Automatic Updates Automatic Manual

Background Intelligent Automatic Disabled

Clipbook Disabled Disabled

Computer Browser Automatic Disabled

DHCP Server Manual Disabled



For more Windows Server 2003 tuning tips, refer to the IBM RedPaper on "Tuning Windows Server 2003 on IBM eServer xSeries Servers" at http://www.redbooks.ibm.com/redpieces/abstracts/redp3943.html.

6.3.3 Solaris ulimit, maxuprc, and kernel parameters

6.3.3.1 Solaris File Descriptors ulimitThis parameter specifies the number of open files permitted. If the value of this parameter is too low, a "Too many files open" error displays in the WebSphere Application Server stderr.log (this applies to Resource Manager and eClient Server).

Use the ulimit -a command to display the current values for all limitations on system resources, and ulimit —n <number> command to set or change, as follows:

ulimit -a

ulimit –n <new_value> ulimit –n -1<must reboot the system>

of 75

Service Default Startup Setting Recommended Setting

Error Reporting Service Automatic Disabled

Fax Service Manual Disabled

File Replication Manual Disabled

File Server for Macintosh Manual Disabled

Help and Support Automatic Disabled

HTTP SSL Manual Disabled

Infrared Monitor Automatic Disabled

Intersite messaging Manual Disabled

License Logging Manual Disabled

Logical Disk Manager Automatic Manual

Message Queuing Automatic Disabled

Messenger Automatic Disabled

Portable Media Serial Number Service Manual Disabled

Shell Hardware Detection Automatic Disabled

SNMP Service Manual Disabled

Windows Audio Automatic Disabled

Wireless Configuration Automatic Disabled

http://www.redbooks.ibm.com/redpieces/abstracts/redp3943.html.



Recommended value is unlimited if a system has plenty of resources, 2000 at least for a system that shares resource with other applications.

6.3.3.2 Maximum Number of Processes Per User maxuprcThe Solaris equivalent to the AIX kernel tunable maxuproc is maxuprc. As with all Solaris tunable parameters the value for maxuprc can be set within the file /etc/system. The example here sets the value of maxuprc to 8192.

set maxuprc = 8192

6.3.3.3 Kernel Parameters

Solaris kernel parameters can be tuned to improve an application's performance. DB2 and WebSphere, for example, recommend that you update the Solaris IPC configuration parameters to make better use of available resources.

DB2 UDB provides the db2osconf command to suggest recommended IPC kernel parameters. Run the command in a shell Windows:

db2osconf

For the tested environment here are the reported recommendations for the Library Server system (Solaris 9):

set msgsys:msginfo _msgmax = 65535 set msgsys:msginfo_msgmnb = 65535 set msgsys:msginfo_msgmni = 7168 set msgsys:msginfo_msgtql = 7168 set msgsys:msginfo_msgssz = 16 set msgsys:msginfo _msgseg = 32767

set semsys:seminfo _semmni = 8192 set semsys:seminfo _semmns = 17204 set semsys:seminfo _semmnu = 8192 set semsys:seminfo _semume = 240 set semsys:seminfo _semmap = 1026 set semsys:seminfo _semopm = 200 set semsys:seminfo _semmsl = 200 set semsys:seminfo _semvmx = 32767

set semsys:seminfo _semmap = 1026set semsys:seminfo _semopm = 200set shmsys:shminfo _shmmax = 30074587545 set shmsys:shminfo _shmmax = 15037293773 set shmsys:shminfo _shmmni = 8192set shmsys:shminfo _shmseg = 240set shmsys:shminfo _shmmin = 1

You must have root authority to modify kernel parameters. To set these kernel parameters, add these lines at the end of the /etc/sys tem file. Reboot the system for the changes to take effect.

of 75



WebSphere recommends a slightly different set of values for Solaris kernel parameters (Solaris 9):

set shmsys:shminfo _shmmax = 5000000000 set shmsys:shminfo _shmmni = 2048set shmsys:shminfo _shmseg = 1500

set semsys:seminfo _semaem = 16384 set semsys:seminfo _semmni = 2048 set semsys:seminfo _semmap = 2050 set semsys:seminfo _semmns = 18000 set semsys:seminfo _semmsl = 200 set semsys:seminfo _semopm = 100 set semsys:seminfo _semmnu = 3000 set semsys:seminfo _semume = 256

set msgsys:msginfo_msgmap = 3500 set msgsys:msginfo _msgmax = 140000 set msgsys:msginfo_msgmnb = 65535 set msgsys:msginfo_msgtql = 1792 set msgsys:msginfo _msgseg = 32767 set msgsys:msginfo_msgmni = 256 set msgsys:msginfo_msgssz = 32

set rlim_fd_cur=1024 set rlim_fd_max=34000

If DB2 and WebSphere are required on the same system, as is the case for the Resource Manager component of Content Manager V8.3, ensure that the larger of the values are selected for the kernel parameter settings (again, for DB2, use the db2osconf command to recommend the set of values).

For the tested environment here are the reported recommendations for the Resource Manager system (Solaris 9):

set msgsys:msginfo _msgmax = 65535 set msgsys:msginfo_msgmnb = 65535 set msgsys:msginfo_msgmni = 6144 set msgsys:msginfo_msgtql = 6144 set msgsys:msginfo_msgssz = 32 set msgsys:msginfo _msgseg = 32767

set semsys:seminfo _semmni = 6144 set semsys:seminfo _semmns = 15052 set semsys:seminfo _semmnu = 7168 set semsys:seminfo _semume = 240 set semsys:seminfo _semmap = 1026 set semsys:seminfo _semopm = 200 set shmsys:shminfo _shmmin = 1set semsys:seminfo _semmsl = 200 set semsys:seminfo _semvmx = 32767

set shmsys:shminfo _shmmax = 22502876774 set shmsys:shminfo _shmmni = 7168set shmsys:shminfo _shmseg = 240

of 75



For more DB2 Solaris tuning information, visit http://publib.boulder.ibm.com/infocenter/tiv3help/index.jsp?topic=/com.ibm.tivoli.tio.doc/soli/TIO Install 3125. htm

For more WebSphere Solaris tuning information, visit http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae /tprf tuneopsys.html For a complete list of the Solaris tunable kernel parameters, visit http://docsun.cites.uiuc.edu/sun docs/C/solaris 9/SU NWaadm/SOLTU N EPARAM REF/toc.html

of 75

http://docsun.cites.uiuc.edu/sun

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tprf

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tprf

http://publib.boulder.ibm.com/infocenter/tiv3help/index.jsp?topic=/com.ibm.tivoli.tio.doc/soli/TIO

http://publib.boulder.ibm.com/infocenter/tiv3help/index.jsp?topic=/com.ibm.tivoli.tio.doc/soli/TIO



7. Performance Monitoring ToolsBecause a Content Manager system is composed of multiple components - Library Server, Resource Manager, and optionally one or more Mid-tier (eClient) Servers, and each component uses different software such as DB2, WebSphere, Tivoli Storage Manager, the operating system itself, and others, one is given many tuning and performance monitoring tools. This section highlights the important ones that are used in the tested environment. System administrators may find other tools which are not listed here also useful. The purpose is to give you an overview of what are provided by the operating systems and the software used in a CM V8.3 setup.

7

.1 UNIX Monitoring Tools

7.1.1 CPU Performance

AIX (to take 100 snapshots every 5 seconds) # sar -u 5 100AIX othello 1 5 000C30AD4C00 06/17/05

12:38:09 %usr %sys %wio %idle12:38:24 12 1 1 8512:38:39 26 2 0 7212:38:54 9 2 1 89

Solaris (to take 100 snapshots every 5 seconds) sar 5 100

SunOS cage 5.9 Generic _118558-05 sun4u 07/12/2005

15:31:07 %usr %sys %wio %idle15:31:12 0 0 0 10015:31:17 1 0 0 9915:31:22 0 0 0 10015:31:27 0 0 0 100

An alternate tool to monitor CPU utilization on Solaris is the mpstat command. The mpstat command reports CPU utilization on a per CPU basis as well as extended statistics such as context switches, interrupts, etc. The mpstat command is invoked in the following manner:

mpstat 5 5 will take 5 samples every 5 seconds.

Below is a example of the mpstat command output:

mpstat 5 100CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl2 14 0 26 5 1 60 2 3 9 0 170 1 1 0 993 15 0 22 28 24 62 1 2 10 0 142 1 1 0 9934 19 0 24 193 14 65 1 2 11 0 153 1 1 0 99

of 75



35 17 0 26 5 1 67 2 3 11 0 152 1 1 0 9966 17 0 25 89 1 69 2 2 10 0 154 1 1 0 9967 15 0 23 5 1 68 2 2 10 0 149 1 1 0 9998 14 0 23 5 1 66 2 2 10 0 148 1 1 0 9999 14 0 23 5 1 101 2 2 10 0 149 1 0 0 99

130 14 0 26 5 1 66 2 2 11 0 137 1 0 0 99131 14 0 22 5 1 67 2 2 11 0 140 1 0 0 99162 15 0 22 5 1 67 2 2 10 0 144 1 0 0 99

7.1.2 I/O PerformanceBelow are sample outputs of the iostat command on AIX and Solaris. The reports are dissimilar for each Operating system. On AIX the iostat command with the –a option is more useful that the default output. The –a option will give I/O statistics on a per adapter basis.

AIX# iostat -a

System configuration: lcpu=4 disk=12

tty: tin tout avg-cpu: % user % sys % idle % iowait0.0 0.0 0.2 0.5 99.2 0.1

Adapter: Kbps tps Kb _read Kb_wrtnscsi0 5.2 1.2 196495 2154064

Paths/Disk: % tm_act Kbps tps Kb _read Kb_wrtn

hdisk1_Path0 0.0 0.0 0.0 0 0hdisk2_Path0 0.0 0.0 0.0 7397 4hdisk3_Path0 0.0 0.0 0.0 2199 28hdisk0_Path0 0.7 5.2 1.2 186899 2154032

Adapter: Kbps tps Kb _read Kb_wrtn

fcs0 11.8 1.3 110301 5166084

Paths/Disk: % tm_act Kbps tps Kb_read Kb_wrtn

vpath1_hdisk17 0.0 0.7 0.2 22729 282512vpath1_hdisk13 0.0 0.7 0.2 17239 281396vpath0_hdisk16 0.0 2.3 0.2 7217 1006120vpath0_hdisk12 0.0 2.3 0.2 8758 1010056vpath3_hdisk19 0.0 2.3 0.2 22024 1006064vpath2_hdisk14 0.0 0.6 0.2 8980 281792vpath3_hdisk15 0.0 2.3 0.2 14352 1016480vpath2_hdisk18 0.0 0.6 0.2 9002 281664

of 75



The Solaris iostat command has extensive options that will assist in monitoring I/O devices. The command below uses the –x option which gives extended statistics but there are many more arguments that can be utilized.Solaris# iostat

device

-x

extended device statisticsr/s w/s kr/s kw/s wait actv svc_t %w %b

sd15 0.0 0.0 0.0 0.0 0.0 0.0 2.4 0 0sd16 0.0 0.0 0.0 0.0 0.0 0.0 2.4 0 0sd17 3.7 0.6 9.2 5.1 0.0 0.0 1.3 0 0sd45 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0sd46 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0sd47 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0sd75 0.0 0.0 0.0 0.0 0.0 0.0 1.4 0 0sd76 0.0 0.0 0.0 0.0 0.0 0.0 1.6 0 0sd105 0.0 0.0 0.0 0.0 0.0 0.0 1.3 0 0sd106 0.0 0.0 0.0 0.0 0.0 0.0 1.3 0 0sd107 0.0 0.0 0.0 0.0 0.0 0.0 1.3 0 0sd136 0.0 3.1 0.0 12.6 0.0 0.0 0.6 0 0sd137 0.0 0.0 0.0 0.0 0.0 0.0 0.3 0 0sd139 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0sd140 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0sd2315 0.0 0.0 0.0 0.0 0.0 0.0 0.4 0 0sd2316 0.0 0.0 2.9 0.0 0.0 0.0 13.8 0 0sd2317 0.3 3.7 2.1 26.5 0.0 0.0 1.4 0 0sd2442 0.0 0.0 0.0 0.0 0.0 0.0 0.2 0 0sd2443 0.0 0.0 0.0 0.0 0.0 0.0 0.3 0 0

7.1.3 Network PerformanceAIX (snapshot every 5 seconds on the en0 adapter)

# netstat -I en0 5input (en0) output input (Total) outputpackets errs packets errs colls packets errs packets errs colls260984 0 128140 0 0 514023 0 405638 0 0342 0 331 0 0 342 0 331 0 0837 0 828 0 0 837 0 828 0 0671 0 670 0 0 673 0 672 0 0Solaris (snapshot every 5 seconds on the ce8 adapter)# netstat -I ce8 5

input ce8 output input (Total) outputpackets errs packets errs colls packets errs packets errs colls39248977 0 39931746 0 0 39739399 0 40422168 0 07 0 0 0 0 7 0 0 0 06 0 0 0 0 6 0 0 0 07 0 3 0 0 7 0 31 0 08 0 0 0 0 8 0 0 0 09 0 0 0 0 9 0 0 0 05 0 0 0 0 5 0 0 0 0

of 75



7.1.4 Memory UsageAIX usage(snapshot every 5 seconds)# vmstat 5System Configuration: lcpu=4 mem=14336MBkthr memory page faults cpu

r b avm fre re pi po fr sr cy in sy cs us sy id wa1 1 772314 2075422 0 0 0 0 0 0 575 810 242 0 1 99 00 0 772156 2075580 0 0 0 0 0 0 579 579 214 0 1 99 00 0 772414 2075321 0 0 0 0 0 0 571 1034 198 0 0 99 00 0 772006 2075730 0 0 0 0 0 0 560 1060 163 0 0 99 00 0 772006 2075730 0 0 0 0 0 0 562 521 165 0 1 99 0

Solaris usage(snapshot every 5 seconds)

# vmstat 5kthr memory pager b w swap free re mf pi po fr

de

disk sr s1 s1 s1

faults s4 in

cpusy cs us sy id

0 0 0 39372952 28946544 127 2729 2 2 0 0 0 0 4 0 8032498 1152 1 1 990 0 0 43181064 29508744 0 1 0 0 0 0 0 0 0 0 0 384 559 328 0 0 1000 0 0 43179664 29508112 232 53616 0 0 0 0 0 0 8 0 6162286 361 1 1 990 0 0 43181064 29508744 0 0 0 0 0 0 0 0 0 0 0 379 774 326 0 0 1000 0 0 43179648 29508096 232 53616 0 0 0 0 0 0 8 0 6182304 366 1 1 99

7.1.5 nmon - Automating Resource Monitoring on UNIXIt helps to automate the resource utilization collection during a performance test, or in a production environment. IBM offers a free tool called nmon that allows you to do just that. The nmon tool runs on AIX and Linux platforms. The tool is designed to collect and analyze (with the nmon analyzer Excel spreadsheet) AIX performance data including

· CPU utilization· Memory use· Kernel statistics and run queue information· Disks I/O rates, transfers, and read/write ratios· Free space on file systems· Disk adapters· Network I/O rates, transfers, and read/write ratios· Paging space and paging rates· CPU and AIX specification· Top processors· IBM HTTP web cache· User defined disk groups· Machine details and resources· Async I/O· Workload Manager· ESS disks· NFS· Dynamic LPAR changes

of 75



To start the nmon process and log entries to a file, use:

nmon -f -s 15 -c 120

The above command logs performance statistics every 15 seconds for 120 intervals (or (15*120)/60 = 30 minutes), to a file called <hostname>_date_time.nmon in the running directory. You may want to run this with the nohup option if you need to log out of the system.

When the tool finishes, you run the sort command to sort and generate a comma delimited file for use by the Excel nmon analyzer:

sort -A mymachine _311201 _1030.nmon > res _usage _test1.csv

Open the Excel spreadsheet called nmon analyzer v301 . xls, and load the .csv file generated above:

Figure 10. The nmon Analyzer Excel Spreadsheet

After analysis, save the output file as a regular Excel file. In the output file, resource utilization is listed under each tab. The first sheet is the summary sheet. Below are examples of the generated output:

of 75



Figure 11. Sample Resource Usage Summary reported by nmon

Visit http://www-128.ibm.com/developerworks/eserver/articles/nmon.html for downloads and documentation on nmon.

7.2 Windows 2003 Monitoring Tool - perfmon

The Windows Performance Monitor (perfmon . exe) is the best tool for monitoring the operation system resource utilization. You can monitor live or output the entries (for a given interval) to a file for later analysis. The perfmon tool is a light-weight process, so it is recommended that you monitor all the counters for the following performance objects:

· processor· memory· network interface· physical disk· process A counter log file should be created so that entries are logged into a file for later analysis.

You can create either a binary file or a comma delimited file — both can be read by the perfmon tool, but the latter can alsobe loaded into a spreadsheet for manual analysis and graphing.

To start perfmon, go to Start -> Run... -> Type "perfmon" in the text box, and hit Enter.

The following screen shows how a counter log is created (repeat this for the above listed objects):

of 75

http://www-128.ibm.com/developerworks/eserver/articles/nmon.html



Figure 12. Windows perfmon Add Counters Screen

After a test, you can load the counter log file, and choose the time interval for which you are interested in (click on "Time Range"):

Figure 13. Windows perfmon post analysis

The averages of the resource utilization will be re-calculated based on the time range you choose:

of 75



Figure 14. Sample Windows Resource Usage Post Analysis

Visit http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/optimize/perftune.mspx#XSLTsecti on130121120120 for more information on perfmon objects and Windows tuning.

7.3 WebSphere JVM verbosegcFor WebSphere applications, such as Resource Manager, eClient Server or a customized mid-tier application, monitoring the memory usage is critical in tuning the performance. The "-verbose: gc" option in the JVM setting logs garbage collection output to the stderr. log of the application server. Verbose gc outputs are similar to the following:

<AF[ 43] : Allocation Failure. need 524 bytes, 0 ms since last AF><AF[ 43] : managing allocation failure, action=0 (1057927024/1073740288)> <GC(43) : GC cycle started Wed Jul 06 10:58:42 2005<GC(43) : freed 6294968 bytes, 45% free (1064221992/1073740288), in 61 ms> <GC(43) : mark: 53 ms, sweep: 8 ms, compact: 0 ms><GC(43): refs: soft 0 (age >= 32), weak 0, final 23, phantom 0>

<AF[ 43] : completed in 75 ms>

A "healthy' JVM under a workload should keep the free memory percentage somewhat constant. It decreases then increases after garbage collection is done. If the 45% free (1064221992/1073740288) percentage goes down over time to near zero, the JVM may hang or report "out of memory" error, an indication that your application either has a large memory footprint or has memory leaks. More debugging is needed to determine what is causing the problem.

of 75

http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/optimize/perftune.mspx#XSLTsecti



Visit http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0407shah/index.html for more information on performance tuning and debugging methodology for Content Manager applications.

of 75

http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0407shah/index.html



8. Tuning Down for a Demo InstallationIBM DB2 Content Manager V8.3 Enterprise Edition sets many "production-ready" performance parameters by default. However, these new default parameters can sometimes be excessive for a single-machine "demo system" such as a laptop or a "proof of concept" machine, especially when memory is limited (less than 1GB). The following steps will modify some of the underlying system attributes to reduce the memory usage and improve the user experience on a demo system.

To query current DB2 instance, database bufferpool sizes, use the following commands:

Library Server database

db2 get dbm cfg > db2dbm.cfg, the file db2dbm.cfg will contain all dbm parameters, look for:

Query heap size (4KB) (QUERY_HEAP_SZ) = 32768Sort heap threshold (4KB) (SHEAPTHRES) = 10000Max number of existing agents (MAXAGENTS) = 500

db2 connect to icmnlsdb user demo1 using demo4youdb2 get db cfg for icmnlsdb > ls.cfg, the file ls.cfg should contain the following entries:

Max appl. control heap size (4KB) (APP_CTL_HEAP_SZ) = 1024Max storage for lock list (4KB) (LOCKLIST) = 1000SQL statement heap (4KB) (STMTHEAP) = 16384Sort list heap (4KB) (SORTHEAP) = 256Max number of active applications (MAXAPPLS) = 200

db2 connect to icmnlsdb user demo1 using demo4youdb2 select * from syscat.bufferpools > lsbp.cfg, the file should contain bufferpool sizes:

ICMLSFREQBP4 1000ICMLSVOLATILEBP4 8000ICMLSMAINBP32 8000CMBMAIN4 1000

Resource Manager database

db2 connect to rmdb user demo1 using demo4youdb2 select * from syscat.bufferpools > rmbp.cfg, containing bufferpool sizes:

OBJECTPOOL 2000SMSPOOL 500PARTSPOOL 100BLOBPOOL 1000

TRACKINGPOOL 250

of 75



Commands to set new bufferpool sizes

Commands to use to tune your laptop demo system are listed below. Run this in a DB2 Command Window:

db2 update dbm cfg using QUERY _HEAP _SZ 4096 db2 update dbm cfg using SHEAPTHRES 2000 db2 update dbm cfg using MAXAGENTS 50

db2 connect to icmnlsdb user demo1 using demo4youdb2 update db cfg using APP_CTL_HEAP_SZ 2000 db2 update db cfg using LOCKLIST 200db2 update db cfg using STMTHEAP 4096 db2 update db cfg using SORTHEAP 128 db2 update db cfg using MAXAPPLS 50

db2 alter bufferpool ICMLSFREQBP4 size 500db2 alter bufferpool ICMLSVOLATILEBP4 size 800 db2 alter bufferpool ICMLSMAINBP32 size 800 db2 alter bufferpool CMBMAIN4 size 500

db2 connect to rmdb user demo1 using demo4you

db2 alter bufferpool OBJECTPOOL size 800 db2 alter bufferpool SMSPOOL size 100 db2 alter bufferpool PARTSPOOL size 60 db2 alter bufferpool BLOBPOOL size 400db2 alter bufferpool TRACKINGPOOL size 100

Restart DB2 database manager for changes to take effect.

of 75



Appendix A. References1. DB2 for Linux, UNIX, and Windows; http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?

topic=/com.ibm.db2.udb.doc/start/t000848 8.htm

2. Windows 2003 TCP/IP stack is up to 25% faster in performance; http://www.microsoft.com/windowsserver2003/evaluation/performance/default.mspx; http://www.sql-server-performance.com/operating system tuning w2003.asp

3. Oracle Corporation. Oracle Technology Network. Oracle Corporation. May 7, 2003. http:// otn.oracle.com/pls/tahiti/tahiti.initora

4. IBM DeveloperWorks whitepaper: Performance Tuning for CM web applications http://www.ibm.com/developerworks/db2/library/techarticle/dm-0407shah

5. IBM Redbook: Tuning Windows Server 2003 on IBM eServer xSeries Servers http://www.redbooks.ibm.com/redpapers/pdfs/redp3943.pdf

6. White paper: IBM DB2 Content Manager Version 8 Configuring High Availability in a Microsoft Cluster Services Environment at http://www.ibm.com/support/docview.wss?uid=swg27005017

7. Web Server Best Practices http://www.ibm.com/software/webservers/appserv/ws bestpractices.pdf

8. WebSphere Scalability http://www.redbooks.ibm.com/redbooks/SG246153.html

9. IBM Redbook Performance Tuning for Content Manager V8 http://www.redbooks.ibm.com/redbooks/pdfs/sg246949.pdf

10. DB2 U DB Version 8.2 Information Center http://publib.boulder.ibm.com/infocenter/db2help/index.jsp

11. CM V8.3 Performance Monitoring Guide at http://www.ibm.com/support/docview.wss?uid=swg27006451

12. CM V8.3 Performance Troubleshooting Guide http://www.ibm.com/support/docview.wss?uid=swg27006450

13. CM V8.3 Performance Tuning Guide for CM on Linux with DB2

http://www.ibm.com/support/docview.wss?uid=swg27007130 14. CM V8.3 for zOS Performance Hints and Tips

http://www.ibm.com/support/docview.wss?uid=swg27008999

of 75





http://publib.boulder.ibm.com/infocenter/db2help/index.jsp

http://www.redbooks.ibm.com/redbooks/pdfs/sg246949.pdf

http://www.redbooks.ibm.com/redbooks/SG246153.html

http://www.ibm.com/software/webservers/appserv/ws


http://www.redbooks.ibm.com/redpapers/pdfs/redp3943.pdf

http://www.ibm.com/developerworks/db2/library/techarticle/dm-0407shah

http://otn.oracle.com/pls/tahiti/tahiti.initora

http://www.sql-server-performance.com/operating

http://www.microsoft.com/windowsserver2003/evaluation/performance/default.mspx;

http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/start/t000848

http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/start/t000848



Appendix B. Workload and Hardware DescriptionWorkload

The X8 benchmark is an internal Content Manager performance benchmark designed to exercise particular API calls of the CM application. The X8 scenario simulates users that iterate over a set of operations in parallel, exposing bottlenecks within individual operations and contention between operations. The run time for the X8 performance test is configurable and was set for duration of 30 minutes for each performance run. The user think-time is also configurable. In our test, users "think" randomly between 4-8 seconds. In general, the X8 benchmark exercises the functionality outlined below. The labels on the right are the names of the operations within the charts and tables.

Each virtual user performs the following scenario:

[A user logs in CM V8.3 system, and repeats the following until test is done]> Create a folder.> [Repeat 3 times]

· Create a document with a 100KB and 1KB part.· Add the document to the folder.· Retrieve both parts (1k and 100K documents)· Move the document into a different item type.· Initiate a workflow process on the document.· Get next work package for the document.· Continue the process· Complete doc routing process

Hardware Specifications

The tuning parameters listed in this paper are specific to the platforms on the following hardware. Plan and tune your applications accordingly.

Platform Library Server Resource Manager Mid-tier Server

of 75

AIX IBM eServer pSeries 6904 1.3 GHz CPUs16 GB RAM1Gbps Network Adapter 2Gbps PCI Fibre Channel

IBM eServer pSeries 690 4 1.3 GHz CPUs16 GB RAM1Gbps Network Adapter 2Gbps PCI Fibre Channel

IBM eServer pSeries 690 4 1.3 GHz CPUs16 GB RAM1Gbps Network Adapter 2Gbps PCI Fibre Channel

of 75

Windows IBM eServer xSeries 3604 2.8GHz Intel® Xeon CPUs 8 GB RAM1Gbps Network Adapter 2Gbps PCI Fibre Channel

IBM eServer xSeries 3604 2.8GHz Intel® Xeon CPUs 8 GB RAM1Gbps Network Adapter 2Gbps PCI Fibre Channel

IBM eServer xSeries 3604 2.8GHz Intel® Xeon CPUs 8 GB RAM1Gbps Network Adapter 2Gbps PCI Fibre Channel

of 75

Solaris SUN Fire V880 SUN Fire V880 SUN Fire V8804 750 MHz CPUs 2 750 MHz CPUs 2 750 MHz CPUs8 GB RAM 4 GB RAM 4 GB RAM

1Gbps Network Adapter 1Gbps Network Adapter 1Gbps Network Adapter

of 75



Appendix C. DDL CustomizationThis section lists the DDL files and tablespace information that a Content Manager administrator needs to know when customizing the physical database design with DMS (Database Managed Storage). Knowing what each tablespace's function is will help you to layout the storage more efficiently by introducing more parallel disk I/O therefore reducing I/O waits in the system.

Files available for DDL customizationPrimary filesDDL file name Contents description icmlsdb2def.ddl Library Server database, buffer pool, and tablespace definitionsicmplsct.ddl Library Server database table definitionsicmplsci.ddl Library Server server index definitionsicmrmcrdb.ddl Resource Manager server database, buffer pools, and tablespacesdefinitionsicmrmcrtab.ddl Resource Manager server database tables and index definitions

Additional filesDDL file name Contents description cmbadm81.db2 Library Server federated administration table definitionsicmpwfcr.ddl Library Server federated advanced workflow table definitionsicmjcr.ddl Library Server JCR table definitions - reserved for future useicmjcrup.ddl Library Server JCR table definitions - reserved for future use

Library Server default tablespaces and intended usageBufferpool Tablespace Description

icmlfq32 Holds all the large, persistent, "frequentlyused" tables - most notably, all the item type tables. When a new item type is defined, the system administration client defines the new tables in this tablespace. If you customize the DDL, this tablespace should be defined across multiple containers for performance and scalability.

icmlsmainbp32 icmlnf32 Holds the large but less-frequently used tables, such as event logs, versions, andreplicas. If you don't use any of thesefeatures, this tablespace won't need much space.

icmlsvolatilebp4 icmvfq04 Holds the "volatile" tables, those whose size is ususally small but which can vary widely, and for which both updates and deletes are very common. For example, the tables associated with document routing "in progress" items, checked out items, etc. Putting this on a separate physical disk should help performance.

icmlsfreqbp4 icmsfq04 Holds all the small "frequently used" but seldom updated tables, such as system information, user definitions, ACLs, federatedadmin, etc, that don't take up much space but that are always needed in memory for good performance.

cmbmain4 cmbinv04 Holds the federated inventory tables. If you don't use federated access, this tablespace will be very small.

Resource Manager default tablespaces and intended usage

of 75



of 75



Appendix D. Sample SettingsThe following sections document the raw output for some CM V8.3 components and their final configurations that were used to achieve the optimal performance in the lab environment. Not all platforms are listed here. Please do not copy and paste these values directly into your environment, because these values are output from a particular machine and from a particular CM V8.3 setup. They are provided here for your reference only.

Content Manager V8.3 On Windows 2003

db2 get dbm cfg for CM V8.3 Library Server (DB2)

Database Manager Configuration

Node type = Enterprise Server Edition with local and remote clients

Database manager configuration release level = 0x0a00

Maximum total of files open (MAXTOTFILOP) = 16000CPU speed (millisec/instruction) (CPUSPEED) = 3.148962e-007Communications bandwidth (MB/sec) (COMM _BANDWIDTH) = 1.000000e+000

Max number of concurrently active databases (NUMDB) = 4Data Links support (DATALINKS) = NOFederated Database System Support (FEDERATED) = NOTransaction processor monitor name (TP_MON_NAME) =

Default charge-back account (DFT _ACCOUNT _STR) =

Java Development Kit installation path (JDK_PATH) = D:\PROGRA~1\IBM\SQLLIB\java\jdk

Diagnostic error capture level (DIAGLEVEL) = 3Notify Level (NOTIFYLEVEL) = 3Diagnostic data directory path (DIAGPATH) =

Default database monitor switches

Buffer pool (DFT _MON _BUFPOOL) = OFFLock (DFT _MON _LOCK) = OFFSort (DFT _MON _SORT) = OFFStatement (DFT _MON _STMT) = OFFTable (DFT _MON _TABLE) = OFFTimestamp (DFT _MON _TIMESTAMP) = OFFUnit of work (DFT _MON _UOW) = OFF

Monitor health of instance and databases (HEALTH _MON) = OFF

SYSADM group name (SYSADM _GROUP) =SYSCTRL group name (SYSCTRL _GROUP) =SYSMAINT group name (SYSMAINT _GROUP) =SYSMON group name (SYSMON _GROUP) =

Client Userid-Password Plugin (CLNT_PW_PLUGIN) =Client Kerberos Plugin (CLNT_KRB_PLUGIN) = IBMkrb5Group Plugin (GROUP _PLUGIN) =GSS Plugin for Local Authorization (LOCAL _GSSPLUGIN) =Server Plugin Mode (SRV _PLUGIN _MODE) = UNFENCEDServer List of GSS Plugins (SRVCON _GSSPLUGIN _LIST) =Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIEDDatabase manager authentication (AUTHENTICATION) = SERVERCataloging allowed without authority (CATALOG _NOAUTH) = NOTrust all clients (TRUST _ALLCLNTS) = YESTrusted client authentication (TRUST _CLNTAUTH) = CLIENT

of 75



Bypass federated authentication (FED _NOAUTH) = NO

Default database path (DFTDBPATH) = D:

Database monitor heap size (4KB) (MON _HEAP _SZ) = 1000Java Virtual Machine heap size (4KB) (JAVA _HEAP _SZ) = 512Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATICBackup buffer default size (4KB) (BACKBUFSZ) = 1024Restore buffer default size (4KB) (RESTBUFSZ) = 1024

Agent stack size (AGENT _STACK _SZ) = 384Minimum committed private memory (4KB) (MIN_PRIV_MEM) = 32Private memory threshold (4KB) (PRIV _MEM _THRESH) = 20000

Sort heap threshold (4KB) (SHEAPTHRES) = 10000

Directory cache support (DIR_CACHE) = YES

Application support layer heap size (4KB) (ASLHEAPSZ) = 15Max requester I/O block size (bytes) (RQRIOBLK) = 65535DOS requester I/O block size (bytes) (DOS _RQRIOBLK) = 4096Query heap size (4KB) (QUERY _HEAP _SZ) = 32768

Workload impact by throttled utilities(UTIL _IMPACT _LIM) = 100

Priority of agents (AGENTPRI) = SYSTEMMax number of existing agents (MAXAGENTS) = 200Agent pool size (NUM_POOLAGENTS) = 100(calculated)Initial number of agents in pool (NUM_INITAGENTS) = 0Max number of coordinating agents (MAX _COORDAGENTS) = (MAXAGENTS - NUM_INITAGENTS)Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX _COORDAGENTS Max number of client connections (MAX_CONNECTIONS) = 1200

Keep fenced process (KEEPFENCED) = YESNumber of pooled fenced processes (FENCED _POOL) = MAX _COORDAGENTSInitial number of fenced processes (NUM_INITFENCED) = 0

Index re-creation time and redo index build (INDEXREC) = ACCESS

Transaction manager database name (TM_DATABASE) = 1ST_CONNTransaction resync interval (sec) (RESYNC _INTERVAL) = 180

SPM name (SPM _NAME) = IMAGESPM log size (SPM _LOG _FILE _SZ) = 256SPM resync agent limit (SPM _MAX _RESYNC) = 20SPM log path (SPM _LOG _PATH) =

NetBIOS Workstation name (NNAME) =

TCP/IP Service name (SVCENAME) = db2c_DB2Discovery mode (DISCOVER) = SEARCHDiscover server instance (DISCOVER _INST) = ENABLE

Maximum query degree of parallelism (MAX _QUERYDEGREE) = ANY Enable intra-partition parallelism (INTRA _PARALLEL) = NO

No. of int. communication buffers (4KB) (FCM = 4096_NUM _BUFFERS)Number of FCM request blocks (FCM_NUM_RQB) = 2048Number of FCM connection entries (FCM_NUM _CONNECT) = (FCM_NUM_RQB * 0.75)Number of FCM message anchors (FCM _NUM _ANCHORS) = (FCM_NUM_RQB * 0.75)

Node connection elapse time (sec) (CONN _ELAPSE) = 10Max number of node connection retries (MAX _CONNRETRIES) = 5 Max time difference between nodes (min) (MAX _TIME _DIFF) = 60

db2start/db2stop timeout (min) (START_STOP_TIME) = 10



db2 get db cfg for icmnlsdb for CM V8.3 Library Server (DB2)

Database Configuration for Database icmnlsdb

Database configuration release level = 0x0a00Database release level = 0x0a00

Database territory = USDatabase code page = 1252Database code set = IBM-1252Database country/region code = 1Database collating sequence = UNIQUEAlternate collating sequence (ALT_COLLATE) =

Dynamic SQL Query management (DYN _QUERY _MGMT) = DISABLE

Discovery support for this database (DISCOVER_DB) = ENABLE

Default query optimization class (DFT_QUERYOPT) = 2Degree of parallelism (DFT _DEGREE) = 1Continue upon arithmetic exceptions (DFT_SQLMATHWARN) = NODefault refresh age (DFT _REFRESH _AGE) = 0Default maintained table types for opt (DFT _MTTB _TYPES) = SYSTEMNumber of frequent values retained (NUM_FREQVALUES) = 10Number of quantiles retained (NUM_QUANTILES) = 20

Backup pending = NO

Database is consistent = NORollforward pending = NORestore pending = NO

Multi-page file allocation enabled = YES

Log retain for recovery status = NOUser exit for logging status = NO

Data Links Token Expiry Interval (sec) (DL_EXPINT) = 60Data Links Write Token Init Expiry Intvl(DL_WT_IEXPINT) = 60 Data Links Number of Copies (DL _NUM _COPIES) = 1Data Links Time after Drop (days) (DL _TIME _DROP) = 1Data Links Token in Uppercase (DL_UPPER) = NOData Links Token Algorithm (DL _TOKEN) = MAC0

Database heap (4KB) (DBHEAP) = 2400Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC Catalog cache size (4KB) (CATALOGCACHE_SZ) = (MAXAPPLS*4)Log buffer size (4KB) (LOGBUFSZ) = 32Utilities heap size (4KB) (UTIL_HEAP_SZ) = 5000Buffer pool size (pages) (BUFFPAGE) = 250Extended storage segments size (4KB) (ESTORE_SEG_SZ) = 16000Number of extended storage segments (NUM_ESTORE_SEGS) = 0Max storage for lock list (4KB) (LOCKLIST) = 1000

Max size of appl. group mem set (4KB) (APPGROUP_MEM_SZ) = 40000 Percent of mem for appl. group heap (GROUPHEAP _RATIO) = 70Max appl. control heap size (4KB) (APP_CTL_HEAP_SZ) = 512

Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = (SHEAPTHRES)Sort list heap (4KB) (SORTHEAP) = 256SQL statement heap (4KB) (STMTHEAP) = 16384Default application heap (4KB) (APPLHEAPSZ) = 2560Package cache size (4KB) (PCKCACHESZ) = (MAXAPPLS*8)Statistics heap size (4KB) (STAT _HEAP _SZ) = 4384

Interval for checking deadlock (ms) (DLCHKTIME) = 10000

of 75



Percent. of lock lists per application (MAXLOCKS) = 22Lock timeout (sec) (LOCKTIMEOUT) = 30

Changed pages threshold (CHNGPGS_THRESH) = 60Number of asynchronous page cleaners (NUM_IOCLEANERS) = 1 Number of I/O servers (NUM_IOSERVERS) = 3Index sort flag (INDEXSORT) = YESSequential detect flag (SEQDETECT) = YESDefault prefetch size (pages) (DFT_PREFETCH_SZ) = 16

Track modified pages (TRACKMOD) = OFF

Default number of containers = 1

Default tablespace extentsize (pages) (DFT_EXTENT_SZ) = 32

Max number of active applications (MAXAPPLS) = 1200Average number of active applications (AVG _APPLS) = 5Max DB files open per application (MAXFILOP) = 64

Log file size (4KB) (LOGFILSIZ) = 1000Number of primary log files (LOGPRIMARY) = 10Number of secondary log files (LOGSECOND) = 20Changed path to log files (NEWLOGPATH) =Path to log files = K:\DB2\NODE0000\SQL00001\SQLOGDIR\Overflow log path (OVERFLOWLOGPATH) =Mirror log path (MIRRORLOGPATH) =First active log file =Block log on disk full (BLK_LOG_DSK_FUL) = NO Percent of max active log space by transaction (MAX _LOG) = 0 Num. of active log files for 1 active UOW(NUM _LOG _SPAN) = 0

Group commit count (MINCOMMIT) = 1Percent log file reclaimed before soft chckpt (SOFTMAX) = 100Log retain for recovery enabled (LOGRETAIN) = OFFUser exit for logging enabled (USEREXIT) = OFF

HADR database role = STANDARD

HADR local host name (HADR _LOCAL _HOST) =HADR local service name (HADR _LOCAL _SVC) =HADR remote host name (HADR _REMOTE _HOST) =HADR remote service name (HADR _REMOTE _SVC) =HADR instance name of remote server (HADR _REMOTE _INST) =HADR timeout value (HADR _TIMEOUT) = 120HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC

First log archive method (LOGARCHMETH1) = OFFOptions for logarchmeth1 (LOGARCHOPT1) =Second log archive method (LOGARCHMETH2) = OFFOptions for logarchmeth2 (LOGARCHOPT2) =Failover log archive path (FAILARCHPATH) =Number of log archive retries on error (NUMARCHRETRY) = 5Log archive retry Delay (secs) (ARCHRETRYDELAY) = 20Vendor options (VENDOROPT) =

Auto restart enabled (AUTORESTART) = ONIndex re-creation time and redo index build (INDEXREC) = SYSTEM (ACCESS)Log pages during index build (LOGINDEXBUILD) = OFFDefault number of loadrec sessions (DFT_LOADREC_SES) = 1Number of database backups to retain (NUM_DB _BACKUPS) = 12 Recovery history retention (days) (REC _HIS _RETENTN) = 366

TSM management class (TSM_MGMTCLASS) =TSM node name (TSM_NODENAME) =TSM owner (TSM_OWNER) =TSM password (TSM _PASSWORD) =

Automatic maintenance (AUTO _MAINT) = OFFAutomatic database backup (AUTO _DB _BACKUP) = OFF

of 75



Automatic table maintenance (AUTO _TBL _MAINT) = OFFAutomatic runstats (AUTO _RUNSTATS) = OFFAutomatic statistics profiling (AUTO _STATS _PROF) = OFF

Automatic profile updates (AUTO _PROF _UPD) = OFFAutomatic reorganization (AUTO _REORG) = OFF

of 75



db2 get dbm cfg and db cfg for rmdb for CM V8.3 Resource Manager databases (DB2)

Database Manager Configuration



Maximum total of files open (MAXTOTFILOP) = 16000CPU speed (millisec/instruction) (CPUSPEED) = 3.148962e-007Communications bandwidth (MB/sec) (COMM _BANDWIDTH) = 1.000000e+000

Max number of concurrently active databases (NUMDB) = 8Data Links support (DATALINKS) = NOFederated Database System Support (FEDERATED) = YESTransaction processor monitor name (TP_MON_NAME) =


Java Development Kit installation path (JDK_PATH) = D:\PROGRA~1\IBM\SQLLIB\java\jdk

Diagnostic error capture level (DIAGLEVEL) = 3Notify Level (NOTIFYLEVEL) = 3Diagnostic data directory path (DIAGPATH) =




SYSADM group name (SYSADM _GROUP) =SYSCTRL group name (SYSCTRL _GROUP) =SYSMAINT group name (SYSMAINT _GROUP) =SYSMON group name (SYSMON _GROUP) =

Client Userid-Password Plugin (CLNT_PW_PLUGIN) =Client Kerberos Plugin (CLNT_KRB_PLUGIN) = IBMkrb5Group Plugin (GROUP _PLUGIN) =GSS Plugin for Local Authorization (LOCAL _GSSPLUGIN) =Server Plugin Mode (SRV _PLUGIN _MODE) = UNFENCEDServer List of GSS Plugins (SRVCON _GSSPLUGIN _LIST) =Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =Server Connection Authentication (SRVCON_AUTH) = NOT _SPECIFIEDDatabase manager authentication (AUTHENTICATION) = SERVERCataloging allowed without authority (CATALOG _NOAUTH) = NOTrust all clients (TRUST _ALLCLNTS) = YESTrusted client authentication (TRUST _CLNTAUTH) = CLIENTBypass federated authentication (FED _NOAUTH) = NO

Default database path (DFTDBPATH) = D:

Database monitor heap size (4KB) (MON _HEAP _SZ) = 66Java Virtual Machine heap size (4KB) (JAVA _HEAP _SZ) = 512Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATICBackup buffer default size (4KB) (BACKBUFSZ) = 1024Restore buffer default size (4KB) (RESTBUFSZ) = 1024

Agent stack size (AGENT _STACK _SZ) = 16Minimum committed private memory (4KB) (MIN_PRIV_MEM) = 32

of 75



of 75

Private memory threshold (4KB) (PRIV _MEM _THRESH) = 20000



Application support layer heap size (4KB) (ASLHEAPSZ) = 15Max requester I/O block size (bytes) (RQRIOBLK) = 32767DOS requester I/O block size (bytes) (DOS _RQRIOBLK) = 4096Query heap size (4KB) (QUERY _HEAP _SZ) = 32768

Workload impact by throttled utilities (UTIL _IMPACT _LIM) = 100

Priority of agents (AGENTPRI) = SYSTEMMax number of existing agents (MAXAGENTS) = 400Agent pool size (NUM_POOLAGENTS) = 200(calculated)Initial number of agents in pool (NUM_INITAGENTS) = 0Max number of coordinating agents (MAX _COORDAGENTS) = (MAXAGENTS - NUM_INITAGENTS)Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX _COORDAGENTS Max number of client connections (MAX _CONNECTIONS) = MAX _COORDAGENTS


Index re-creation time and redo index build (INDEXREC) = ACCESS


SPM name (SPM _NAME) = IMAGESPM log size (SPM _LOG _FILE _SZ) = 256SPM resync agent limit (SPM _MAX _RESYNC) = 20SPM log path (SPM _LOG _PATH) =

NetBIOS Workstation name (NNAME) =

TCP/IP Service name (SVCENAME) = db2c_DB2Discovery mode (DISCOVER) = SEARCHDiscover server instance (DISCOVER _INST) = ENABLE


No. of int. communication buffers (4KB) (FCM _NUM _BUFFERS) = 4096Number of FCM request blocks (FCM_NUM_RQB) = 2048Number of FCM connection entries (FCM_NUM _CONNECT) = (FCM_NUM_RQB * 0.75)Number of FCM message anchors (FCM _NUM _ANCHORS) = (FCM_NUM_RQB * 0.75)



D:\WebSphere\AppServer\bin>db2 get db cfg for rmdb

Database Configuration for Database rmdb


Database territory = USDatabase code page = 1208Database code set = UTF-8Database country/region code = 1



Database collating sequence = BINARYAlternate collating sequence (ALT_COLLATE) =



Default query optimization class (DFT_QUERYOPT) = 2Degree of parallelism (DFT _DEGREE) = 1Continue upon arithmetic exceptions (DFT_SQLMATHWARN) = NO Default refresh age (DFT _REFRESH _AGE) = 0Default maintained table types for opt (DFT _MTTB _TYPES) = SYSTEMNumber of frequent values retained (NUM_FREQVALUES) = 10Number of quantiles retained (NUM_QUANTILES) = 20

Backup pending = NO

Database is consistent = NORollforward pending = NORestore pending = NO



Data Links Token Expiry Interval (sec) (DL_EXPINT) =60Data Links Write Token Init Expiry Intvl(DL_WT_IEXPINT) = 60Data Links Number of Copies (DL _NUM _COPIES) = 1Data Links Time after Drop (days) (DL _TIME _DROP) = 1Data Links Token in Uppercase (DL_UPPER) = NOData Links Token Algorithm (DL _TOKEN) = MAC0

Database heap (4KB) (DBHEAP) = 1000Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC Catalog cache size (4KB) (CATALOGCACHE_SZ) = (MAXAPPLS*4)Log buffer size (4KB) (LOGBUFSZ) = 8Utilities heap size (4KB) (UTIL_HEAP_SZ) = 5000Buffer pool size (pages) (BUFFPAGE) = 250Extended storage segments size (4KB) (ESTORE_SEG_SZ) = 16000Number of extended storage segments (NUM_ESTORE_SEGS) = 0Max storage for lock list (4KB) (LOCKLIST) = 1000


Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = (SHEAPTHRES)Sort list heap (4KB) (SORTHEAP) = 256SQL statement heap (4KB) (STMTHEAP) = 2048Default application heap (4KB) (APPLHEAPSZ) = 1024Package cache size (4KB) (PCKCACHESZ) = (MAXAPPLS*8)Statistics heap size (4KB) (STAT _HEAP _SZ) = 4384

Interval for checking deadlock (ms) (DLCHKTIME) = 10000Percent. of lock lists per application (MAXLOCKS) = 22Lock timeout (sec) (LOCKTIMEOUT) = -1

Changed pages threshold (CHNGPGS _THRESH) = 60Number of asynchronous page cleaners (NUM_IOCLEANERS) = 1 Number of I/O servers (NUM_IOSERVERS) = 3Index sort flag (INDEXSORT) = YESSequential detect flag (SEQDETECT) = YESDefault prefetch size (pages) (DFT_PREFETCH_SZ) = AUTOMATIC


Default number of containers = 1


Content Manager V8.3 Performance Tuning GuideDefault tablespace extentsize (pages) (DFT_EXTENT_SZ) = 32


Log file size (4KB) (LOGFILSIZ) = 1000Number of primary log files (LOGPRIMARY) = 25Number of secondary log files (LOGSECOND) = 50Changed path to log files (NEWLOGPATH) =Path to log files = K:\DB2\NODE0000\SQL00001\ SQLOGDIR\Overflow log path (OVERFLOWLOGPATH) =Mirror log path (MIRRORLOGPATH) =First active log file =Block log on disk full (BLK_LOG_DSK_FUL) = NOPercent of max active log space by transaction (MAX _LOG) = 0 Num. of active log files for 1 active UOW(NUM _LOG _SPAN) = 0

Group commit count (MINCOMMIT) = 1Percent log file reclaimed before soft chckpt (SOFTMAX) = 100 Log retain for recovery enabled (LOGRETAIN) = OFFUser exit for logging enabled (USEREXIT) = OFF

HADR database role = STANDARD

HADR local host name (HADR _LOCAL _HOST) =HADR local service name (HADR _LOCAL _SVC) =HADR remote host name (HADR _REMOTE _HOST) =HADR remote service name (HADR _REMOTE _SVC) =HADR instance name of remote server (HADR _REMOTE _INST) = HADR timeout value (HADR _TIMEOUT) = 120HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC


Auto restart enabled (AUTORESTART) = ONIndex re-creation time and redo index build (INDEXREC) = SYSTEM (ACCESS) Log pages during index build (LOGINDEXBUILD) = OFFDefault number of loadrec sessions (DFT_LOADREC_SES) = 1Number of database backups to retain (NUM_DB _BACKUPS) = 12Recovery history retention (days) (REC _HIS _RETENTN) = 366


Automatic maintenance (AUTO _MAINT) = OFFAutomatic database backup (AUTO _DB _BACKUP) = OFFAutomatic table maintenance (AUTO _TBL _MAINT) = OFF

Automatic runstats (AUTO _RUNSTATS) = OFFAutomatic statistics profiling (AUTO _STATS _PROF) = OFF


of 75



Oracle D:\oracle\ora92\database\initicmnlsdb.ora configuration file################################################################################ Licensed Materials - Property of IBM# IBM DB2 Content Manager Enterprise Edition V8 (program number 5724-B19)# IBM DB2 Content Manager Express Edition V8 (program number 5724-F73)# (c ) Copyright IBM Corp. 1997, 2004. All Rights Reserved.# IBM DB2 Information Integrator for Content V8 (program number 5724-B43)# (c ) Copyright IBM Corp. 1998, 2004. All Rights Reserved.# US Government Users Restricted Rights -# Use, duplication or disclosure restricted by GSA ADP Schedule# Contract with IBM Corporation################################################################################# Database characteristicsdb_name = icmnlsdbdb _domain = stl.ibm.com global_names = trueremote _login_passwordfile = noneundo_management = autocontrol_files = ("D:\oracle\ora92\database\icmnlsdb _control _01.ctl","i :\ icmnlsdb\ icmnlsdb\ ctl\ icmnlsdb _control _02. ctl")# Instancedb _block _size = 4096 # cmperf tuneddb _cache _size = 500M shared_pool _size = 125Mlarge_pool _size = 0 java_pool _size = 0 pre_page_sga = true # cmperf tuned# pga_aggregate_target = 200MWORKAREA_S I ZE_PO LI CY=AUTOpga_aggregate_target = 500Mdb _files = 1024open _cursors = 500# cmperf tuned, was 150processes = 1000 log_checkpoint_interval = 10000log_buffer = 1048576 # Optimizercursor_sharing = similarcursor_space_for_time = true# Loggingbackground_dump_dest = i :\ icmnlsdb\ icmnlsdb\bdumpuser_dump_dest = i:\icmnlsdb\icmnlsdb\udump core_dump_dest = i:\icmnlsdb\icmnlsdb\cdump max_dump_file_size = 10240# OracleTextjob_queue_processes = 1# Misccompatible = 9.2.0 # cmperf tunedundo_retention = 7200

of 75

http://stl.ibm.com/



WebSphere application server “icmrm” environment variables and JVM parametersD:\WebSphere\AppServer\bin>more start_icmrm.bat @REM start_icmrm.bat@REM Generated: Mon Mar 14 14:24:21 PST 2005

@setlocal@echo off

@REM Bootstrap values ... call "%~dp0setupCmdLine.bat"

@REM For debugging the server process:@REM set DEBUG=-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_soc ket, server=y, suspend=y, address=7777

@REM Environment Settings SET PATH=%WAS_PATH%

@REM Launch Command"D:\WebSphere\AppServer\java/bin/java" %DEBUG% "-Xbootclasspath/p:D:\WebSphere\ AppServer\java/jre/lib/ext/ibmorb.jar;D:\WebSphere\AppServer\java/jre/lib/ext/ib mext.jar" "-classpath" "D:\WebSphere\AppServer/properties;D:\WebSphere\AppServer /properties;D:\WebSphere\AppServer/lib/bootstrap.jar;D:\WebSphere\AppServer/lib/ j2ee.jar;D:\WebSphere\AppServer/lib/lmproxy.jar;D:\WebSphere\AppServer/lib/urlpr otocols.jar" "-Xms768m" "-Xmx768m" "-Dws.ext.dirs=D:\WebSphere\AppServer\java/lib ;D:\WebSphere\AppServer/classes;D:\WebSphere\AppServer/classes;D:\WebSphere\AppS erver/lib;D:\WebSphere\AppServer/lib/ext;D:\WebSphere\AppServer/web/help;D:\WebS phere\AppServer/deploytool/itp/plugins/com. ibm.etools .ejbdeploy/runtime" "-Dserv er.root=D:\WebSphere\AppServer" "-Ddb2j.system.home=D:\WebSphere\AppServer/cloud scape" "-Duser.install.root=D:\WebSphere\AppServer" "-Dcom.ibm.itp.location=D:\W ebSphere\AppServer/bin" "-Dwas.install .root=D:\WebSphere\AppServer" "-Dibm.websp here.preload.classes=true" "-Djava.security.auth.login.config=D:\WebSphere\AppSe rver/properties/wsjaas .conf" "-Djava. security.policy=D:\WebSphere\AppServer/prop erties/server.policy" "com.ibm.ws.bootstrap.WSLauncher" "com.ibm.ws.runtime.WsSe rver" "D : \ WebSphere\ AppServer\ config" "aragorn" "aragorn" "icmrm"

@endlocal

Content Manager V8.3 On Solaris

dbm cfg for CM V8.3 Database Manager (DB2)Database Manager Configuration



CPU speed (millisec/instruction) (CPUSPEED) = 1.110788e-06Communications bandwidth (MB/sec) (COMM _BANDWIDTH) = 1.000000e+00

Max number of concurrently active databases (NUMDB) = 4Data Links support (DATALINKS) = NOFederated Database System Support (FEDERATED) = NOTransaction processor monitor name (TP_MON_NAME) =


Java Development Kit installation path (JDK_PATH) = /usr/j2se

Diagnostic error capture level (DIAGLEVEL) = 3Notify Level (NOTIFYLEVEL) = 3Diagnostic data directory path (DIAGPATH) = /export/home/db2inst1/sqllib/db2dump

of 75






SYSADM group name (SYSADM _GROUP) = DB2GRP1SYSCTRL group name (SYSCTRL _GROUP) =SYSMAINT group name (SYSMAINT _GROUP) =SYSMON group name (SYSMON_GROUP) =

Client Userid-Password Plugin (CLNT_PW_PLUGIN) =Client Kerberos Plugin (CLNT_KRB_PLUGIN) =Group Plugin (GROUP _PLUGIN) =GSS Plugin for Local Authorization (LOCAL _GSSPLUGIN) =Server Plugin Mode (SRV _PLUGIN _MODE) = UNFENCEDServer List of GSS Plugins (SRVCON _GSSPLUGIN _LIST) =Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIEDDatabase manager authentication (AUTHENTICATION) = SERVERCataloging allowed without authority (CATALOG _NOAUTH) = NOTrust all clients (TRUST _ALLCLNTS) = YESTrusted client authentication (TRUST _CLNTAUTH) = CLIENTBypass federated authentication (FED _NOAUTH) = NO

Default database path (DFTDBPATH) = /d20/cm83_db2db

Database monitor heap size (4KB) (MON _HEAP _SZ) = 1000Java Virtual Machine heap size (4KB) (JAVA _HEAP _SZ) = 256Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC Backup buffer default size (4KB) (BACKBUFSZ) = 1024

Restore buffer default size (4KB) (RESTBUFSZ) = 1024



Application support layer heap size (4KB) (ASLHEAPSZ) = 15Max requester I/O block size (bytes) (RQRIOBLK) = 65535Query heap size (4KB) (QUERY _HEAP _SZ) = 32768

Workload impact by throttled utilities(UTIL _IMPACT _LIM) = 10

Priority of agents (AGENTPRI) = SYSTEMMax number of existing agents (MAXAGENTS) = 2000Agent pool size (NUM_POOLAGENTS) = 600Initial number of agents in pool (NUM_INITAGENTS) = 600Max number of coordinating agents (MAX _COORDAGENTS) = 2000Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX _COORDAGENTSMax number of client connections (MAX_CONNECTIONS) = MAX _COORDAGENTS


Index re-creation time and redo index build (INDEXREC) = RESTART


SPM name (SPM _NAME) =

of 75



SPM log size (SPM_LOG_FILE_SZ) = 256SPM resync agent limit (SPM_MAX_RESYNC) = 20SPM log path (SPM _LOG _PATH) =

TCP/IP Service name (SVCENAME) = db2c_db2inst1Discovery mode (DISCOVER) = SEARCHDiscover server instance (DISCOVER _INST) = ENABLE


No. of int. communication buffers (4KB) (FCM _NUM _BUFFERS) = 4096 Number of FCM request blocks (FCM_NUM_RQB) = AUTOMATICNumber of FCM connection entries (FCM_NUM _CONNECT) = AUTOMATICNumber of FCM message anchors (FCM _NUM _ANCHORS) = AUTOMATIC



of 75



db cfg for CM V8.3 Library Server databaseDatabase Configuration for Database icmnlsdb


Database territory = USDatabase code page = 819Database code set = ISO8859-1Database country/region code = 1Database collating sequence = UNIQUEAlternate collating sequence (ALT_COLLATE) =Database page size = 4096




Backup pending = NO

Database is consistent = YESRollforward pending = NORestore pending = NO




Database heap (4KB) (DBHEAP) = 1200Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC Catalog cache size (4KB) (CATALOGCACHE_SZ) = 64Log buffer size (4KB) (LOGBUFSZ) = 128Utilities heap size (4KB) (UTIL_HEAP_SZ) = 5000Buffer pool size (pages) (BUFFPAGE) = 1000Extended storage segments size (4KB) (ESTORE_SEG_SZ) = 16000Number of extended storage segments (NUM_ESTORE_SEGS) = 0Max storage for lock list (4KB) (LOCKLIST) = 1000


Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = (SHEAPTHRES) Sort list heap (4KB) (SORTHEAP) = 32SQL statement heap (4KB) (STMTHEAP) = 4096Default application heap (4KB) (APPLHEAPSZ) = 4096Package cache size (4KB) (PCKCACHESZ) = 5000Statistics heap size (4KB) (STAT _HEAP _SZ) = 4384

Interval for checking deadlock (ms) (DLCHKTIME) = 10000

of 75



Percent. of lock lists per application (MAXLOCKS) = 25Lock timeout (sec) (LOCKTIMEOUT) = 60

Changed pages threshold (CHNGPGS_THRESH) = 60Number of asynchronous page cleaners (NUM_IOCLEANERS) = 4 Number of I/O servers (NUM_IOSERVERS) = 6Index sort flag (INDEXSORT) = YESSequential detect flag (SEQDETECT) = YESDefault prefetch size (pages) (DFT_PREFETCH_SZ) = AUTOMATIC


Default number of containers = 1Default tablespace extentsize (pages) (DFT_EXTENT_SZ) = 32


Log file size (4KB) (LOGFILSIZ) = 1000Number of primary log files (LOGPRIMARY) = 10Number of secondary log files (LOGSECOND) = 20Changed path to log files (NEWLOGPATH) =P a t h t o l o g f i l e s = /d20/cm83_db2db/db2inst1/NODE0000/SQL00001/SQLOGDIR/ Overflow log path (OVERFLOWLOGPATH) =Mirror log path (MIRRORLOGPATH) =First active log file =Block log on disk full (BLK_LOG_DSK_FUL) = NOPercent of max active log space by transaction (MAX _LOG) = 0 Num. of active log files for 1 active UOW(NUM _LOG _SPAN) = 0

Group commit count (MINCOMMIT) = 1Percent log file reclaimed before soft chckpt (SOFTMAX) = 100Log retain for recovery enabled (LOGRETAIN) = OFFUser exit for logging enabled (USEREXIT) = OFF

HADR database role = STANDARDHADR local host name (HADR _LOCAL _HOST) =HADR local service name (HADR _LOCAL _SVC) =HADR remote host name (HADR _REMOTE _HOST) =HADR remote service name (HADR _REMOTE _SVC) =HADR instance name of remote server (HADR _REMOTE _INST) =HADR timeout value (HADR _TIMEOUT) = 120HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC


Auto restart enabled (AUTORESTART) = ONIndex re-creation time and redo index build (INDEXREC) = SYSTEM (RESTART)Log pages during index build (LOGINDEXBUILD) = OFFDefault number of loadrec sessions (DFT_LOADREC_SES) = 1Number of database backups to retain (NUM_DB _BACKUPS) = 12 Recovery history retention (days) (REC _HIS _RETENTN) = 366


Automatic maintenance (AUTO _MAINT) = OFF

of 75



Automatic database backup (AUTO _DB _BACKUP) = OFFAutomatic table maintenance (AUTO _TBL _MAINT) = OFFAutomatic runstats (AUTO _RUNSTATS) = OFFAutomatic statistics profiling (AUTO _STATS _PROF) = OFF


of 75



db cfg for CM V8.3 Resource Manager (DB2) databaseDatabase Configuration for Database rmdb


Database territory = USDatabase code page = 1208Database code set = UTF-8Database country/region code = 1Database collating sequence = BINARYAlternate collating sequence (ALT_COLLATE) =




Backup pending = NO

Database is consistent = YESRollforward pending = NORestore pending = NO




Database heap (4KB) (DBHEAP) = 1200Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC Catalog cache size (4KB) (CATALOGCACHE_SZ) = 64Log buffer size (4KB) (LOGBUFSZ) = 128Utilities heap size (4KB) (UTIL_HEAP_SZ) = 5000Buffer pool size (pages) (BUFFPAGE) = 1000Extended storage segments size (4KB) (ESTORE_SEG_SZ) = 16000Number of extended storage segments (NUM_ESTORE_SEGS) = 0Max storage for lock list (4KB) (LOCKLIST) = 1000


Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = (SHEAPTHRES) Sort list heap (4KB) (SORTHEAP) = 32SQL statement heap (4KB) (STMTHEAP) = 4096Default application heap (4KB) (APPLHEAPSZ) = 4096Package cache size (4KB) (PCKCACHESZ) = 2000Statistics heap size (4KB) (STAT _HEAP _SZ) = 4384

Interval for checking deadlock (ms) (DLCHKTIME) = 10000Percent. of lock lists per application (MAXLOCKS) = 25

of 75



Lock timeout (sec) (LOCKTIMEOUT) = 60

Changed pages threshold (CHNGPGS_THRESH) = 60Number of asynchronous page cleaners (NUM_IOCLEANERS) = 8 Number of I/O servers (NUM_IOSERVERS) = 6Index sort flag (INDEXSORT) = YESSequential detect flag (SEQDETECT) = YESDefault prefetch size (pages) (DFT_PREFETCH_SZ) = AUTOMATIC


Default number of containers = 1Default tablespace extentsize (pages) (DFT_EXTENT_SZ) = 32


Log file size (4KB) (LOGFILSIZ) = 1000Number of primary log files (LOGPRIMARY) = 10Number of secondary log files (LOGSECOND) = 20Changed path to log files (NEWLOGPATH) =Path to log files = /d07/db283_logs/NODE0000/Overflow log path (OVERFLOWLOGPATH) =Mirror log path (MIRRORLOGPATH) =First active log file =Block log on disk full (BLK_LOG_DSK_FUL) = NOPercent of max active log space by transaction (MAX _LOG) = 0 Num. of active log files for 1 active UOW(NUM _LOG _SPAN) = 0

Group commit count (MINCOMMIT) = 1Percent log file reclaimed before soft chckpt (SOFTMAX) = 100 Log retain for recovery enabled (LOGRETAIN) = OFFUser exit for logging enabled (USEREXIT) = OFF

HADR database role = STANDARDHADR local host name (HADR _LOCAL _HOST) =HADR local service name (HADR _LOCAL _SVC) =HADR remote host name (HADR _REMOTE _HOST) =HADR remote service name (HADR _REMOTE _SVC) =HADR instance name of remote server (HADR _REMOTE _INST) =HADR timeout value (HADR _TIMEOUT) = 120HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC


Auto restart enabled (AUTORESTART) = ONIndex re-creation time and redo index build (INDEXREC) = SYSTEM (RESTART)Log pages during index build (LOGINDEXBUILD) = OFFDefault number of loadrec sessions (DFT_LOADREC_SES) = 1Number of database backups to retain (NUM_DB _BACKUPS) = 12 Recovery history retention (days) (REC _HIS _RETENTN) = 366


Automatic maintenance (AUTO _MAINT) = OFFAutomatic database backup (AUTO _DB _BACKUP) = OFFAutomatic table maintenance (AUTO _TBL _MAINT) = OFF

of 75



Automatic runstats (AUTO _RUNSTATS) = OFFAutomatic statistics profiling (AUTO _STATS _PROF) = OFF


of 75



Appendix E: ThanksThanks to the following members of the IBM DB2 Content Manager V8.3 Enterprise Edition Performance Team for contributing to this paper.

Author of the paper: Jesse F Chen, [email protected]

Key Contributors:

Dave Royer Bruce Smith Atul GoreRichard Heffel David Bronner Sandi Pond

IBM Silicon Valley Lab, 555 Bailey Ave. San Jose, California 95141, USA.

of 75

mailto:[email protected]



®Copyright IBM Corporation 2007 IBM United States of America Produced in the United States of AmericaAll Rights Reserved

The e-business logo, the eServer logo, IBM, the IBM logo, IBM Directory Server, DB2, Content Manager and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries or both.

The following are trademarks of other companies:Solaris, Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries or both. Windows and Windows 2003 Enterprise Edition are trademarks of Microsoft Corporation in the United States and/or other countries Oracle 9i and all Oracle-based trademarks and logos are trademarks of the Oracle Corporation in the United States, other countries or both. Other company, product and service names may be trademarks or service marks of others.

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PAPER "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. Information in this paper as to the availability of products was believed accurate as of the time of publication. IBM cannot guarantee that identified products will continue to be made available by their suppliers. This information could include technical inaccuracies or typographical errors. Changes may be made periodically to the information herein; these changes may be incorporated in subsequent versions of the paper. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this paper at any time without notice.

Any references in this document to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents.

You can send license inquiries, in writing, to: IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY, USA 10504-1 785

of 75

IBM DB2 Content Manager V8.3 Performance Tuning Guide

Technology

Transcript of IBM DB2 Content Manager V8.3 Performance Tuning Guide