Performance Tuning for Content Manager

378 Performance Tuning for Content Manager

COLUMNS DEFAULT NUM_FREQVALUES 100 NUM_QUANTILES 200 AND DETAILED

INDEXES

ALL ALLOW WRITE ACCESS ;

12.6.3 Performance improvement in Content Manager V8.3

In Content Manager Version 8.2, we have one thread for one volume. Starting in

Content Manager Version 8.3, we have a thread pool for volumes. That can

improve migrator performance greatly.

If you need to migrate a huge number of objects from one device to another and

you experience the performance issue, you might consider the V8.3 upgrade.

12.7 Slow administration in the sys admin client

The system administration client provides the tools that you need to set up and

manage your Content Manager system. When you work with the system

administration client (such as create, change, and remove an item type; create

and remove a user ID), you might experience a performance issue.

12.7.1 Tune database

In one scenario, a system administrator spent more than 40 minutes removing an

item type in the system administration client.

We suspected that some SELECT or DELETE SQL statement used most of this

time. We got the item type ID (1023) and component type ID (1042) based on the

name of the item type, and ran SELECT to test the performance:

SELECT * FROM ICMSTCOMPDEFS WHERE itemtypeid = 1023

SELECT COUNT(*) FROM ICMSTITEMS001001 WHERE COMPONENTTYPEID = 1042

These SQL statements ran for a long time on the machine. We asked the system

administrator to maintain the Library Server database. After maintaining the

database using reorg, runstat, and rebind, the system functioned much faster.

Our recommendation also included performing this type of task (in this case,

removing item type) during off-peak time.

If the maintenance on Library Server database and performing it during off-peak

time were not working, we would analyze the ICMSERVER.LOG file, with trace

level set to 15, to find out which SQL statements the system was running. From

there, we would tune these statements. We might need to tune the entire DB2

UDB server. Some SQL statements are static SQL that might be not in an

ICMSERVER.LOG file. In such cases, you should run the event monitor or ask