2018.2

Table Of Contents
Job size limits
Job size is a relative concept. In a small service company a job may be considered large when
it counts 1,000 records, whereas in an insurance company the same job may be seen as small.
PrintShop Mail Connectlets you define job sizes by setting the maximum number of records in
a small job, and the minimum number of records in a large job. Jobs that are neither small nor
large are medium sized. (Note that the term 'records' refers to top-level records only. Detail
records are not considered.) These job size limits could have an impact on performance.
l
Small jobs always get just one engine. Do not set the limit for small jobs too high; small
jobs should be easily handled by one engine.
l
The number of engines used for medium and large jobs is configurable.
Which job size limits are ideal in your setup can't be said beforehand. It requires testing to find
the minimum and maximum number of records in jobs that benefit from running with more than
one Merge engine. Take into account that jobs with fewer records could actually be medium or
large if each individual record outputs 10,000 pages.
l
To set the job size limits, select Window > Preferences... from the menu; then go to
Scheduling.
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.
Page 28