|
Measures reported by AspNetAppCacheTest
ASP.NET provides two types of caching that you can use to create high-performance Web applications. The first is called output caching, which allows you to store dynamic page and user control responses on any HTTP 1.1 cache-capable device in the output stream, from the originating server to the requesting browser. On subsequent requests, the page or user control code is not executed; the cached output is used to satisfy the request. The second type of caching is traditional application data caching, which you can use to programmatically store arbitrary objects, such as data sets, to server memory so that your application can save the time and resources it takes to recreate them.
The AspNetAppCacheTest monitors the performance of the ASP.NET Application (or Application Domain) Cache. The measures
made by this test are as
follows:
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Cache_total_entries
|
The current number of entries in the cache (both User and Internal) |
Number
|
 
|
| Cache_hit_ratio
|
The current hit-to-miss ratio of all cache requests (both user and internal) |
Percent
|
Physical I/O takes a significant amount of time, and also increases the CPU resources required. The server configuration should therefore ensure that the required information is available on the memory. A low value of this measure indicates that physical I/O is greater.
|
| Cache_turnover_rate
|
The number of additions and removals to the cache per second (both user and internal) |
Cached/Sec
|
A high turnover rate indicates that items are being quickly added and removed, which can be expensive.
|
| Cache_api_entries
|
The number of entries currently in the user cache |
Number
|
 
|
| Cache_user_hit_ratio
|
Total hit-to-miss ratio of user cache requests
|
Percent
|
A high value of this measure is indicative of the good health of the server.
|
| Cache_user_turnover_rate
|
The number of additions and removals to the user cache per second
|
Cached/Sec
|
A high turnover rate indicates that items are being quickly added and removed, which can be expensive.
|
| Output_cache_entries
|
The number of entries currently in the Output Cache
|
Number
|
 
|
| Output_cache_hit_ratio
|
The total hit-to-miss ratio of Output Cache requests
|
Percent
|
A high value of this measure is a sign of good health.
|
| Output_cache_trnover_rate
|
The number of additions and removals to the output cache per second
|
Cached/Sec
|
If the turnover is high, the cache is not being used effectively.
|
|