2019.2

Specify the maximum amount of random access memory (RAM) in megabytes that will be used
per engine in order to make optimal use of the machine's memory.
The selections made here will apply to all Engines of that type.
Note
These settings only control the maximum size of the Java heap memory that an engine
can use; the total amount of memory that will used by an engine is actually a bit higher.
Also keep in mind that the Connect Server and the operating system itself will need
memory to keep running.
By default, each engine is set to use up to a predetermined amount of RAM. To make optimum
use of a machine's capabilities it might be useful to increase the amount of memory that the
various engines can use.
Here are some simple scenarios where you might want to increase an Engine's memory usage:
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940).
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
Page 89