298 IBM Content Manager OnDemand Guide
13.1  Tuning Content Manager OnDemand to enhance 
performance
Two components make up performance: throughput and response time:
/SM590000Throughput: The number of transactions (Content Manager OnDemand requests) that can 
be satisfied for each unit of time. The more transactions that are run for each unit of time, 
the higher the throughput. Higher throughput implies that more users can be served 
concurrently and more load jobs can be run in parallel. If the throughput values are low, 
the system might not be able to support the required number of users.
/SM590000Response time: The amount of time it takes to service a single transaction (Content 
Manager OnDemand request). Faster response times imply that the users are able to 
retrieve their data faster from the archive, which in turn leads to more satisfied users. If the 
response time is slow, users are dissatisfied with the system. 
A high performance system, such as Content Manager OnDemand, provides both high 
throughput and short response times.
The following sections describe the various components of a Content Manager OnDemand 
system and its architecture. They provide guidance about the parameters and configurations 
that you can change to improve performance.
The ability to separate the object server from the library server offers two main advantages:
/SM590000The ability to share workload by dedicating machines to individual tasks
/SM590000The ability to reduce the impact of retrieving a large piece of data over a network that is 
either slow or overloaded
13.1.1  Content Manager OnDemand configuration
How reports are defined, indexed, and stored within Content Manager OnDemand greatly 
influences the speed at which Content Manager OnDemand can retrieve them. Various hints 
and tips for the optimum way to define reports within Content Manager OnDemand are 
described in Chapter 3, “Administration” on page 45.
13.1.2  System logging
Use Content Manager OnDemand system logging for usage monitoring, charge-back, or 
troubleshooting. Because system logging involves writing all of the selected log messages to 
disk, you incur an increase in both resource usage and response time. Logging increases 
both the amount of the processor that is used and the amount of I/O to disk. For this reason, 
select only the types of logging that you want performed for a particular application group. 
Depending on your system usage requirements, you might decide to perform any of the 
following tasks:
/SM590000Turn off all system logging.
/SM590000Record a minimal amount of information (only the information that is needed for reporting 
functions).
/SM590000Record all transactions.
/SM590000Record the log information to one or more external files by using the system log exit.
/SM590000Turn on system logging only while you troubleshoot the system.
/SM590000Turn on system logging once every time period to sample the system usage patterns.