HMI CimView counters provide you with the capability to review the performance of CimView during any single session. A CimView session begins when the first CimView screen is opened and ends when the last open CimView screen is closed. A session can include CimView, Terminal Services and WebView access.
Accumulated totals since a CimView session started
|
For |
Counter |
Counts the Number of: |
|
E |
BitBlts |
Cumulative number of BitBlockTransfers for a CimView session. |
|
N |
Object Redraws |
Cumulative number of times objects are redrawn from the start of a CimView session. For example, each object on a screen is included in the total when the screen opens; animated objects are counted each time they are redrawn. |
|
A |
Events |
Cumulative number of events that have been fired from the start of a CimView session. |
Indicators of current CimView performance
|
For |
Counter |
Displays the |
|
E |
BitBlts/sec |
Current rate (per second) at which the BitBlockTransfers occur during a CimView session. |
|
N |
Object Redraws/sec |
Current rate (per second) that objects are being redrawn in a CimView session. |
|
N |
Open Screens |
The number of open CimView screens. |
|
A |
Event Queue Length |
Current number of events waiting to be fired. |
|
A |
Events per sec |
Current rate (per second) that events are fired in a CimView session. |
Other CimView session indicators
|
For |
Counter |
Displays the |
|
N |
Maximum Cache Size |
The maximum cache size available during a CimView session. CimView, Terminal Services and WebView have individual sizes. A system administrator can change any of the cache sizes for future CimView sessions using CIMPLICITY global parameters. The global parameters are:
|
|
N |
Process ID |
The process number that Windows assigns CimView when a session starts. This number remains constant during a single CimView session. When the session ends and a new session begins, a new number is assigned. |
Expertise Code
|
N |
Novice |
|
A |
Advanced |
|
E |
Expert |
|
|
CIMPLICITY counters. |
