2021.1

l Weaver engines always require a Licensed task to run.
l Merge engines only require a Licensed task when creating Email or Web output. Merge
engines involved in a Print process don't need a Licensed task in order to run.
l DataMapper engines don't need Licensed tasks.
In situations where Print and Email and/or Web output are created at the same time, only the
Merge engines that create Email/Web output count towards the maximum number of Licensed
tasks for that type of output.
Spare speed units are distributed proportionally
Since the number of engines is configurable, and jobs may run concurrently, the number of
engines in use may not match the exact number of available Licensed tasks.
When there are more Licensed tasks than there are engines in use, the Connect server
distributes the speed units and the maximum 'pages' per minute to all running jobs in proportion
to the number of engines they are using.
Note
Output speed is the speed at which the output is created by the engine in question. Data
mapping and other steps in a production process are not taken into account. The
throughput speed is the speed of the entire production process. This will always be
lower than the output speed.
Launching multiple engines
One single engine can only process a single job at a time and will run mostly single-threaded.
In order to benefit from multi-core systems it is recommended that several engines run in
parallel.
As a rule of thumb, you will want to run one less engine in total on a machine than the system
has cores, leaving one CPU core free for the Connect Server and the operating system to use.
Modern hardware typically has both full cores and hyper-threading or logical cores. The
logical cores should not be counted as a full core when determining how many engines to use.
As a guide, count logical cores for only 25%-50% of a full core.
For example: on an Intel i7 CPU that comes with 4 cores and 4 additional hyper-threading
Page 97