These counters measure the activities for scheduled dispatchers and workers.
Counter name | Type | Definition |
---|---|---|
Active Threads | Meter | Current in-use threads in the scheduled dispatchers pool. Total minus Active yields how many unused threads might be present. Too many unused threads can indicate a requirement to lower the idle timeout. |
Created Threads | Event | Number of threads that are created since the application was started. An excessive number of created threads after the system is warmed up might indicate a requirement to raise the idle timeout to keep more available threads in the pool. |
Threads | Meter | Current number of threads in the scheduled dispatchers pool. Total includes both in-use and available threads |
Total Tasks Completed | Event | Number of scheduled (dispatcher) tasks that are run from the scheduled background thread pool. Overall view of system activity. Running a task to query what work is waiting can result in finding no additional actions are required. This query is counted as an execution even when no work is found. More details about the work of a dispatcher can be found in the counters that are provided by the particular dispatcher task. |
Duration of Task Execution | Duration | The average duration for a task to complete. Because of the diversity of operations that runs on the background threads, the variance in the duration values of a few milliseconds up to much longer time periods can be expected. |
Total Tasks Completed | Event | |
Wait Time for Thread | Duration | For every execution, how long a task waited to be assigned an available thread of execution. For scheduled (dispatcher) tasks, the duration from when the task is set to run and the actual time when the task is assigned a thread. The duration does not include the time that the dispatcher was scheduled to wait. A high average wait time might indicate a requirement to raise the idle timeout to keep more available threads in the pool or a requirement to raise the maximum threads for the pool (pending availability of system resources). |
Counter name | Type | Definition |
---|---|---|
Active Threads | Meter | Current in-use threads in the workers pool. Total minus Active yields how many unused threads might be present. Too many unused threads might indicate a requirement to lower the idle timeout. |
Created Threads | Event | Number of threads that are created since the application was started. An excessive number of created threads after the system is warmed up might indicate a requirement to raise the idle timeout to keep more available threads in the pool. |
Number Queued | Meter | Current workers that are waiting for a thread of execution. An excessive number of queued executions might indicate a requirement to raise the idle timeout to keep more available threads in the pool or a requirement to raise the maximum threads for the pool (pending availability of system resources). |
Threads | Meter | Current number of threads in the workers pool. The total includes both in-use and available threads. |
Total Tasks Completed | Event | How many workers ran from the worker background thread pool. Overall view of system activity. More details about worker processing can be found in the counters that are provided by the particular running task. |
Duration of Task Execution | Duration | The average duration for a task to complete. Because of the diversity of operations that runs on the background threads, the variance in the duration values of a few milliseconds up to much longer time periods can be expected. |
Wait Time for Thread | Duration | For every execution, how long a task waited to be assigned an available thread of execution. A high average wait time might indicate a requirement to raise the idle timeout to keep more available threads in the pool or a requirement to raise the maximum threads for the pool (pending availability of system resources). |