Cache Object
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
The Cache performance object consists of counters that monitor the file system cache, an area of physical memory that stores recently used data as long as possible to permit access to the data without having to read from the disk. Because applications typically use the cache, the cache is monitored as an indicator of application input/output (I/O) operations. When memory is plentiful, the cache can grow, but when memory is scarce, the cache can become too small to be effective.
Counter Name | Description | Counter Type |
---|---|---|
Async Copy Reads/sec |
Shows the rate at which read operations from pages of the file system cache involve a memory copy of the data from the cache to the application's buffer. The application regains control immediately, even if the disk must be accessed to retrieve the page. |
|
Async Data Maps/sec |
Shows the rate at which an application that uses a file system (such as the NTFS file system) to map a page of a file into the file system cache does not wait for the page to be retrieved, if the page is not in main memory. |
|
Async Fast Reads/sec |
Shows the rate at which read operations from the file system cache bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the file system to retrieve data from a file, but this path permits data to be retrieved from the cache directly (without file system involvement) if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided. If the data is not in the cache, the request does not wait until the data has been retrieved from the disk, but gets control immediately. |
|
Async MDL Reads/sec |
Shows the rate at which read operations from the file system cache use a memory descriptor list (MDL) to access the pages. The MDL contains the physical address of each page in the transfer, thus permitting direct memory access (DMA) of the pages. If the accessed pages are not in main memory, the calling application program does not wait for the pages to be retrieved from disk through a page fault. |
|
Async Pin Reads/sec |
Shows the rate at which data is read into the file system cache before writing the data back to disk. Pages read in this fashion are "pinned" in memory at the completion of the read. Pinned pages are those that are read into the file system cache before the system writes data back to the disk at the completion of the read. The file system regains control immediately, even if the disk must be accessed to retrieve the page. While pinned, a page's physical address is not altered. |
|
Copy Read Hits % |
Shows the percentage of cache copy read requests that did not require a disk read to access the page in the cache. A copy read is a file read operation that is satisfied by a memory copy from a page in the cache to the application's buffer. The LAN redirector uses this method for retrieving information from the cache, as does the LAN server for small transfers. This method is also used by the disk file systems. |
|
Copy Reads/sec |
Shows the rate at which read operations from pages of the file system cache involve a copy read. |
|
Data Flush Pages/sec |
Shows the rate at which the file system cache has flushed its contents to disk in response to a request to flush, or to satisfy a write-through file write request. More than one page can be transferred on each flush operation. |
|
Data Flushes/sec |
Shows the rate at which the file system cache has flushed its contents to disk in response to a request to flush, or to satisfy a write-through file write request. |
|
Data Map Hits % |
Shows the percentage of data maps in the file system cache that can be resolved without having to retrieve a page from the disk, because the page is already in physical memory. |
|
Data Map Pins/sec |
Shows the rate at which data maps in the file system cache resulted in pinning a page in main memory. |
|
Data Maps/sec |
Shows the rate at which a file system, such as NTFS, maps a page of a file into the file system cache to read the page. |
|
Fast Read Not Possibles/sec |
Shows the rate at which an application programming interface (API) function call attempts to bypass the file system to get to data in the file system cache that required invoking the file system. |
|
Fast Read Resource Misses/sec |
Shows the rate at which cache misses occur because there are not enough resources to satisfy the request. |
|
Fast Reads/sec |
Shows the rate at which read operations from the file system cache bypass the installed file system and retrieve the data directly from the cache. |
|
Lazy Write Flushes/sec |
Shows the rate at which the Lazy Writer thread writes to disk. |
|
Lazy Write Pages/sec |
Shows the rate at which the Lazy Writer thread has written to disk. |
|
MDL Read Hits % |
Shows the percentage of MDL read requests to the file system cache that did not have to access the disk to provide memory access to the page or pages in the cache. |
|
MDL Reads/sec |
Shows the rate at which read operations from the file system cache use an MDL to access the data. The LAN server uses this method for large transfers out of the server. |
|
Pin Read Hits % |
Shows the percentage of pin read requests that did not have to access the disk to provide access to the page in the file system cache. |
|
Pin Reads/sec |
Shows the rate at which data is read into the file system cache before writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. |
|
Read Aheads/sec |
Shows the rate at which read operations from the file system cache detect sequential access to a file. Read aheads permit data to be transferred in larger blocks than those being requested by the application, reducing the overhead per access. |
|
Sync Copy Reads/sec |
Shows the rate at which read operations from pages of the file system cache involve a memory copy of the data from the cache to the application's buffer. The file system does not regain control until the copy operation is complete, even if the disk must be accessed to retrieve the page. |
|
Sync Data Maps/sec |
Shows the rate at which a file system (such as NTFS) maps a page of a file into the file system cache to read the page, and — if the page is not in main memory — waits for it to be retrieved. |
|
Sync Fast Reads/sec |
Shows the rate at which read operations from the file system cache bypass the installed file system and retrieve the data directly from the cache. |
|
Sync MDL Reads/sec |
Shows the rate at which read operations from the file system cache use an MDL to access the pages. |
|
Sync Pin Reads/sec |
Shows the rate at which data is read into the file system cache before it is written back to disk. Pages read in this fashion are pinned in memory at the completion of the read. |
See Also
Concepts
Finding Cache Bottlenecks
Find memory bottlenecks
Windows Server 2003 System Performance Counters