2019.2

come in.
This option is better suited for batch processing.
l
Maximize simultaneous tasks: Merge engines will be reassigned from a running
task to new tasks when they arrive.
To accommodate as many tasks as possible, the server can dynamically reassign
Merge engines to new tasks as they arrive. Thus a running Content Creation task
need not block other tasks.
If multiple Merge engines are processing a task, an engine can be taken from that
task and reassigned to a new task.
As each task finishes, any freed up Merge engines get re-assigned back to still
running tasks, if no new tasks were waiting.
This option is better for on demand (ad hoc) and simultaneous job processing.
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.
Page 137