2019.2

Content Creation Tab (Designer Preferences)
A Tab with data that relates solely to Content Creation.
The options are:
l
Total Merge engines configured read only display: This is a read only entry that shows
the total number of Merge engines available. To change this value, you must update the
Merge Engines in the Engines preferences page.
l
Multi tasking group:
When starting a new Content Creation task, the task will immediately commence if there
is a Merge engine available. How many Merge engines to use is based on the number of
records in the input data.
Select from the following options:
l
Optimize per task:This runs each task with as many Merge engines as needed
(until engines are exhausted).
Using this option means that Merge engines will not be reassigned when new tasks
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.
Page 134