During initialization, Arbortext Publishing Engine starts its minimum number of Arbortext PE サブプロセス according to a configuration specification. Periodically, Arbortext Publishing Engine checks for idle Arbortext PE サブプロセス and tracks the lifetime duration of each Arbortext PE サブプロセス.

When an HTTP request is passed to Arbortext PE Request Manager, Arbortext Publishing Engine assigns it to the idle Arbortext PE サブプロセス with the least elapsed time since last use. If there is no idle Arbortext PE サブプロセス, Arbortext Publishing Engine will start a new Arbortext PE サブプロセス to handle the request if the maximum number of Arbortext PE サブプロセス allowed is larger than the minimum number. of 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 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.