Engines preferences
Background
This preferences page allows control over those Connect engine settings.
This page appears in a both the Designer Preferences and the Connect Server Configuration tool preferences, but with some different options between each.
This preference page was remodelled in 2019.2 to improve ease of control over output production settings.
For further background on Engine Configuration, see this page: Engine configuration.
Settings
Configure engine options
-
AFP, PCL and PostScript input have to be converted to PDF before data mapping can be performed. For this, a DataMapper engine will request a conversion engine.
The selection here manages the maximum number of AFP/PCL/PostScript conversion requests that can be handled in parallel.
When printing from the Designer, the Designer offloads AFP/PCL conversions to the Server but locally handles PostScript conversions.Note: AFP input is dependent upon a third party library (CDP), which only allows PReS Connect to run up to 4 AFP input processes on a given machine at a given time.
In a Server Clustering setup these processes can only currently be run on the Main Server. - Tasks handled by:
Note:
Note:
Number of engines
This group is only available if Engines were selected as the processing architecture
- DataMapper Engines selection:
This selection is only available in the Connect Server Configuration utility. It is not available in the Connect Designer Preferences.
Select the desired amount of DataMapper Engines. - When large data mapping operations have to be run simultaneously for many jobs.
- When frequently using PDF or XML based input. Particularly in the case of XML input with large individual records.
- When the All In One plugin is used often in Workflow configurations and there are more than two Merge engines running.
- Merge Engines selection: Select the desired amount of Merge Engines.
Generally, launching a relatively high number of Merge engines results in better performance, as Merge engines are involved in the creation of output of all kinds (Print, Email and Web) and because content creation is relatively time-consuming.
Note: The Connect installer automatically sets the number of Merge Engines based upon the machine CPUs/Processors (the number of cores) and available Memory (RAM). The default setting will likely be enough for most users.
However, virtual machines can provide an exception to this. In some virtual environments the Connect installer cannot accurately determine the number of logical cores actually available to the virtual machine, and will thus use a lesser number than that which could actually be supported.
You can confirm how many Merge engines are running on your machine by running Task Manager and locating the mergeengine.exe entries in your process list.
Note that there will be an extra Merge and Weaver engine in your task manager if you are running Designer.
The Merge engine is responsible for the plugins Create Print Content, Create Email Content and Create Web Content.
License restrictions only apply to the Merge engine when creating Email or Web content. They do not apply for Create Print Content. This means you are allowed to start an infinite amount of Merge engines on any given Connect Sever to run print jobs, but you will be restricted to a set number of Merge engines for your Email and HTML jobs.
Adding DataMapper engines might be useful in the following circumstances:
The Connect MariaDB 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 Engines selection: This option is read-only in PReS Connect Designer Preferences.
Select the desired amount of Weaver (Output) Engines.
Adding extra Weaver (Output) engine(s) might be useful when large Print jobs are to be run simultaneously with smaller Print jobs. However, too many running engines will waste precious RAM and CPU cycles to idle processes, whilst too few could create a bottleneck.
Memory
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:
-
DataMapper engines may perform better with greater memory when running jobs containing a lot of data.
-
For complex templates with a lot of pages per document, there is a chance that Merge engines will run better with more memory.
-
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).
The options available in the Memory group are:
-
DataMapper Engine (MB) selection: This selection is only available in the Connect Server Configuration utility. It is not available in the Connect Designer Preferences.
Select the desired amount of DataMapper Engine memory.
DataMapper engines may perform better with greater memory when running jobs containing a lot of data. -
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. -
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).
Multi-threading settings
This group allows you to set Multi-threading rasterization options for form ripping when generating AFPDS or IPDS output.
- 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.
- Number of multi-threaded form rips selection: Set the amount of individual threads to assign to form ripping.
This setting is useful for when graphics content triggers rasterization when writing AFP or IPDS output. Typical examples of content triggering rasterization are: transparency; fill patterns; gradient fills; or text rotated at a non-right angle.
Increasing the number of threads should speed up Output Creation under such circumstances.Note: How effective this setting is at speeding up the output will depend upon the number of cores available on the processing machine and how many other tasks the machine is running simultaneously.
If only one Output Creation task is running, setting this value as equal to the number of (logical) cores will likely give the best performance.
Buttons
The Engines preferences also provides you with buttons to :
-
Restore Defaults. This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences.
-
Apply: This option applies the settings made within the current Preferences page, but does not close the Preferences dialog.