2021.1

l Additional engine every (records) entry: This controls how many Merge engines
are used for a Content Creation task. It means that for every additional 'x' records in
the task, an additional Merge engine will be used.
For example, with the default 100 record threshold, tasks with 1-100 records will be
assigned 1 Merge engine, tasks with 101-200 get assigned 2 merge engines, tasks
with 201-300 get assigned 3 merge engines, and so on.
Note
These entries aren't applied instantaneously. There is often a lag. That is why
you can reserve a specific number of engines for new jobs, in the options
below. Those reservations operate in real time.
The default of 100 records was chosen purely because it is an easily multiplied
number, not because it has been proven to have any significant value. It means that
on an average system (i.e., less than 10 Merge engines) any decently sized task is
allowed to use all Merge engines. It also assumes that using more than one Merge
engine for less than 100 records will probably not make a big enough difference to
throughput speed. Obviously, there are situations where these assumptions will not
apply.
Note
Currently, it’s only the print and PDF content creation tasks that use multiple
Merge engines.
Parallel Processing properties (Server Configuration)
Whether options are available for selection on this page or not is entirely dependent upon the
Number of engines selection made in the Engines preferences page. If either of the Merge
Engines or Weaver Engines were set to a value beyond one, then options will become
available in this Parallel Processing properties page.
Preset selection (Server Configuration)
Choose from some common usage scenarios. The preset scenarios are:
Page 106