During initialization, Arbortext Publishing Engine starts its minimum number of Sous-processus Arbortext PE according to a configuration specification. Periodically, Arbortext Publishing Engine checks for idle Sous-processus Arbortext PE and tracks the lifetime duration of each Sous-processus Arbortext PE.

When an HTTP request is passed to Arbortext PE Request Manager, Arbortext Publishing Engine assigns it to the idle Sous-processus Arbortext PE with the least elapsed time since last use. If there is no idle Sous-processus Arbortext PE, Arbortext Publishing Engine will start a new Sous-processus Arbortext PE to handle the request if the maximum number of Sous-processus Arbortext PE allowed is larger than the minimum number. of Sous-processus Arbortext PE.

Finding the right balance of configuration settings depends on your hardware, network traffic, system capabilities, volume and size of requests, and other factors that are particular to your site. In most cases, you will achieve the most efficient throughput by setting the maximum number of Sous-processus Arbortext PE to the number of processors on the Arbortext Publishing Engine server system. This guideline ensures all CPUs will be used and avoids unnecessary context switching, which can hinder throughput.