Performance Tuning for Content Manager

214 Performance Tuning for Content Manager

Based on the system load and the time agents remain idle in the pool, agents

may terminate themselves, as necessary, to reduce the size of the idle pool to

the configured parameter value.

Default values (range)

-1 (-1, 0 - MAXAGENTS)

To update

Run the following DB2 command:

db2 update dbm cfg using NUM_POOLAGENTS <parameter value>

Our recommendation

Use the default -1 (MAXAGENTS), which will enable DB2 to calculate the value.

If you have memory constraints, consider reducing this value gradually, down to

50% of MAXAGENTS. Otherwise, the general rule is to reduce this parameter

value if the system has few applications connected concurrently, and to increase

the value if the system has many applications connected concurrently.

Use the database manager snapshot to monitor this element. If the ratio of

“Agents created from empty pool” divided by “Agents assigned from pool” is high

(5:1 or more), increase NUM_POOLAGENTS. If the ratio is low, then

NUM_POOLAGENTS is probably set too high and there are some agents

wasting system resources.

8.6.10 Maximum number of fenced processes (FENCED_POOL)

Impact

DBM - Medium

Description

For threaded db2fmp processes (processes serving thread-safe stored

procedures and user-defined functions), this parameter represents the number of

threads cached in each db2fmp process. For non-threaded db2fmp processes, this

parameter represents the number of processes that are cached.

If your environment uses fenced stored procedures or user-defined functions,

then this parameter can be used to ensure that an appropriate number of db2fmp

processes are available to process the maximum number of concurrent stored

procedures and user-defined functions, which run on the instance.

If the database manager configuration parameter KEEPFENCED is set to yes

(which is the default), then each db2fmp process that is created in the cache pool