Processing

Concurrent network transfer tasks

The number of FTP and email file transfers (counting both send and receive) allowed to occur in parallel

Concurrent transfers to the same site

The number of file transfers to the same FTP site allowed to occur in parallel (counting both send and receive)

Automatic means that there is no limit other than the overall maximum number of concurrent file transfers as determined by the previous preference

Concurrent processing tasks

The number of job processing tasks allowed to run in parallel

Flow elements: All elements in the Configurator sections of the Flow Elements pane, Assemble job, Execute command, Set hierarchy path, Split multi job, Ungroup job, Monitor confirmation, Pack job, Unpack job, Database connector, Hold job, Inject job, Log job info, Merge PDF, Print PDF, Rename job, Sort by preflight state, Sort files in job, Sort job, Sort on certificate, Split PDF, set hierarchy, compress and uncompress. Also custom scripts (script element) are affected by the number of Concurrent external processes as soon as the script is a "heavy script". (For more details about light an heavy scripts See Execution slots )

Default number of slots for concurrent elements

The number of slots available for scripts and tools working in concurrent mode. By default, this property is set to "1", this will cause a serialized execution mode. Change the number of slots to more than 1 to execute in concurrent mode. Setting this property to "0" means all available slots will be used.

In Switch, this default value from the preferences can be overruled by

1. Setting the flow property Allow advanced performance tuning to yes

2. Changing the element property "number of slots" from default to any other value.

Performance tuning properties and preferences need to be set cautiously because however they are made to speed up processing, unwary use may slow down performance.

Scan input folders every (seconds)

The frequency with which the input folders (i.e. the folders without incoming connections) and submit hierarchies are scanned for newly arrived jobs

Scan intermediate folders every (seconds)

The frequency with which the intermediate folders (i.e. the folders with incoming connections) are scanned for newly arrived jobs

Note that jobs placed in an intermediate folder by Switch are detected and processed immediately and without waiting for the next scan

Process file only after (seconds)

The time for which newly arrived jobs must be stable before they are processed; to avoid picking up an input job before it has been completely written to disk, Switch ensures that the size of the file (or the total size of a job folder) has not changed for at least this amount of time before processing the job

Reactivate flows upon startup

When starting up, if this property is set to yes, Switch automatically reactivates flows that were active when Switch was last closed; otherwise all flows are inactive after startup

Stop processing if free disk space is less than (MB)

If the amount of free disk space for application data is lower than the entered amount, processing will stop, avoiding "Disk Full" processing errors.