2018.1

installed on a system with a slow hard drive, adding a DataMapper engine may not
increase the overall performance.
Weaver engine
Adding an extra Weaver engine might be useful when large Print jobs have to run
simultaneously with smaller Print jobs.
Memory per engine
By default, each 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 A DataMapper engine may run better with more memory when large jobs bring a lot of
data mapping.
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, for jobs that use Cut & Stack impositioning, and for jobs using particular
variables that entail page buffering (see "Content variables" on page1115).
The Maximum memory per engine setting is found in the scheduling preferences of each
engine type; see "Merge engine scheduling" on page120 and "Weaver engine scheduling" on
page124.
Note that this setting only controls the maximum size of the Java heap memory that an engine
can use; the total amount of memory used by an engine is actually somewhat higher. Also keep
in mind that the Connect Server and the operating system itself need memory to keep running.
Allocating processing power to jobs
Which engine configuration is most efficient in your case depends on how Connect is used.
What kind of output is needed: Print, Email, and/or Web? How often? How big are those jobs?
Do they have to be handled at the same time or in sequence? Would it be useful to give priority
to small, medium or large jobs, and/or to jobs of a certain kind?
Depending on the answers to these questions, you can allocate processing power to jobs in
order to run them as fast as possible, and/or in the order of your preference.
The first step in this process is to define the size of small, medium and large jobs.
Page 112