2020.1

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947).
The options available in the Memory group are:
l
Merge Engines (MB) selection: Select the desired amount of Merge Engine memory.
For complex templates with a lot of pages per document, there is a chance that Merge
engines will run better with more memory.
l
Weaver Engine (MB) selection:
Select the desired amount of Weaver (Output)Engine memory.
When running really large jobs, it often pays to increase Weaver memory allocation, even
if only for the duration of the production job(s).
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947).
Multi-threading settings
This group allows you to set Multi-threading rasterization options for form ripping when
generating AFPDSor IPDSoutput.
l
Enable multi-threaded reading check box: This setting controls how the engine reads its
input, with multi-threading reading being the default.
Note
This setting is primarily for trouble shooting. We recommended always leaving
multi-threading on, unless otherwise advised by Support.
Page 85