2018.1

l
Email limit: Enter the maximum number of engines that can run Email jobs.
l
Maximum Email limit in license: Read-only box indicating the maximum number of
engines useable for Email content creation.
l
HTML limit: Enter the maximum number of engines that can run Web jobs.
l
Maximum HTML limit in license: Read-only box indicating the maximum number of
engines useable for Web content creation.
Weaver engine scheduling
A DataMapper engine extracts data from a data file. A Merge engine merges the template and
the data to create Email and Web output, or to create an intermediary file for Printed output. The
intermediary file is in turn used by a Weaver engine to prepare the Print output.
This preference page determines the number of Weaver engines launched, as well as their
speed, when generating the output.
The Weaver Engine is used to convert one specific job into the Print output of your choice. You
can only ever use a single Weaver engine to convert one specific job to whatever output you
want.
The Weaver Engine pool is also used by the Datamapper when importing PCL/PS/PDF and
AFP data.
When you want to create output for multiple jobs in parallel, you will need to increase the
number of weaver engines.
Too many engines will waste precious RAM and CPU cycles to idle processes, whilst too few
could create a bottleneck.
Each Weaver engine requires a speed unit from the available speed unit reservation pool. If no
speed unit is available, the job will be queued even if an engine is available.
For an explanation of the various engines, the terminology and their settings, see "Engine
configuration" on page108.
For some performance tips, see "Performance considerations" on page27.
Page 124