Checking System Health

These three categories check the health of your server computer: Processor Cores, Memory and Tasks.

Processor Cores

The check determines if sufficient processor cores are present for the current Automation Engine setup.

For each Automation Engine server (master and assistants):

The number of processor cores is calculated that are required to run the configured number of file streaming sessions (the Viewer) and Gang Run Printing sessions.
- 2 file streaming sessions require 1 processor core. If the number of file streaming sessions is not even, an extra processor core is required.
- 1 gang run printing session requires 1 processor core.
Based on this calculation, if there are not enough processor cores, the resulting status is a warning and a specific message. An example:
The number of processor cores in "name-of-the-server" ({1}) is not sufficient. A system that can run {2} file streaming sessions and {3} gang run printing sessions requires at least {4} processor cores.

For the whole cluster, the remaining number of processor cores is checked against the number of defined processing channels. 1 processing channel requires 1 processor core.

Note: The remaining number of processor cores in the cluster is the sum of all remaining cores in each host after subtracting the ones needed for file streaming and gang run printing sessions.

When there are not enough processor cores to run tasks, the resulting status is a warning and a message appears. An example:

The number of processor cores in the cluster available for running tasks ({0}) is not sufficient. There should be at least {1} processor cores available. Please consider reducing the number of file streaming sessions and/or gang run printing sessions or consider upgrading your cluster.

Memory

This check determines if sufficient memory (RAM) is present for the current Automation Engine setup.

For each Automation Engine server (master and assistants):

The amount of memory is calculated that is required to run the configured number of file streaming sessions (Viewer) and gang run printing sessions. 1 file streaming session requires 1 GB. 1 gang run printing session requires 500 MB.
Based on this calculation, if there are is not enough memory, the resulting status is a warning and a specific message is shown. An example:
The amount of memory in "{hostname}" ({1}) is not sufficient. A system that can run {2} file streaming sessions and {3} gang run printing sessions requires at least {4}.

For the whole cluster, the remaining amount of memory is checked against the number of processing channels defined. 1 processing channel requires 2 GB.

Note: The remaining amount of memory in the cluster = the sum of all remaining memory in each host after subtracting the memory needed for file streaming and gang run printing sessions.

If there is not enough memory to run tasks, the resulting status is a warning and a specific message appears. An example:

The amount of memory in the cluster available for running tasks ({0}) is not sufficient. There should be at least {1} available. Please consider reducing the number of file streaming sessions and/or gang run printing sessions or consider upgrading your cluster.

Tasks

The number of tasks in the tasks database is checked against some predefined thresholds. Also, a check for old tasks is done.

The thresholds depend on the database version:
- For an SQL Express edition, the warning threshold is 30.000, the error threshold is 100.000 .
- For all other database versions, the warning threshold is 200.000, the error threshold is none.
Old tasks are tasks that were launched more than 6 months ago. The check returns a specific message. An example:
The Tasks database contains {0} tasks of which {1} tasks are older than 6 months. Please consider adding cleanup rules for the Tasks database in Configure.