2019.2

may have to wait (or wait longer). However, if the server receives many web requests then
having engines reserved for HTML output can help performance.
l
By reserving a number of parallel engines for Print jobs of a certain size (see "Number
of parallel engines per Print job" on page129). More parallel engines will make them run
faster, but they will have to wait (longer) if the required number of engines isn't available
when they come in.
l
By specifying target speeds for simultaneous Print jobs of a certain size.
All of these engine configuration settings are found in the Parallel Processing Preferences:
1.
Open the Connect Server Configuration utility tool (see "Server Configuration Settings"
on page121).
2.
Under Parallel Processing, check out the information contained in both Content Creation
and Output Creation tabs.
How the Server decides if a job can be handled
In summary, this is how jobs are handled when they can run in parallel.
l Whenever a job comes in, the number of engines to use is determined. (For Print jobs,
this is based on whether the operation is small, medium or large; see "Job size" on
page129.)
l
If there are enough reserved Merge engines for that type of job available then those
engines will be used.
l If there are not enough reserved Merge engines available, then any unreserved Merge
engine that is available will be used.
l If no, or not enough, Merge engines are available then the job will have to wait until the
required number of appropriate Merge engines becomes available.
The following limitations apply at all times:
l The maximum number of concurrent Merge engines working on jobs of the same kind or
size may not be exceeded.
l If no - or not enough - speed units are available for that type of output, the job must wait.
Examples
Here are a few examples of use cases and settings that would be appropriate in such cases.
Page 131