DB2 10.5 for Linux, UNIX, and Windows

priv_mem_thresh - Private memory threshold configuration parameter

This parameter has been deprecated since Version 9.5, but is still being used by pre-Version 9.5 data servers and clients. Any value specified for this configuration parameter will be ignored by the database manager in DB2® Version 9.5 or later releases.

Note: The following information applies only to pre-Version 9.5 data servers and clients.

Configuration type

Database manager

Applies to

Database server with local and remote clients
Database server with local clients
Partitioned database server with local and remote clients

Parameter type

Configurable

Default [range]

20 000 [-1; 32 - 112 000]

Unit of measure

Pages (4 KB)

This parameter is used to determine the amount of unused agent private memory that will be kept allocated, ready to be used by new agents that are started. It does not apply to Linux and UNIX platforms.

A value of -1 will cause this parameter to use the value of the min_priv_mem parameter.

Recommendation: When setting this parameter, you should consider the client connection/disconnection patterns as well as the memory requirements of other processes on the same machine.

If there is only a brief period during which many clients are concurrently connected to the database, a high threshold will prevent unused memory from being decommitted and made available to other processes. This case results in poor memory management which can affect other processes which require memory.

If the number of concurrent clients is more uniform and there are frequent fluctuations in this number, a high threshold will help to ensure memory is available for the client processes and can reduce the processing time taken to allocate and deallocate memory.