2019.1

Merge engine
Generally, launching a relatively high number of Merge engines results in better performance,
as Merge engines are involved in the creation of output of all kinds (Print, Email and Web) and
because content creation is relatively time-consuming.
DataMapper engine
Adding DataMapper engines might be useful in the following circumstances:
When large data mapping operations have to be run simultaneously for many jobs When
frequently using PDF or XML based input. Particularly in the case of XML input with large
individual records. When the All-In-One plugin is used often in Workflow configurations and
there are more than two Merge engines running. The Connect MySQL database needs a fast
storage system (SSD or other fast devices) to be able to keep up with two or more DataMapper
engines. When the database is installed on a system with a slow hard drive, adding a
DataMapper engine may not increase the overall performance.
Weaver engine
Adding extra Weaver (Output) engine(s) might be useful when large Print jobs are to be run
simultaneously with smaller Print jobs.
Memory per engine
By default, each engine is set to use up to a predetermined amount of RAM. To make optimum
use of a machine's capabilities it might be useful to increase the amount of memory that the
various engines can use.
l DataMapper engines may perform better with greater memory when running jobs
containing a lot of data.
l For complex templates with a lot of pages per document, there is a chance that Merge
engines will run better with more memory.
l The maximum memory usage of a Weaver engine can be relevant for jobs with heavy
graphics; or for jobs that use Cut & Stack impositioning; or for jobs using particular
variables that entail page buffering (see "Content variables" on page1342).
The Maximum memory per engine setting is found in the Engine Setup preferences.
Page 118