These attributes define the number of Sous-processus Arbortext PE running in a pool. The minSubprocesses attribute sets the minimum number of Sous-processus Arbortext PE that will be started and continue to run. The maxSubprocesses attribute sets the maximum number of Sous-processus Arbortext PE that can run in a pool when conditions controlled by other configuration settings are met.

When an Sous-processus Arbortext PE pool initializes, it starts Sous-processus Arbortext PE until the minimum number have been started. If a pool terminates an Sous-processus Arbortext PE and causes the number running to drop below the minimum number configured (refer to The maxIdleInterval Attribute and The maxLifetime Attribute’ for information on configuring terminations), the pool will immediately start a new Sous-processus Arbortext PE.

The maximum number of Sous-processus Arbortext PE must be greater than the minimum number to start additional Sous-processus Arbortext PE if needed to satisfy requests. The pool can't exceed the maximum number of Sous-processus Arbortext PE, which counts both allocated and idle Sous-processus Arbortext PE in the pool.

The default value for both minSubprocesses and maxSubprocesses is 1. Specifying a value less than zero or setting maxSubprocesses less than minSubprocesses is an error.

Ordinarily, set the minimum and maximum numbers of Sous-processus Arbortext PE to the same value to optimize performance. An extra Sous-processus Arbortext PE consumes a certain amount of memory, but even if it is seldom or never asked to service a request, it's a small penalty. If you specify starting a small number of Sous-processus Arbortext PE and allocate more as needed, consider the overhead associated with startup and initialization that can delay fulfilling a request.