2018.1

l
Use one internal engine: Check this option to limit to a single internal engine. Only use
this option on computers that run below the recommended System requirements, or demo
machines. With external engines, both the engines and the server have more memory
and can run faster.
l
Total engines available: Read-only box indicating the current number of engines that are
active or available.
l
Local engines launched: Enter the total number of Datamapper engines desired on this
server.
l
Maximum conversion engines: Enter the maximum number of PS/PCL conversion
requests that can be handled in parallel. PSand PCL input have to be converted to PDF
before data mapping can be performed. For this, a Datamapper engine requests a
conversion engine.
When printing from the Designer, the Designer offloads PCL conversions to the Server
but locally handles PS conversions.
l
Restart after (mins): Due to a currently unfixable memory leak in some libraries used by
PlanetPress Connect, it is necessary to restart our engines after a certain amount of time.
The default is generally sufficient for all our clients. Only change on the advice of a
technical support agent.
l
Max memory usage (mb): An engine restart will be performed when the total amount of
memory used by the engine process exceeds the defined maximum. The default value is
0, which means there is no limit.
If this setting must be used due to memory problems it is recommended to set it to at least
1.5GB or 225% of the memory per engine setting (whichever is higher). The maximum for
this setting is 1024000MB, which roughly corresponds to 1TB.
Note that the actual memory usage is reported in the "Working Set" column in Windows'
Process Explorer.
l
Memory per engine: Specify the maximum random access memory (RAM) to be used
per engine in order to make optimal use of the machine's memory. 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 a bit higher. Also keep in mind that the
system itself needs memory to keep running.
Note
For a Datamapper engine each job is considered a medium-sized job, for the simple reason that the
number of records is not known in advance.
Page 119