Specifying maxSubprocesses sets the maximum number of Arbortext PE sub-processes in the service pool. You can minimize the overhead associated with launching and terminating Arbortext PE sub-processes by setting maxSubprocesses and minSubprocesses to the same number. There is no physical limit to the maximum number you can set, but be aware of the overhead required to run more than you really need to handle the request load.

In most cases, you will achieve the most efficient throughput by setting maxSubprocesses 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.