| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Time_in_runtime_checks |
The percentage of elapsed time spent in performing runtime Code Access Security (CAS) checks during the last measurement period |
Percent |
If this counter is high, revisit what is being checked and how often. The application may be executing unnecessary stack walk depths. Another cause for a high percentage of time spent in runtime checks could be numerous linktime checks. |
| Stack_walk_depth |
The depth of the stack during that last measurement period |
Number |
|
| Queue_length_peak |
The total number of threads that waited to acquire some managed lock during the last measurement period |
Number |
A high turnover rate indicates that items are being quickly added and removed, which can be expensive. |
| Link_time_checks |
The total number of linktime Code Access Security (CAS) checks during the last measurement period |
Number |
The value displayed is not indicative of serious performance issues, but it is indicative of the health of the security system activity. |
| Runtime_checks |
The total number of runtime CAS checks performed during the last measurement period |
Number |
A high number for the total runtime checks along with a high stack walk depth indicates performance overhead. |