2018.1

l
Under Scheduling - Merge engine you can set the number of Parellel engines per job
for medium and large jobs.
Example
Testing may reveal that jobs between 50 and 250 records benefit from running with 2 Merge
engines, but that running those jobs with more Merge engines doesn't result in higher output
speeds or even takes a bit longer.
In this case, the maximum number of records in a small job should be set to 50; the minimum
number of records in a large job could be set to 250. Subsequently, the Parallel engines per job
setting could be set to 2 for medium jobs, and for large jobs it should be set to the maximum
number of Merge engines available.
Memory per engine
As explained above, PrintShop Mail Connect can be configured to use multiple Merge engines.
By default, each Merge engine, as well as the Datamapper engine and Weaver engine, is set to
use 640MB of RAM. To make optimum use of the machine's capabilities it might be useful to
increase the amount of memory that an engine can use.
l For complex templates with a lot of pages per document, there is a chance that the Merge
engines will run better with more memory.
l For jobs with heavy graphics, jobs that use Cut & Stack impositioning and jobs that use
particular variables that entail page buffering (see "Content variables" on page719), the
maximum memory usage of the Weaver engine can be relevant.
The Maximum memory per engine setting is found in the scheduling preferences of each
engine type; see Merge Engine Scheduling and Weaver Engine Scheduling.
Performance Considerations
This page is a guide to getting the most performance out of PrintShop Mail Connect as well as
a rough guideline to indicate when it's best to upgrade.
Performance analysis details
In PrintShop Mail Connect, after each print job, a message dialog displays a print job summary
(see "Print Job Summary dialog" on page403). This summary may help you determine how
best to maximize the performance of PrintShop Mail Connect.
Page 28