BACK TO INDEX

Win32_PerfFormattedData_PerfOS_Cache
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 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.
NameSpace Path
\ROOT\CIMV2
PROPERTYSMS_REPORTCIMTYPEDESCRIPTION
AsyncCopyReadsPersecUInt32Async Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The application will regain control immediately even if the disk must be accessed to retrieve the page.
AsyncDataMapsPersecUInt32Async Data Maps/sec is the frequency that an application using a file system, such as NTFS, to map a page of a file into the file system cache to read the page, and does not wait for the page to be retrieved if it is not in main memory.
AsyncFastReadsPersecUInt32Async Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests will invoke the appropriate 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 (application program call) will not wait until the data has been retrieved from disk, but will get control immediately.
AsyncMDLReadsPersecUInt32Async MDL Reads/sec is the frequency of reads from the file system cache that 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 page(s) are not in main memory, the calling application program will not wait for the pages to fault in from disk.
AsyncPinReadsPersecUInt32Async Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will regain control immediately even if the disk must be accessed to retrieve the page. While pinned, a page's physical address will not be altered.
CaptionStringA short textual description (one-line string) for the statistic or metric.
CopyReadHitsPercentUInt32Copy Read Hits is the percentage of cache copy read requests that hit the cache, that is, they did not require a disk read in order to provide access to 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 is a method used by the disk file systems as well.
CopyReadsPersecUInt32Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The LAN Redirector uses this method for retrieving information from the file system cache, as does the LAN Server for small transfers. This is a method used by the disk file systems as well.
DataFlushesPersecUInt32Data Flushes/sec is the rate at which the file system cache has flushed its contents to disk as the result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation.
DataFlushPagesPersecUInt32Data Flush Pages/sec is the number of pages the file system cache has flushed to disk as a result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation.
DataMapHitsPercentUInt32Data Map Hits is the percentage of data maps in the file system cache that could be resolved without having to retrieve a page from the disk, because the page was already in physical memory.
DataMapPinsPersecUInt32Data Map Pins/sec is the frequency of data maps in the file system cache that resulted in pinning a page in main memory, an action usually preparatory to writing to the file on disk. While pinned, a page's physical address in main memory and virtual address in the file system cache will not be altered.
DataMapsPersecUInt32Data Maps/sec is the frequency that a file system such as NTFS, maps a page of a file into the file system cache to read the page.
DescriptionStringA textual description of the statistic or metric.
FastReadNotPossiblesPersecUInt32Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass the file system to get to data in the file system cache that could not be honored without invoking the file system.
FastReadResourceMissesPersecUInt32Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request.
FastReadsPersecUInt32Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache 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.
Frequency_ObjectUInt64NA
Frequency_PerfTimeUInt64NA
Frequency_Sys100NSUInt64NA
LazyWriteFlushesPersecUInt32Lazy Write Flushes/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred by each write operation.
LazyWritePagesPersecUInt32Lazy Write Pages/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred on a single disk write operation.
MDLReadHitsPercentUInt32MDL Read Hits is the percentage of Memory Descriptor List (MDL) Read requests to the file system cache that hit the cache, i.e., did not require disk accesses in order to provide memory access to the page(s) in the cache.
MDLReadsPersecUInt32MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the data. The MDL contains the physical address of each page involved in the transfer, and thus can employ a hardware Direct Memory Access (DMA) device to effect the copy. The LAN Server uses this method for large transfers out of the server.
NameStringThe Name property defines the label by which the statistic or metric is known. When subclassed, the property can be overridden to be a Key property.
PinReadHitsPercentUInt32Pin Read Hits is the percentage of pin read requests that hit the file system cache, i.e., did not require a disk read in order to provide access to the page in the file system cache. While pinned, a page's physical address in the file system cache will not be altered. The LAN Redirector uses this method for retrieving data from the cache, as does the LAN Server for small transfers. This is usually the method used by the disk file systems as well.
PinReadsPersecUInt32Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. While pinned, a page's physical address in the file system cache will not be altered.
ReadAheadsPersecUInt32Read Aheads/sec is the frequency of reads from the file system cache in which the Cache detects sequential access to a file. The read aheads permit the data to be transferred in larger blocks than those being requested by the application, reducing the overhead per access.
SyncCopyReadsPersecUInt32Sync Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The file system will not regain control until the copy operation is complete, even if the disk must be accessed to retrieve the page.
SyncDataMapsPersecUInt32Sync Data Maps/sec counts the frequency that a file system, such as NTFS, maps a page of a file into the file system cache to read the page, and wishes to wait for the page to be retrieved if it is not in main memory.
SyncFastReadsPersecUInt32Sync Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache 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 (application program call) will wait until the data has been retrieved from disk.
SyncMDLReadsPersecUInt32Sync MDL Reads/sec is the frequency of reads from the file system cache that 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 page(s) are not in main memory, the caller will wait for the pages to fault in from the disk.
SyncPinReadsPersecUInt32Sync Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will not regain control until the page is pinned in the file system cache, in particular if the disk must be accessed to retrieve the page. While pinned, a page's physical address in the file system cache will not be altered.
Timestamp_ObjectUInt64NA
Timestamp_PerfTimeUInt64NA
Timestamp_Sys100NSUInt64NA
SAMPLE DATA INSTANCE
   [Description("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 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."): ToInstance Amended, DisplayName("Cache"): ToInstance Amended, genericperfctr: ToInstance Amended, locale(1033): ToInstance Amended]
   instance of Win32_PerfFormattedData_PerfOS_Cache
   {
    [Description("Async Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The application will regain control immediately even if the disk must be accessed to retrieve the page."): ToInstance Amended, DisplayName("Async Copy Reads/sec"): ToInstance Amended] AsyncCopyReadsPersec = 0;
    [Description("Async Data Maps/sec is the frequency that an application using a file system, such as NTFS, to map a page of a file into the file system cache to read the page, and does not wait for the page to be retrieved if it is not in main memory."): ToInstance Amended, DisplayName("Async Data Maps/sec"): ToInstance Amended] AsyncDataMapsPersec = 0;
    [Description("Async Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests will invoke the appropriate 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 (application program call) will not wait until the data has been retrieved from disk, but will get control immediately."): ToInstance Amended, DisplayName("Async Fast Reads/sec"): ToInstance Amended] AsyncFastReadsPersec = 0;
    [Description("Async MDL Reads/sec is the frequency of reads from the file system cache that 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 page(s) are not in main memory, the calling application program will not wait for the pages to fault in from disk."): ToInstance Amended, DisplayName("Async MDL Reads/sec"): ToInstance Amended] AsyncMDLReadsPersec = 0;
    [Description("Async Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will regain control immediately even if the disk must be accessed to retrieve the page. While pinned, a page's physical address will not be altered."): ToInstance Amended, DisplayName("Async Pin Reads/sec"): ToInstance Amended] AsyncPinReadsPersec = 0;
    [Description("Copy Read Hits is the percentage of cache copy read requests that hit the cache, that is, they did not require a disk read in order to provide access to 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 is a method used by the disk file systems as well."): ToInstance Amended, DisplayName("Copy Read Hits %"): ToInstance Amended] CopyReadHitsPercent = 0;
    [Description("Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The LAN Redirector uses this method for retrieving information from the file system cache, as does the LAN Server for small transfers. This is a method used by the disk file systems as well."): ToInstance Amended, DisplayName("Copy Reads/sec"): ToInstance Amended] CopyReadsPersec = 0;
    [Description("Data Flushes/sec is the rate at which the file system cache has flushed its contents to disk as the result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation."): ToInstance Amended, DisplayName("Data Flushes/sec"): ToInstance Amended] DataFlushesPersec = 0;
    [Description("Data Flush Pages/sec is the number of pages the file system cache has flushed to disk as a result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation."): ToInstance Amended, DisplayName("Data Flush Pages/sec"): ToInstance Amended] DataFlushPagesPersec = 0;
    [Description("Data Map Hits is the percentage of data maps in the file system cache that could be resolved without having to retrieve a page from the disk, because the page was already in physical memory."): ToInstance Amended, DisplayName("Data Map Hits %"): ToInstance Amended] DataMapHitsPercent = 0;
    [Description("Data Map Pins/sec is the frequency of data maps in the file system cache that resulted in pinning a page in main memory, an action usually preparatory to writing to the file on disk. While pinned, a page's physical address in main memory and virtual address in the file system cache will not be altered."): ToInstance Amended, DisplayName("Data Map Pins/sec"): ToInstance Amended] DataMapPinsPersec = 0;
    [Description("Data Maps/sec is the frequency that a file system such as NTFS, maps a page of a file into the file system cache to read the page."): ToInstance Amended, DisplayName("Data Maps/sec"): ToInstance Amended] DataMapsPersec = 0;
    [Description("Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass the file system to get to data in the file system cache that could not be honored without invoking the file system."): ToInstance Amended, DisplayName("Fast Read Not Possibles/sec"): ToInstance Amended] FastReadNotPossiblesPersec = 0;
    [Description("Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request."): ToInstance Amended, DisplayName("Fast Read Resource Misses/sec"): ToInstance Amended] FastReadResourceMissesPersec = 0;
    [Description("Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache 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."): ToInstance Amended, DisplayName("Fast Reads/sec"): ToInstance Amended] FastReadsPersec = 0;
    [Description("Lazy Write Flushes/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred by each write operation."): ToInstance Amended, DisplayName("Lazy Write Flushes/sec"): ToInstance Amended] LazyWriteFlushesPersec = 0;
    [Description("Lazy Write Pages/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred on a single disk write operation."): ToInstance Amended, DisplayName("Lazy Write Pages/sec"): ToInstance Amended] LazyWritePagesPersec = 0;
    [Description("MDL Read Hits is the percentage of Memory Descriptor List (MDL) Read requests to the file system cache that hit the cache, i.e., did not require disk accesses in order to provide memory access to the page(s) in the cache."): ToInstance Amended, DisplayName("MDL Read Hits %"): ToInstance Amended] MDLReadHitsPercent = 0;
    [Description("MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the data. The MDL contains the physical address of each page involved in the transfer, and thus can employ a hardware Direct Memory Access (DMA) device to effect the copy. The LAN Server uses this method for large transfers out of the server."): ToInstance Amended, DisplayName("MDL Reads/sec"): ToInstance Amended] MDLReadsPersec = 0;
    [Description("Pin Read Hits is the percentage of pin read requests that hit the file system cache, i.e., did not require a disk read in order to provide access to the page in the file system cache. While pinned, a page's physical address in the file system cache will not be altered. The LAN Redirector uses this method for retrieving data from the cache, as does the LAN Server for small transfers. This is usually the method used by the disk file systems as well."): ToInstance Amended, DisplayName("Pin Read Hits %"): ToInstance Amended] PinReadHitsPercent = 0;
    [Description("Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. While pinned, a page's physical address in the file system cache will not be altered."): ToInstance Amended, DisplayName("Pin Reads/sec"): ToInstance Amended] PinReadsPersec = 0;
    [Description("Read Aheads/sec is the frequency of reads from the file system cache in which the Cache detects sequential access to a file. The read aheads permit the data to be transferred in larger blocks than those being requested by the application, reducing the overhead per access."): ToInstance Amended, DisplayName("Read Aheads/sec"): ToInstance Amended] ReadAheadsPersec = 0;
    [Description("Sync Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The file system will not regain control until the copy operation is complete, even if the disk must be accessed to retrieve the page."): ToInstance Amended, DisplayName("Sync Copy Reads/sec"): ToInstance Amended] SyncCopyReadsPersec = 0;
    [Description("Sync Data Maps/sec counts the frequency that a file system, such as NTFS, maps a page of a file into the file system cache to read the page, and wishes to wait for the page to be retrieved if it is not in main memory."): ToInstance Amended, DisplayName("Sync Data Maps/sec"): ToInstance Amended] SyncDataMapsPersec = 0;
    [Description("Sync Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache 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 (application program call) will wait until the data has been retrieved from disk."): ToInstance Amended, DisplayName("Sync Fast Reads/sec"): ToInstance Amended] SyncFastReadsPersec = 0;
    [Description("Sync MDL Reads/sec is the frequency of reads from the file system cache that 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 page(s) are not in main memory, the caller will wait for the pages to fault in from the disk."): ToInstance Amended, DisplayName("Sync MDL Reads/sec"): ToInstance Amended] SyncMDLReadsPersec = 0;
    [Description("Sync Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will not regain control until the page is pinned in the file system cache, in particular if the disk must be accessed to retrieve the page. While pinned, a page's physical address in the file system cache will not be altered."): ToInstance Amended, DisplayName("Sync Pin Reads/sec"): ToInstance Amended] SyncPinReadsPersec = 0;
   };