Performance Tuning for Content Manager

212 Performance Tuning for Content Manager

To update

Run the following DB2 command:

db2 update dbm cfg using MAX_CONNECTIONS <parameter value>

Our recommendation

Use the default.

8.6.7 Maximum coordinating agents (MAX_COORDAGENTS)

Impact

DBM - Medium

Description

When the connection concentrator is off, (when MAX_CONNECTIONS is equal

to MAX_COORDAGENTS), this parameter determines the maximum number of

coordinating agents that can exist at one time on a server in a partitioned or

non-partitioned database environment.

One coordinating agent is acquired for each local or remote application that

connects to a database or attaches to an instance. Requests that require an

instance attachment include create database, drop database, and database

system monitor commands.

When the connection concentrator is on (that is, when MAX_CONNECTIONS is

greater than MAX_COORDAGENTS), there might be more connections than

coordinator agents to service them. An application is in an active state only if

there is a coordinator agent servicing it. Otherwise, the application is in an

inactive state. Requests from an active application will be serviced by the

database coordinator agent (and subagents in SMP or MPP configurations).

Requests from an inactive application will be queued until a database coordinator

agent is assigned to service the application. This application then becomes

active. As a result, this parameter can be used to control the load on the system.

Default values (range)

-1 (-1, 0 - MAXAGENTS)

For non-partitioned database environments and environments in which

INTRA_PARALLEL is set to no, MAX_COORDAGENTS must equal

MAXAGENTS.

To update

Run the following DB2 command:

db2 update dbm cfg using MAX_COORDAGENTS <parameter value>