210 Performance Tuning for Content Manager
query users are using your system; therefore, the optimizer would be more
conservative in assumptions about buffer pool availability.
When setting this parameter, you should estimate the number of complex query
applications that typically use the database. This estimate should exclude all light
OLTP applications.
If you have trouble estimating this number, you can multiply the following two
numbers::
An average number of all applications running against your database. The
database system monitor can provide information about the number of
applications at any given time, and using a sampling technique, you can
calculate an average over a period of time. The information from the database
system monitor includes both OLTP and non-OLTP applications.
Your estimate of the percentage of complex query applications.
As with adjusting other configuration parameters that affect the optimizer, you
should adjust this parameter in small increments. This enables you to minimize
path selection differences.
You should consider rebinding applications (using the rebind package command)
after changing this parameter.
8.6.5 Maximum number of database manager agents (MAXAGENTS)
Impact
DBM - Medium
Description
This parameter indicates the maximum number of database manager agents,
whether coordinator agents or subagents, that are available at any given time to
accept application requests. If you want to limit the number of coordinating
agents, use the MAX_COORDAGENTS parameter.
This parameter can be useful in memory-constrained environments to limit the
total memory usage of the database manager, because each additional agent
requires additional memory.
Default values (range)
200 (1 – 64,000)
400 (1– 64,000) on partitioned database servers with local and remote clients

Get Performance Tuning for Content Manager now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.