2018.2

These setting 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?
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.
Job size
Connect lets 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.)
Determining the size of small, medium and large jobs is important because you can assign
more resources to medium and large jobs via the settings for Merge and Weaver engines.
There is no recommendation to make for the number of records in a small, medium or large job.
This setting needs to be based on an assessment of the actual (or expected) workload of
Connect. 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 a large insurance company the same job may
be seen as small. Also take into account that jobs with fewer records could actually be medium
or large if each individual record outputs 10,000 pages.
To set the job sizes:
1.
Select Window > Preferences... from the menu.
2.
Under Scheduling, enter the maximum number of records in a small job. Note that small
jobs always get just one engine, so they should be easily handled by one engine.
3. Enter the minimum number of records in a large job. The number of engines used for
Page 118