2018.1

1.
Select Window > Preferences... from the menu.
2.
Under Scheduling, select Merge Engine, or Weaver Engine.
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113.)
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.
Batch processing. In a batch processing situation, jobs don't have to be handled
simultaneously. All jobs - whether they are big and small - are processed one after another.
Every job should be handled as quickly as possible. It is therefor recommended to assign the
maximum number of engines and speed units to all jobs. Do not reserve engines or speed units
for certain jobs.
Web requests. In online communication, response times are critical. If the Server receives a lot
of Web requests, it should handle as many as possible, as quickly as possible, at the same
time. It is recommended to launch as many Merge engines as possible and to reserve most of
them for HTML output. The jobs will generally be small and can do with just one Merge engine.
Page 116