Performance Tuning for Content Manager

Chapter 8. Tuning DB2 for Content Manager 211

To update

Run the following DB2 command:

db2 update dbm cfg using MAXAGENTS <parameter value>

Our recommendation

Content Manager changes this value to 500 during Library Server installation.

Use this value initially. If you have more clients connecting concurrently, change

this value. The value of MAXAGENTS should be at least the sum of the values

for MAXAPPLS in each database that is allowed to be accessed concurrently.

An agent is created for each Library Server connection. For each retrieve, one or

more agents are created on Resource Manager. Each agent allocates memory. If

you have memory constraints, this parameter can help you limit the memory

usage by limiting the number of concurrent agents.

8.6.6 Maximum number of client connections (MAX_CONNECTIONS)

Impact

DBM - Medium

Description

This parameter controls the maximum number of applications that can be

connected to the instance. Typically, each application is assigned a coordinator

agent. An agent facilitates the operations between the application and the

database.

When the default value (-1) is used, the connection concentrator feature (see

8.6.39, “Connection concentrator” on page 251) is not activated. The value of

MAX_CONNECTIONS will equal the value of MAX_COORDAGENTS. As a

result, each agent operates with its own private memory and shares database

manager and database global resources such as the buffer pool with other

agents.

When the parameter is set to a value greater than the default, then the

connection concentrator is enabled. The intent of the concentrator is to reduce

the server resources per client application to the point where a DB2 Connect

gateway can handle more than 10,000 client connections.

Default values (range)

-1 (-1, MAX_COORDAGENTS – 64,000)