11.0

Description of counters:

1. ASCT Count – Application Server Communication Threads count. The number of running threads used for

interaction with the Application Server. By default, takes values from 1 to 3. Each thread opens its session.

Additional threads are started if, for the existing threads, latency (ASCT Latency) has reached two seconds.

2. ASCT Latency – Application Server Communication Thread latency (ms). The latency of processing re-

quests in the flows of interaction with the Processing Server. The downtime of queuing requests measured in

milliseconds.

The smaller this value, the better. The ideal value is zero. Values within 1000 (1 second) are the norm.

When the counter value reaches 2 seconds and the maximum number of threads is not running one more

thread is started. When the value reaches 30000 (30 seconds), the Processing Server switches to a critical

mode: it stops taking new tasks and retrieving information about projects on the server until the queue is un-

loaded. Therefore, a long stay is the state > 30 seconds is generally undesirable.

3. Primary Thread Latency – a delay in the response of the Processing Server measured in milliseconds. This

index shows the responsiveness of the server. The increase of this index leads to “freezing” of the Pro-

cessing Server Monitor.

It is desirable that the value of this counter be minimal. This counter is the most critical. The server does not

have auto-adjusting by the value of this counter. A response delay of more the 10 seconds is highly undesir-

able. As a rule, an excessive growth of this counter means that a network interaction with some station is ex-

tremely slow.

Note: With the “view” command of the Processing Server console, you can output the “Server lag time” value

that corresponds to the maximum of the Primary Thread Latency and ASCT Latency values.

4. Task Queue Size the size of the buffer allocated for the task. Includes all tasks displayed in the Processing

Server Monitor as well as some of the tasks deleted over the past 5 minutes. This counter does not matter

much in terms of administration however it can be used to monitor the correlation between the number of

tasks in the Processing Server and the occupied memory.

5. Cores Count – the number of cores in all started (which are in a state Started) Processing Stations of

FlexiCapture.

6. Free Cores – the number of free cores in all started (which are in a state Started) Processing Stations of

FlexiCapture. Allows you to estimate, whether there are enough cores in FlexiCapture.