System Statistics(5.0)
Usage Engine constantly collects information from the different sub-systems and hosts within the installation system. Using System Statistics, you can view, export and import statistical information used for load balancing and performance tweaking.
There are three different types of statistics: host, pico instance, and workflow.
Toolbar
Option | Description |
|---|---|
Search | Allows users to search and return statistical results based on their search criteria. See Searching the System Statistics for more information. |
Refresh | Performs an update of all the statistical results being displayed. |
Import | Allows users to import statistics that they had exported from System Statistics of the same Usage Engine installation or another Usage Engine installation. See Importing Statistics for more information. |
Export | Allows users to export the statistics on the selected time period. See Exporting Statistics for more information. |
Users can print the displayed statistics graphs and charts. |
Host Statistics
Usage Engine collects statistics from the different machines hosting a Platform or Execution Context. The statistics extracted from the machines can be the load of the CPU or the number of context switches.
Usage Engine uses the vmstat UNIX command to collect the information. Ensure that this command is available in your servers to have statistics collected and to perform load-balancing work for workflows. Note that vmstat may not behave the same on different operating systems.
Statistics | Description |
|---|---|
CPU User Time | This value shows how much time was spent in non-kernel specific code. This value is displayed in percentage. 100% means that all processing power is spent. See CPU System Time as well. |
CPU System Time | This value shows how much time was spent in kernel specific code, such as scheduling of different processes or network transfer. This value is displayed in percentage. 100% means that all processing power is spent. |
Context Switches | The number of context switches per second. A context switch occurs when one process hands over information to another process. The more context switches, the less effective and scalable the system will be. |
Swapped To Disk | The amount of data that was swapped out. A large value indicates that the system does not have enough RAM to manage the memory requirements of the different processes. |
Swapped In From Disk | The amount of data that was read from swap. |
Processes Waiting For Run | Shows how many processes that are waiting to run. A high number indicates that the machine is not fast enough to manage the load. |
Processes In Sleep | The number of processes that are presently not doing anything. |
Pico Instance
Every minute, Usage Engine collects memory information from the different Java processes defining the Platform and the Execution Context. This information shows how much memory is used and how much memory that is available for the running process.
Statistics | Description |
|---|---|
Used Memory | Shows the amount of memory currently allocated by the running process. As Java is a language utilizing garbage collection, this number may very well get close to the maximum memory limit without being a problem for the running process. However, if the amount of used memory is close to the maximum limit for a long time, the process needs more memory. This value is displayed in bytes. |
Maximum Memory | Shows the amount of memory that the process can use. This value is displayed in bytes. |
Process CPU Time | Shows the percentage of CPU time that has been used. |
Open File Descriptors | This is a Unix measurement that enables you to create a statistical diagram over the number of open files during the last minute, hour, or day. |
Garbage Collection Count | Shows the number of times the garbage collector has run since the last time statistics was collected. |
Garbage Collection Time | Shows the amount of time the garbage collector has run since the last time statistics was collected. This value is displayed in milliseconds |
Thread Count | Shows the number of allocated threads. |
Workflow Statistics
Usage Engine collects statistical data that is sampled every 5 seconds as long as a workflow is being executed. This information includes:
Statistics | Description |
|---|---|
Throughput | Displays workflow throughput. As long as a workflow is being executed, Usage Engine continuously samples the amount of processed UDRs, or raw data, per second. |
Queue Throughput | Displays queue throughput per second for real-time queues. Statistics for real-time queues is only available when routing UDRs, not raw data. Note! To enable its convenient delegation to external systems, or to generate an alarm if the throughput falls too low, throughput is also defined as a MIM value for the workflow. For further information, see Throughput Calculation in Workflow Properties Execution Tab(5.0). |
Simultaneous | Displays the number of simultaneously running workflows. |
Queue Size | The size of the queue space that is being used at the time of the sample for each individual queue. |