2022.1

The Connect MySQL database needs a fast storage system (SSD or other fast devices) to be
able to keep up with two or more DataMapper engines.
When the database is installed on a system with a slow hard drive, adding a DataMapper
engine may not increase the overall performance.
Weaver engine
Adding extra Weaver (Output) engine(s) might be useful when large Print jobs are to be run
simultaneously with smaller Print jobs.
Memory per engine
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.
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1552).
The Maximum memory per engine setting is found in the Engines preferences.
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.
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?
Page 98