The System node give you system performance measures. The memory node lists all memory related performance counters.
The Total lists the total number of bytes allocated for GSEOS block buffer. This corresponds to the setting in the gseos.ini [Buffer] section. The Free count lists the available memory and the Used count the space that is currently occupied by unprocessed blocks. A percentage counter is provided as well. One very important counter is the Alloc Fails counter. This counter should always be zero. If the system can not accocate any space for a new buffer this counter will be incremented and the received data discarded. This means that incoming data was not processed and lost. If this counter is different from zero you might try to increase the buffer space allocated for the use of GSEOS. If this problem still persists, even with an adequately configured buffer the system is overloaded. The System Load counter gives you a measure of the incoming block rate vs. the processed block rate, i.e. if the GSEOS block queue is growing or shrinking. Although temporary higher receive rates cause no problem, if this situation persists the buffer will eventually run out of space. You can use the Tasks view below to get more detailed information which task is taking up the most processing time.
Task
The name of the GSEOS task.
Count
The number of blocks that this task has processed.
Curr. Time
The time in ms this task took to process the last few blocks. This is a sliding average over the last few blocks so you can determine the current performance of the task.
Total Time
The total time in ms this task has been executing.
Avg. Time
The average time in ms needed to process a block. This is the quotient of total time over count.
Out Block Count
If this task also generates blocks the number of generated blocks is indicated by this counter.
Used buffer
The buffer in bytes that is allocated in blocks that have not been processed by this task. This should typically be a small number, ideally zero.
Lost Blocks
The number of blocks that could not be allocated due to insufficient memory. See also the Explorer System node for information on allocation failures. If a task has requested notification of a particular block and this block could not be put on the BDM queue due to allocation failures that lost block counter of this task is incremented. This should not happend and the system needs to be configured to avoid lost blocks. This counter gives you some visibility into the performance of the system.
Ack
A task has to acknowledge the processing of a particular block with the BDM. It will not get notified of new block arrivals until the acknowledgement for the current block is received. If this flag is permanently 'No' the task will not process blocks and there is most likely a bug in the task.
Terminated
If a task has been terminated from processing this flag is set to Yes.
Priority
If this task is a decoder it will have a priority other than 0. Decoders are executed in the order of their priority. None decoder tasks have the lowest priority.
Data Source
If this task is a mutually exclusive data source this flag is set to Yes. Note that no data source should have a priority other than 0. Specifically, decoders should never be data sources.