????

Your IP : 18.222.26.253

Current Path : C:/Windows/System32/
Upload File :
Current File : C:/Windows/System32/perfh009.dat

3The System performance object consists of counters that apply to more than one instance of a component processors on the computer.5The Memory performance object  consists of counters that describe the behavior of physical and virtual memory on the computer.  Physical memory is the amount of random access memory on the computer.  Virtual memory consists of the space in physical memory and on disk.  Many of the memory counters monitor paging, which is the movement of pages of code and data between disk and physical memory.  Excessive paging, a symptom of a memory shortage, can cause delays which interfere with all system processes.7% Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the percentage of time that the processor spends executing the idle thread and then subtracting that value from 100%. (Each processor has an idle thread that consumes cycles when no other threads are ready to run). This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. It should be noted that the accounting calculation of whether the processor is idle is performed at an internal sampling interval of the system clock (10ms). On todays fast processors, % Processor Time can therefore underestimate the processor utilization as the processor may be spending a lot of time servicing threads between the system clock sampling interval. Workload based timer applications are one example  of applications  which are more likely to be measured inaccurately as timers are signaled just after the sample is taken.9% Total DPC Time is the average percentage of time that all processors spend receiving and servicing deferred procedure calls (DPCs).  (DPCs are interrupts that run at a lower priority than the standard interrupts). It is the sum of Processor: % DPC Time for all processors on the computer, divided by the number of processors.  System: % Total DPC Time is a component of System: % Total Privileged Time because DPCs are executed in privileged mode.  DPCs are counted separately and are not a component of the interrupt count.  This counter displays the average busy time as a percentage of the sample time.11File Read Operations/sec is the combined rate of file system read requests to all devices on the computer, including requests to read from the file system cache.  It is measured in numbers of reads.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.13File Write Operations/sec is the combined rate of the file system write requests to all devices on the computer, including requests to write to data in the file system cache.  It is measured in numbers of writes. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.15File Control Operations/sec is the combined rate of file system operations that are neither reads nor writes, such as file system control requests and requests for information about device characteristics or status.  This is the inverse of System: File Data Operations/sec and is measured in number of operations perf second.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.17File Read Bytes/sec is the overall rate at which bytes are read to satisfy  file system read requests to all devices on the computer, including reads from the file system cache.  It is measured in number of bytes per second.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.19File Write Bytes/sec is the overall rate at which bytes are written to satisfy file system write requests to all devices on the computer, including writes to the file system cache.  It is measured in number of bytes per second.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.21File Control Bytes/sec is the overall rate at which bytes are transferred for all file system operations that are neither reads nor writes, including file system control requests and requests for information about device characteristics or status.  It is measured in numbers of bytes.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.23% Total Interrupt Time is the average percentage of time that all processors spend receiving and servicing hardware interrupts during sample intervals, where the value is an indirect indicator of the activity of devices that generate interrupts. It is the sum of Processor: % Interrupt Time for of all processors on the computer, divided by the number of processors.  DPCs are counted separately and are not a component of the interrupt count.  This value is an indirect indicator of the activity of devices that generate interrupts, such as the system timer, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices.25Available Bytes is the amount of physical memory, in bytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists.27Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the physical memory which has space reserved on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average.29Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages faulted per second because only one page is faulted in each fault operation, hence this is also equal to the number of page fault operations. This counter includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most processors can handle large numbers of soft faults without significant consequence. However, hard faults, which require disk access, can cause significant delays.31Commit Limit is the amount of virtual memory that can be committed without having to extend the paging file(s).  It is measured in bytes. Committed memory is the physical memory which has space reserved on the disk paging files. There can be one paging file on each logical drive). If the paging file(s) are be expanded, this limit increases accordingly.  This counter displays the last observed value only; it is not an average.33Write Copies/sec is the rate at which page faults are caused by attempts to write that have been satisfied by coping of the page from elsewhere in physical memory. This is an economical way of sharing data since pages are only copied when they are written to; otherwise, the page is shared. This counter shows the number of copies, without regard for the number of pages copied in each operation.35Transition Faults/sec is the rate at which page faults are resolved by recovering pages that were being used by another process sharing the page, or were on the modified page list or the standby list, or were being written to disk at the time of the page fault. The pages were recovered without additional disk activity. Transition faults are counted in numbers of faults; because only one page is faulted in each operation, it is also equal to the number of pages faulted.37Cache Faults/sec is the rate at which faults occur when a page sought in the file system cache is not found and must be retrieved from elsewhere in memory (a soft fault) or from disk (a hard fault). The file system cache is an area of physical memory that stores recently used pages of data for applications. Cache activity is a reliable indicator of most application I/O operations. This counter shows the number of faults, without regard for the number of pages faulted in each operation.39Demand Zero Faults/sec is the rate at which a zeroed page is required to satisfy the fault.  Zeroed pages, pages emptied of previously stored data and filled with zeros, are a security feature of Windows that prevent processes from seeing data stored by earlier processes that used the memory space. Windows maintains a list of zeroed pages to accelerate this process. This counter shows the number of faults, without regard to the number of pages retrieved to satisfy the fault. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.41Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays.  It is the sum of Memory\\Pages Input/sec and Memory\\Pages Output/sec.  It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.43Page Reads/sec is the rate at which the disk was read to resolve hard page faults. It shows the number of reads operations, without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in working set or elsewhere in physical memory, and must be retrieved from disk. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files. Compare the value of Memory\\Pages Reads/sec to the value of Memory\\Pages Input/sec to determine the average number of pages read during each operation.45Processor Queue Length is the number of threads in the processor queue.  Unlike the disk counters, this counter counters, this counter shows ready threads only, not threads that are running.  There is a single queue for processor time even on computers with multiple processors. Therefore, if a computer has multiple processors, you need to divide this value by the number of processors servicing the workload. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent of the workload.47Thread State is the current state of the thread.  It is 0 for Initialized, 1 for Ready, 2 for Running, 3 for Standby, 4 for Terminated, 5 for Wait, 6 for Transition, 7 for Unknown.  A Running thread is using a processor; a Standby thread is about to use one.  A Ready thread wants to use a processor, but is waiting for a processor because none are free.  A thread in Transition is waiting for a resource in order to execute, such as waiting for its execution stack to be paged in from disk.  A Waiting thread has no use for the processor because it is waiting for a peripheral operation to complete or a resource to become free.49Pages Output/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written back to disk only if they are changed in physical memory, so they are likely to hold data, not code. A high rate of pages output might indicate a memory shortage. Windows writes more pages back to disk to free up space when physical memory is in short supply.  This counter shows the number of pages, and can be compared to other counts of pages, without conversion.51Page Writes/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written to disk only if they are changed while in physical memory, so they are likely to hold data, not code.  This counter shows write operations, without regard to the number of pages written in each operation.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.53The Browser performance object consists of counters that measure the rates of announcements, enumerations, and other Browser transmissions.55Announcements Server/sec is the rate at which the servers in this domain have announced themselves to this server.57Pool Paged Bytes is the size, in bytes, of the paged pool, an area of the system virtual memory that is used for objects that can be written to disk when they are not being used.  Memory\\Pool Paged Bytes is calculated differently than Process\\Pool Paged Bytes, so it might not equal Process(_Total)\\Pool Paged Bytes. This counter displays the last observed value only; it is not an average.59Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of the system virtual memory that is used for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated.  Memory\\Pool Nonpaged Bytes is calculated differently than Process\\Pool Nonpaged Bytes, so it might not equal Process(_Total)\\Pool Nonpaged Bytes.  This counter displays the last observed value only; it is not an average.61Pool Paged Allocs is the number of calls to allocate space in the paged pool. The paged pool is an area of the system virtual memory that is used for objects that can be written to disk when they are not being used. It is measured in numbers of calls to allocate space, regardless of the amount of space allocated in each call.  This counter displays the last observed value only; it is not an average.63Pool Paged Resident Bytes is the size, in bytes, of the portion of the paged pool that is currently resident and active in physical memory. The paged pool is an area of the system virtual memory that is used for objects that can be written to disk when they are not being used. This counter displays the last observed value only; it is not an average.65Pool Nonpaged Allocs is the number of calls to allocate space in the nonpaged pool. The nonpaged pool is an area of system memory area for objects that cannot be written to disk, and must remain in physical memory as long as they are allocated.  It is measured in numbers of calls to allocate space, regardless of the amount of space allocated in each call.  This counter displays the last observed value only; it is not an average.67Bytes Total/sec is the total rate of bytes sent to or received from the network by the protocol, but only for the frames (packets) which carry data. This is the sum of Frame Bytes/sec and Datagram Bytes/sec.69System Code Total Bytes is the size, in bytes, of the pageable operating system code currently mapped into the system virtual address space. This value is calculated by summing the bytes in Ntoskrnl.exe, Hal.dll, the boot drivers, and file systems loaded by Ntldr/osloader.  This counter does not include code that must remain in physical memory and cannot be written to disk. This counter displays the last observed value only; it is not an average.71System Code Resident Bytes is the size, in bytes, of the pageable operating system code that is currently resident and active in physical memory. This value is a component of Memory\\System Code Total Bytes. Memory\\System Code Resident Bytes (and Memory\\System Code Total Bytes) does not include code that must remain in physical memory and cannot be written to disk. This counter displays the last observed value only; it is not an average.73System Driver Total Bytes is the size, in bytes, of the pageable virtual memory currently being used by device drivers. Pageable memory can be written to disk when it is not being used. It includes both physical memory (Memory\\System Driver Resident Bytes) and code and data paged to disk. It is a component of Memory\\System Code Total Bytes. This counter displays the last observed value only; it is not an average.75System Driver Resident Bytes is the size, in bytes, of the pageable physical memory being used by device drivers. It is the working set (physical memory area) of the drivers. This value is a component of Memory\\System Driver Total Bytes, which also includes driver memory that has been written to disk. Neither Memory\\System Driver Resident Bytes nor Memory\\System Driver Total Bytes includes memory that cannot be written to disk.77System Cache Resident Bytes is the size, in bytes, of the portion of the system file cache which is currently resident and active in physical memory. The System Cache Resident Bytes and Memory\\Cache Bytes counters are equivalent.  This counter displays the last observed value only; it is not an average.79Announcements Domain/sec is the rate at which a domain has announced itself to the network.81Election Packets/sec is the rate at which browser election packets have been received by this workstation.83Mailslot Writes/sec is the rate at which mailslot messages have been successfully received.85Server List Requests/sec is the rate at which requests to retrieve a list of browser servers have been processed by this workstation.87The 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.89Data 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.91Sync 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.93Async 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.95Data 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.97Data 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.99Pin 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.101Sync 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.103Async 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.105Pin 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.107Copy 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.109Sync 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.111Async 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.113Copy 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.115MDL 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.117Sync 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.119Async 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.121MDL 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.123Read 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.125Fast 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.127Sync 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.129Async 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.131Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request.133Fast 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.135Lazy 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.137Lazy 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.139Data 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.141Data 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.143% User Time is the percentage of elapsed time the processor spends in the user mode. User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems.  The alternative, privileged mode, is designed for operating system components and allows direct access to hardware and all memory.  The operating system switches application threads to privileged mode to access operating system services. This counter displays the average busy time as a percentage of the sample time.145% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode.  When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.147Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another.  Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service.  It is the sum of Thread\\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches.  There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.149Interrupts/sec is the average rate, in incidents per second, at which the processor received and serviced hardware interrupts. It does not include deferred procedure calls (DPCs), which are counted separately. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards, and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended. The system clock typically interrupts the processor every 10 milliseconds, creating a background of interrupt activity. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.151System Calls/sec is the combined rate of calls to operating system service routines by all processes running on the computer. These routines perform all of the basic scheduling and synchronization of activities on the computer, and provide access to non-graphic devices, memory management, and name space management. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.153Level 1 TLB Fills/sec is the frequency of faults that occur when reference is made to memory whose Page Table Entry (PTE) is not in the Translation Lookaside Buffer (TLB).  On some computers this fault is handled by software loading the PTE into the TLB, and this counter is incremented.155Level 2 TLB Fills/sec is the frequency of faults that occur when reference is made to memory whose Page Table Entry (PTE) is not in the Translation Lookaside Buffer (TLB), nor is the page containing the PTE.  On some computers this fault is handled by software loading the PTE into the TLB, and this counter is incremented.157% User Time is the percentage of elapsed time that the process threads spent executing code in user mode. Applications, environment subsystems, and integral subsystems execute in user mode. Code executing in user mode cannot damage the integrity of the Windows executive, kernel, and device drivers. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.159% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service is called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.161Enumerations Server/sec is the rate at which server browse requests have been processed by this workstation.163Enumerations Domain/sec is the rate at which domain browse requests have been processed by this workstation.165Enumerations Other/sec is the rate at which browse requests processed by this workstation are not domain or server browse requests.167Missed Server Announcements is the number of server announcements that have been missed due to configuration or allocation limits.169Missed Mailslot Datagrams is the number of Mailslot Datagrams that have been discarded due to configuration or allocation limits.171Missed Server List Requests is the number of requests to retrieve a list of browser servers that were received by this workstation, but could not be processed.173Virtual Bytes Peak is the maximum size, in bytes, of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. However, virtual space is finite, and the process might limit its ability to load libraries.175Virtual Bytes is the current size, in bytes, of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and the process can limit its ability to load libraries.177Page Faults/sec is the rate at which page faults by the threads executing in this process are occurring.  A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This may not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.179Working Set Peak is the maximum size, in bytes, of the Working Set of this process at any point in time. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before they leave main memory.181Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use.  When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory.183Page File Bytes Peak is the maximum amount of virtual memory, in bytes, that this process has reserved for use in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files.  Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory. If there is no paging file, this counter reflects the maximum amount of virtual memory that the process has reserved for use in physical memory.185Page File Bytes is the current amount of virtual memory, in bytes, that this process has reserved for use in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory. If there is no paging file, this counter reflects the current amount of virtual memory that the process has reserved for use in physical memory.187Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes.189% Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.191% Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.193% User Time is the percentage of elapsed time that this thread has spent executing code in user mode.  Applications, environment subsystems, and integral subsystems execute in user mode.  Code executing in user mode cannot damage the integrity of the Windows NT Executive, Kernel, and device drivers.  Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes.  These subsystem processes provide additional protection.  Therefore, some work done by Windows NT on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.195% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode.  When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.197Context Switches/sec is the rate of switches from one thread to another.  Thread switches can occur either inside of a single process or across processes.  A thread switch can be caused either by one thread asking another for information, or by a thread being preempted by another, higher priority thread becoming ready to run.  Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes.  These subsystem processes provide additional protection.  Therefore, some work done by Windows NT on behalf of an application  appear in other subsystem processes in addition to the privileged time in the application.  Switching to the subsystem process causes one Context Switch in the application thread.  Switching back causes another Context Switch in the subsystem thread.199Current Disk Queue Length is the number of requests outstanding on the disk at the time the performance data is collected. It also includes requests in service at the time of the collection. This is a instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have multiple requests that are active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks. For good performance, this difference should average less than two.201% Disk Time is the percentage of elapsed time that the selected disk drive was busy servicing read or write requests.203% Disk Read Time is the percentage of elapsed time that the selected disk drive was busy servicing read requests.205% Disk Write Time is the percentage of elapsed time that the selected disk drive was busy servicing write requests.207Avg. Disk sec/Transfer is the time, in seconds, of the average disk transfer.209Avg. Disk sec/Read is the average time, in seconds, of a read of data from the disk.211Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk.213Disk Transfers/sec is the rate of read and write operations on the disk.215Disk Reads/sec is the rate of read operations on the disk.217Disk Writes/sec is the rate of write operations on the disk.219Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations.221Disk Read Bytes/sec is the rate at which bytes are transferred from the disk during read operations.223Disk Write Bytes/sec is rate at which bytes are transferred to the disk during write operations.225Avg. Disk Bytes/Transfer is the average number of bytes transferred to or from the disk during write or read operations.227Avg. Disk Bytes/Read is the average number of bytes transferred from the disk during read operations.229Avg. Disk Bytes/Write is the average number of bytes transferred to the disk during write operations.231The Process performance object consists of counters that monitor running application program and system processes.  All the threads in a process share the same address space and have access to the same data.233The Thread performance object consists of counters that measure aspects of thread behavior.  A thread is the basic object that executes instructions on a processor.  All running processes have at least one thread.235The Physical Disk performance object consists of counters that monitor hard or fixed disk drive on a computer.  Disks are used to store file, program, and paging data and are read to retrieve these items, and written to record changes to them.  The values of physical disk counters are sums of the values of the logical disks (or partitions) into which they are divided.237The Logical Disk performance object consists of counters that monitor logical partitions of a hard or fixed disk drives.  Performance Monitor identifies logical disks by their a drive letter, such as C.239The Processor performance object consists of counters that measure aspects of processor activity. The processor is the part of the computer that performs arithmetic and logical computations, initiates operations on peripherals, and runs the threads of processes.  A computer can have multiple processors.  The processor object represents each processor as an instance of the object.241% Total Processor Time is the average percentage of time that all processors on the computer are executing non-idle threads.   This counter was designed as the primary indicator of processor activity on multiprocessor computers.  It is equal to the sum of Process: % Processor Time for all processors, divided by the number of processors.  It is calculated by summing the time that all processors spend executing the thread of the Idle process in each sample interval, subtracting that value from 100%, and dividing the difference by the number of processors on the computer.  (Each processor has an Idle thread which consumes cycles when no other threads are ready to run). For example, on a multiprocessor computer, a value of 50% means that all processors are busy for half of the sample interval, or that half of the processors are busy for all of the sample interval.  This counter displays the average percentage of busy time observed during the sample interval.  It is calculated by monitoring the time the service was inactive, and then subtracting that value from 100%.243% Total User Time is the average percentage of non-idle time all processors spend in user mode.  It is the sum of Processor: % User Time for all processors on the computer, divided by the number of processors.  System: % Total User Time and System: % Total Privileged Time sum to % Total Processor Time, but not always to 100%.  (User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems.  The alternative, privileged mode, is designed for operating system components and allows direct access to hardware and all memory.  The operating system switches application threads to privileged mode to access operating system services). This counter displays the average busy time as a percentage of the sample time.245% Total Privileged Time is the average percentage of non-idle time all processors spend in privileged (kernel) mode.  It is the sum of Processor: % Privileged Time for all processors on the computer, divided by the number of processors.  System: % Total User Time and System: % Total Privileged Time sum to % Total Processor Time, but not always to 100%.  (Privileged mode is an processing mode designed for operating system components which allows direct access to hardware and all memory.  The operating system switches application threads to privileged mode to access operating system services.  The alternative, user mode, is a restricted processing mode designed for applications and environment subsystems). This counter displays the average busy time as a percentage of the sample time.247Total Interrupts/sec is the combined rate of hardware interrupts received and serviced by all processors on the computer It is the sum of Processor: Interrupts/sec for all processors, and divided by the number of processors, and is measured in numbers of interrupts.  It does not include DPCs, which are counted separately.  This value is an indirect indicator of the activity of devices that generate interrupts, such as the system timer, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices.  These devices normally interrupt the processor when they have completed a task or require attention.  Normal thread execution is suspended during interrupts.  Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.249Processes is the number of processes in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  Each process represents the running of a program.251Threads is the number of threads in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  A thread is the basic executable entity that can execute instructions in a processor.253Events is the number of events in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  An event is used when two or more threads try to synchronize execution.255Semaphores is the number of semaphores in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  Threads use semaphores to obtain exclusive access to data structures that they share with other threads.257Mutexes counts the number of mutexes in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  Mutexes are used by threads to assure only one thread is executing a particular section of code.259Sections is the number of sections in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval.  A section is a portion of virtual memory created by a process for storing data. A process can share sections with other processes.261The Object performance object consists of counters that monitor  logical objects in the system, such as processes, threads, mutexes, and semaphores.  This information can be used to detect the unnecessary consumption of computer resources.  Each object requires memory to store basic information about the object.263The Redirector performance object consists of counter that monitor network connections originating at the local computer.265Bytes Received/sec is the rate of bytes coming in to the Redirector from the network.  It includes all application data as well as network protocol information (such as packet headers).267Packets Received/sec is the rate at which the Redirector is receiving packets (also called SMBs or Server Message Blocks).  Network transmissions are divided into packets.  The average number of bytes received in a packet can be obtained by dividing Bytes Received/sec by this counter.  Some packets received might not contain incoming data (for example an acknowledgment to a write made by the Redirector would count as an incoming packet).269Read Bytes Paging/sec is the rate at which the Redirector is attempting to read bytes in response to page faults.  Page faults are caused by loading of modules (such as programs and libraries), by a miss in the Cache (see Read Bytes Cache/sec), or by files directly mapped into the address space of applications (a high-performance feature of Windows NT).271Read Bytes Non-Paging/sec are those bytes read by the Redirector in response to normal file requests by an application when they are redirected to come from another computer.  In addition to file requests, this counter includes other methods of reading across the network such as Named Pipes and Transactions.  This counter does not count network protocol information, just application data.273Read Bytes Cache/sec is the rate at which applications are accessing the file system cache by using the Redirector.  Some of these data requests are satisfied by retrieving the data from the cache.  Requests that miss the Cache cause a page fault (see Read Bytes Paging/sec).275Read Bytes Network/sec is the rate at which applications are reading data across the network. This occurs when data sought in the file system cache is not found there and must be retrieved from the network.  Dividing this value by Bytes Received/sec indicates the proportion of application data traveling across the network. (see Bytes Received/sec).277Bytes Transmitted/sec is the rate at which bytes are leaving the Redirector to the network.  It includes all application data as well as network protocol information (such as packet headers and the like).279Packets Transmitted/sec is the rate at which the Redirector is sending packets (also called SMBs or Server Message Blocks).  Network transmissions are divided into packets.  The average number of bytes transmitted in a packet can be obtained by dividing Bytes Transmitted/sec by this counter.281Write Bytes Paging/sec is the rate at which the Redirector is attempting to write bytes changed in the pages being used by applications.  The program data changed by modules (such as programs and libraries) that were loaded over the network are 'paged out' when no longer needed.  Other output pages come from the file system cache (see Write Bytes Cache/sec).283Write Bytes Non-Paging/sec is the rate at which bytes are written by the Redirector in response to normal file outputs by an application when they are redirected to another computer.  In addition to file requests, this count includes other methods of writing across the network, such as Named Pipes and Transactions.  This counter does not count network protocol information, just application data.285Write Bytes Cache/sec is the rate at which applications on your computer are writing to the file system cache by using the Redirector.  The data might not leave your computer immediately; it can be retained in the cache for further modification before being written to the network.  This saves network traffic.  Each write of a byte into the cache is counted here.287Write Bytes Network/sec is the rate at which applications are writing data across the network. This occurs when the file system cache is bypassed, such as for Named Pipes or Transactions, or when the cache writes the bytes to disk to make room for other data.  Dividing this counter by Bytes Transmitted/sec will indicate the proportion of application data being to the network (see Transmitted Bytes/sec).289File Read Operations/sec is the rate at which applications are asking the Redirector for data. Each call to a file system or similar Application Program Interface (API) call counts as one operation.291Read Operations Random/sec counts the rate at which, on a file-by-file basis, reads are made that are not sequential.  If a read is made using a particular file handle, and then is followed by another read that is not immediately the contiguous next byte, this counter is incremented by one.293Read Packets/sec is the rate at which read packets are being placed on the network.  Each time a single packet is sent with a request to read data remotely, this counter is incremented by one.295Reads Large/sec is the rate at which reads over 2 times the server's negotiated buffer size are made by applications.  Too many of these could place a strain on server resources.  This counter is incremented once for each read. It does not count packets.297Read Packets Small/sec is the rate at which reads less than one-fourth of the server's negotiated buffer size are made by applications.  Too many of these could indicate a waste of buffers on the server.  This counter is incremented once for each read. It does not count packets.299File Write Operations/sec is the rate at which applications are sending data to the Redirector. Each call to a file system or similar Application Program Interface (API) call counts as one operation.301Write Operations Random/sec is the rate at which, on a file-by-file basis, writes are made that are not sequential.  If a write is made using a particular file handle, and then is followed by another write that is not immediately the next contiguous byte, this counter is incremented by one.303Write Packets/sec is the rate at which writes are being sent to the network.  Each time a single packet is sent with a request to write remote data, this counter is incremented by one.305Writes Large/sec is the rate at which writes are made by applications that are over 2 times the server's negotiated buffer size.  Too many of these could place a strain on server resources.  This counter is incremented once for each write: it counts writes, not packets.307Write Packets Small/sec is the rate at which writes are made by applications that are less than one-fourth of the server's negotiated buffer size.  Too many of these could indicate a waste of buffers on the server.  This counter is incremented once for each write: it counts writes, not packets.309Reads Denied/sec is the rate at which the server is unable to accommodate requests for Raw Reads.  When a read is much larger than the server's negotiated buffer size, the Redirector requests a Raw Read which, if granted, would permit the transfer of the data without lots of protocol overhead on each packet.  To accomplish this the server must lock out other requests, so the request is denied if the server is really busy.311Writes Denied/sec is the rate at which the server is unable to accommodate requests for Raw Writes.  When a write is much larger than the server's negotiated buffer size, the Redirector requests a Raw Write which, if granted, would permit the transfer of the data without lots of protocol overhead on each packet.  To accomplish this the server must lock out other requests, so the request is denied if the server is really busy.313Network Errors/sec is the rate at which serious unexpected errors are occurring. Such errors generally indicate that the Redirector and one or more Servers are having serious communication difficulties. For example an SMB (Server Message Block) protocol error is a Network Error. An entry is written to the System Event Log and provide details.315Server Sessions counts the total number of security objects the Redirector has managed.  For example, a logon to a server followed by a network access to the same server will establish one connection, but two sessions.317Server Reconnects counts the number of times your Redirector has had to reconnect to a server in order to complete a new active request.  You can be disconnected by the Server if you remain inactive for too long.  Locally even if all your remote files are closed, the Redirector will keep your connections intact for (nominally) ten minutes.  Such inactive connections are called Dormant Connections.  Reconnecting is expensive in time.319Connects Core counts the number of connections you have to servers running the original MS-Net SMB protocol, including MS-Net itself and Xenix and VAX's.321Connects LAN Manager 2.0 counts connections to LAN Manager 2.0 servers, including LMX servers.323Connects LAN Manager 2.1 counts connections to LAN Manager 2.1 servers, including LMX servers.325Connects Windows NT counts the connections to Windows 2000 or earlier computers.327Server Disconnects counts the number of times a Server has disconnected your Redirector.  See also Server Reconnects.329Server Sessions Hung counts the number of active sessions that are timed out and unable to proceed due to a lack of response from the remote server.331The Server performance object consists of counters that measure communication between the  local computer and the network.333The number of bytes the server has received from the network.  Indicates how busy the server is.335The number of bytes the server has sent on the network.  Indicates how busy the server is.337Thread Wait Reason is only applicable when the thread is in the Wait state (see Thread State).  It is 0 or 7 when the thread is waiting for the Executive, 1 or 8 for a Free Page, 2 or 9 for a Page In, 3 or 10 for a Pool Allocation, 4 or 11 for an Execution Delay, 5 or 12 for a Suspended condition, 6 or 13 for a User Request, 14 for an Event Pair High, 15 for an Event Pair Low, 16 for an LPC Receive, 17 for an LPC Reply, 18 for Virtual Memory, 19 for a Page Out; 20 and higher are not assigned at the time of this writing.  Event Pairs are used to communicate with protected subsystems (see Context Switches).339% DPC Time is the percentage of time that the processor spent receiving and servicing deferred procedure calls (DPCs) during the sample interval. DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a component of % Privileged Time because DPCs are executed in privileged mode. They are counted separately and are not a component of the interrupt counters. This counter displays the average busy time as a percentage of the sample time.341The number of sessions that have been closed due to their idle time exceeding the AutoDisconnect parameter for the server.  Shows whether the AutoDisconnect setting is helping to conserve resources.343The number of sessions that have been closed due to unexpected error conditions or sessions that have reached the autodisconnect timeout and have been disconnected normally. The autodisconnect timeout value represents the number of seconds that idle connections with no session attached to have before being disconnected automatically by a server. The default value is 30 seconds. This counter increments as a result of normal server operation, not as an indication of network problems or unexpected error condition.345The number of sessions that have terminated normally.  Useful in interpreting the Sessions Times Out and Sessions Errored Out statistics--allows percentage calculations.347The number of sessions that have been forced to logoff.  Can indicate how many sessions were forced to logoff due to logon time constraints.349The number of failed logon attempts to the server.  Can indicate whether password guessing programs are being used to crack the security on the server.351The number of times opens on behalf of clients have failed with STATUS_ACCESS_DENIED.  Can indicate whether somebody is randomly attempting to access files in hopes of getting at something that was not properly protected.353The number of times accesses to files opened successfully were denied.  Can indicate attempts to access files without proper access authorization.355The number of times an internal Server Error was detected.  Unexpected errors usually indicate a problem with the Server.357The number of times the server has rejected blocking SMBs due to insufficient count of free work items.  Indicates whether the MaxWorkItem or MinFreeWorkItems server parameters might need to be adjusted.359The number of times STATUS_DATA_NOT_ACCEPTED was returned at receive indication time.  This occurs when no work item is available or can be allocated to service the incoming request.  Indicates whether the InitWorkItems or MaxWorkItems parameters might need to be adjusted.361The number of successful open attempts performed by the server of behalf of clients.  Useful in determining the amount of file I/O, determining overhead for path-based operations, and for determining the effectiveness of open locks.363The number of files currently opened in the server.  Indicates current server activity.365The number of sessions currently active in the server.  Indicates current server activity.367The number of searches for files currently active in the server.  Indicates current server activity.369The number of bytes of non-pageable computer memory the server is using.  This value is useful for determining the values of the MaxNonpagedMemoryUsage value entry in the Windows�NT Registry.371The number of times allocations from nonpaged pool have failed.  Indicates that the computer's physical memory is too small.373The maximum number of bytes of nonpaged pool the server has had in use at any one point.  Indicates how much physical memory the computer should have.375The number of bytes of pageable computer memory the server is currently using.  Can help in determining good values for the MaxPagedMemoryUsage parameter.377The number of times allocations from paged pool have failed.  Indicates that the computer's physical memory or paging file are too small.379The maximum number of bytes of paged pool the server has had allocated.  Indicates the proper sizes of the Page File(s) and physical memory.381Server Announce Allocations Failed/sec is the rate at which server (or domain) announcements have failed due to lack of memory.383Mailslot Allocations Failed is the number of times the datagram receiver has failed to allocate a buffer to hold a user mailslot write.385Mailslot Receives Failed indicates the number of mailslot messages that could not be received due to transport failures.387Mailslot Writes Failed is the total number of mailslot messages that have been successfully received, but that could not be written to the mailslot.389Bytes Total/sec is the rate the Redirector is processing data bytes.  This includes all application and file data in addition to protocol information such as packet headers.391File Data Operations/sec is the rate at which the Redirector is processing data operations. One operation should include many bytes, since each operation has overhead. The efficiency of this path can be determined by dividing the Bytes/sec by this counter to obtain the average number of bytes transferred per operation.393Current Commands counter indicates the number of pending commands from the local computer to all destination servers.  If the Current Commands counter shows a high number and the local computer is idle, this may indicate a network-related problem or a redirector bottleneck on the local computer.395The number of bytes the server has sent to and received from the network.  This value provides an overall indication of how busy the server is.397% Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. suspends normal thread execution during interrupts. This counter displays the average busy time as a percentage of the sample time.399The NWLink NetBIOS performance object consists of counters that monitor IPX transport rates and connections.401Packets/sec is the rate the Redirector is processing data packets.  One packet includes (hopefully) many bytes.  We say hopefully here because each packet has protocol overhead.  You can determine the efficiency of this path by dividing the Bytes/sec by this counter to determine the average number of bytes transferred/packet.  You can also divide this counter by Operations/sec to determine the average number of packets per operation, another measure of efficiency.405Context Blocks Queued per second is the rate at which work context blocks had to be placed on the server's FSP queue to await server action.407File Data Operations/ sec is the combined rate of read and write operations on all logical disks on the computer.  This is the inverse of System: File Control Operations/sec.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.409% Free Space is the percentage of total usable space on the selected logical disk drive that was free.411Free Megabytes displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.413Connections Open is the number of connections currently open for this protocol.  This counter shows the current count only and does not accumulate over time.415Connections No Retries is the total count of connections that were successfully made on the first try.  This number is an accumulator and shows a running total.417Connections With Retries is the total count of connections that were made after retrying the attempt.  A retry occurs when the first connection attempt failed.  This number is an accumulator and shows a running total.419Disconnects Local is the number of session disconnections that were initiated by the local computer.  This number is an accumulator and shows a running total.421Disconnects Remote is the number of session disconnections that were initiated by the remote computer.  This number is an accumulator and shows a running total.423Failures Link is the number of connections that were dropped due to a link failure.  This number is an accumulator and shows a running total.425Failures Adapter is the number of connections that were dropped due to an adapter failure.  This number is an accumulator and shows a running total.427Connection Session Timeouts is the number of connections that were dropped due to a session timeout.  This number is an accumulator and shows a running total.429Connections Canceled is the number of connections that were canceled.  This number is an accumulator and shows a running total.431Failures Resource Remote is the number of connections that failed because of resource problems or shortages on the remote computer.  This number is an accumulator and shows a running total.433Failures Resource Local is the number of connections that failed because of resource problems or shortages on the local computer.  This number is an accumulator and shows a running total.435Failures Not Found is the number of connection attempts that failed because the remote computer could not be found.  This number is an accumulator and shows a running total.437Failures No Listen is the number of connections that were rejected because the remote computer was not listening for connection requests.439Datagrams/sec is the rate at which datagrams are processed by the computer.  This counter displays the sum of datagrams sent and datagrams received.  A datagram is a connectionless packet whose delivery to a remote is not guaranteed.441Datagram Bytes/sec is the rate at which datagram bytes are processed by the computer.  This counter is the sum of datagram bytes that are sent as well as received.  A datagram is a connectionless packet whose delivery to a remote is not guaranteed.443Datagrams Sent/sec is the rate at which datagrams are sent from the computer.  A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.445Datagram Bytes Sent/sec is the rate at which datagram bytes are sent from the computer.  A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.447Datagrams Received/sec is the rate at which datagrams are received by the computer.  A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.449Datagram Bytes Received/sec is the rate at which datagram bytes are received by the computer.  A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.451Packets/sec is the rate at which packets are processed by the computer.  This count is the sum of Packets Sent and Packets Received per second.  This counter includes all packets processed: control as well as data packets.453Packets Sent/sec is the rate at which packets are sent by the computer.  This counter counts all packets sent by the computer, i.e. control as well as data packets.455Packets Received/sec is the rate at which packets are received by the computer.  This counter counts all packets processed: control as well as data packets.457Frames/sec is the rate at which data frames (or packets) are processed by the computer.  This counter is the sum of data frames sent and data frames received.  This counter only counts those frames (packets) that carry data.459Frame Bytes/sec is the rate at which data bytes are processed by the computer.  This counter is the sum of data frame bytes sent and received.  This counter only counts the byte in frames (packets) that carry data.461Frames Sent/sec is the rate at which data frames are sent by the computer.  This counter only counts the frames (packets) that carry data.463Frame Bytes Sent/sec is the rate at which data bytes are sent by the computer.  This counter only counts the bytes in frames (packets) that carry data.465Frames Received/sec is the rate at which data frames are received by the computer.  This counter only counts the frames (packets) that carry data.467Frame Bytes Received/sec is the rate at which data bytes are received by the computer.  This counter only counts the frames (packets) that carry data.469Frames Re-Sent/sec is the rate at which data frames (packets) are re-sent by the computer.  This counter only counts the frames or packets that carry data.471Frame Bytes Re-Sent/sec is the rate at which data bytes are re-sent by the computer.  This counter only counts the bytes in frames that carry data.473Frames Rejected/sec is the rate at which data frames are rejected.  This counter only counts the frames (packets) that carry data.475Frame Bytes Rejected/sec is the rate at which data bytes are rejected.  This counter only counts the bytes in data frames (packets) that carry data.477Expirations Response is the count of T1 timer expirations.479Expirations Ack is the count of T2 timer expirations.481Window Send Maximum is the maximum number of bytes of data that will be sent before waiting for an acknowledgment from the remote computer.483Window Send Average is the running average number of data bytes that were sent before waiting for an acknowledgment from the remote computer.485Piggyback Ack Queued/sec is the rate at which piggybacked acknowledgments are queued. Piggyback acknowledgments are acknowledgments to received packets that are to be included in the next outgoing packet to the remote computer.487Piggyback Ack Timeouts is the number of times that a piggyback acknowledgment could not be sent because there was no outgoing packet to the remote on which to piggyback.  A piggyback ack is an acknowledgment to a received packet that is sent along in an outgoing data packet to the remote computer.  If no outgoing packet is sent within the timeout period, then an ack packet is sent and this counter is incremented.489The NWLink IPX performance object consists of counters that measure datagram transmission to and from computers using the IPX protocol.491The NWLink SPX performance object consist of counters that measure data transmission and session connections for computers using the SPX protocol.493The NetBEUI performance object consists of counters that measure data transmission for network activity which conforms to the NetBIOS End User Interface standard.495The NetBEUI Resource performance object consists of counters that track the use of buffers by the NetBEUI protocol.497Used Maximum is the maximum number of NetBEUI resources (buffers) in use at any point in time.  This value is useful in sizing the maximum resources provided.  The number in parentheses following the resource name is used to identify the resource in Event Log messages.499Used Average is the current number of resources (buffers) in use at this time.  The number in parentheses following the resource name is used to identify the resource in Event Log messages.501Times Exhausted is the number of times all the resources (buffers) were in use.  The number in parentheses following the resource name is used to identify the resource in Event Log messages.503The NBT Connection performance object consists of counters that measure the rates at which bytes are sent and received over the NBT connection between the local computer and a remote computer.  The connection is identified by the name of the remote computer.505Bytes Received/sec is the rate at which bytes are received by the local computer over an NBT connection to some remote computer.  All the bytes received by the local computer over the particular NBT connection are counted.507Bytes Sent/sec is the rate at which bytes are sent by the local computer over an NBT connection to some remote computer.  All the bytes sent by the local computer over the particular NBT connection are counted.509Bytes Total/sec is the rate at which bytes are sent or received by the local computer over an NBT connection to some remote computer.  All the bytes sent or received by the local computer over the particular NBT connection are counted.511The Network Interface performance object consists of counters that measure the rates at which bytes and packets are sent and received over a network connection.  It includes counters that monitor connection errors.513Bytes Total/sec is the rate at which bytes are sent and received over each network adapter, including framing characters. Network Interface\Bytes Total/sec is a sum of Network Interface\Bytes Received/sec and Network Interface\Bytes Sent/sec.515Packets/sec is the rate at which packets are sent and received on the network interface.517Packets Received/sec is the rate at which packets are received on the network interface.519Packets Sent/sec is the rate at which packets are sent on the network interface.521Current Bandwidth is an estimate of the current bandwidth of the network interface in bits per second (BPS).  For interfaces that do not vary in bandwidth or for those where no accurate estimation can be made, this value is the nominal bandwidth.523Bytes Received/sec is the rate at which bytes are received over each network adapter, including framing characters. Network Interface\Bytes Received/sec is a subset of Network Interface\Bytes Total/sec.525Packets Received Unicast/sec is the rate at which (subnet) unicast packets are delivered to a higher-layer protocol.527Packets Received Non-Unicast/sec is the rate at which non-unicast (subnet broadcast or subnet multicast) packets are delivered to a higher-layer protocol.529Packets Received Discarded is the number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their delivery to a higher-layer protocol.  One possible reason for discarding packets could be to free up buffer space.531Packets Received Errors is the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.533Packets Received Unknown is the number of packets received through the interface that were discarded because of an unknown or unsupported protocol.535Bytes Sent/sec is the rate at which bytes are sent over each network adapter, including framing characters. Network Interface\Bytes Sent/sec is a subset of Network Interface\Bytes Total/sec.537Packets Sent Unicast/sec is the rate at which packets are requested to be transmitted to subnet-unicast addresses by higher-level protocols.  The rate includes the packets that were discarded or not sent.539Packets Sent Non-Unicast/sec is the rate at which packets are requested to be transmitted to non-unicast (subnet broadcast or subnet multicast) addresses by higher-level protocols.  The rate includes the packets that were discarded or not sent.541Packets Outbound Discarded is the number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent transmission. One possible reason for discarding packets could be to free up buffer space.543Packets Outbound Errors is the number of outbound packets that could not be transmitted because of errors.545Output Queue Length is the length of the output packet queue (in packets). If this is longer than two, there are delays and the bottleneck should be found and eliminated, if possible. Since the requests are queued by the Network Driver Interface Specification (NDIS) in this implementation, this will always be 0.547The IP performance object consists of counters that measure the rates at which IP datagrams are sent and received by using IP protocols.  It also includes counters that monitor IP protocol errors.549Datagrams/sec is the rate, in incidents per second, at which IP datagrams were received from or sent to the interfaces, including those in error. Forwarded datagrams are not included in this rate.551Datagrams Received/sec is the rate, in incidents per second, at which IP datagrams are received from the interfaces, including those in error. Datagrams Received/sec is a subset of Datagrams/sec.553Datagrams Received Header Errors is the number of input datagrams that were discarded due to errors in the IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.555Datagrams Received Address Errors is the number of input datagrams that were discarded because the IP address in their IP header destination field was not valid for the computer. This count includes invalid addresses (for example, 0.0.  0.0) and addresses of unsupported Classes (for example, Class E). For entities that are not IP gateways and do not forward datagrams, this counter includes datagrams that were discarded because the destination address was not a local address.557Datagrams Forwarded/sec is the rate, in incidents per second, at which attemps were made to find routes to forward input datagrams their final destination, because the local server was not the final IP destination. In servers that do not act as IP Gateways, this rate includes only packets that were source-routed via this entity, where the source-route option processing was successful.559Datagrams Received Unknown Protocol is the number of locally-addressed datagrams that were successfully received but were discarded because of an unknown or unsupported protocol.561Datagrams Received Discarded is the number of input IP datagrams that were discarded even though problems prevented their continued processing (for example, lack of buffer space). This counter does not include any datagrams discarded while awaiting re-assembly.563Datagrams Received Delivered/sec is the rate, in incidents per second, at which input datagrams were successfully delivered to IP user-protocols, including Internet Control Message Protocol (ICMP).565Datagrams Sent/sec is the rate, in incidents per second, at which IP datagrams were supplied for transmission by local IP user-protocols (including ICMP). This counter does not include any datagrams counted in Datagrams Forwarded/sec. Datagrams Sent/sec is a subset of Datagrams/sec.567Datagrams Outbound Discarded is the number of output IP datagrams that were discarded even though no problems were encountered to prevent their transmission to their destination (for example, lack of buffer space). This counter includes datagrams counted in Datagrams Forwarded/sec that meet this criterion.569Datagrams Outbound No Route is the number of IP datagrams that were discarded because no route could be found to transmit them to their destination.  This counter includes any packets counted in Datagrams Forwarded/sec that meet this `no route' criterion.571Fragments Received/sec is the rate, in incidents per second, at which IP fragments that need to be reassembled at this entity are received.573Fragments Re-assembled/sec is the rate, in incidents per second, at which IP fragments were successfully reassembled.575Fragment Re-assembly Failures is the number of failures detected by the IP reassembly algorithm, such as time outs, errors, etc.  This is not necessarily a count of discarded IP fragments since some algorithms (notably RFC 815) lose track of the number of fragments by combining them as they are received.577Fragmented Datagrams/sec is the rate, in incidents per second, at which datagrams are successfully fragmented.579Fragmentation Failures is the number of IP datagrams that were discarded because they needed to be fragmented at but could not be (for example, because the `Don't Fragment' flag was set).581Fragments Created/sec is the rate, in incidents per second, at which IP datagram fragments were generated as a result of fragmentation.583The ICMP performance object consists of counters that measure the rates at which messages are sent and received by using ICMP protocols.  It also includes counters that monitor ICMP protocol errors.585Messages/sec is the total rate, in incidents per second, at which ICMP messages were sent and received by the entity. The rate includes messages received or sent in error.587Messages Received/sec is the rate, in incidents per second at which ICMP messages were received. The rate includes messages received in error.589Messages Received Errors is the number of ICMP messages that the entity received but had errors, such as bad ICMP checksums, bad length, etc.591Received Destination Unreachable is the number of ICMP Destination Unreachable messages received.593Received Time Exceeded is the number of ICMP Time Exceeded messages received.595Received Parameter Problem is the number of ICMP Parameter Problem messages received.597Received Source Quench is the number of ICMP Source Quench messages received.599Received Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were received.601Received Echo/sec is the rate, in incidents per second, at which ICMP Echo messages were received.603Received Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were received.605Received Timestamp/sec is the rate, in incidents per second at which ICMP Timestamp Request messages were received.607Received Timestamp Reply/sec is the rate of ICMP Timestamp Reply messages received.609Received Address Mask is the number of ICMP Address Mask Request messages received.611Received Address Mask Reply is the number of ICMP Address Mask Reply messages received.613Messages Sent/sec is the rate, in incidents per second, at which the server attempted to send. The rate includes those messages sent in error.615Messages Outbound Errors is the number of ICMP messages that were not send due to problems within ICMP, such as lack of buffers.  This value does not include errors discovered outside the ICMP layer, such as those recording the failure of IP to route the resultant datagram.  In some implementations, none of the error types are included in the value of this counter.617Sent Destination Unreachable is the number of ICMP Destination Unreachable messages sent.619Sent Time Exceeded is the number of ICMP Time Exceeded messages sent.621Sent Parameter Problem is the number of ICMP Parameter Problem messages sent.623Sent Source Quench is the number of ICMP Source Quench messages sent.625Sent Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were sent.627Sent Echo/sec is the rate of ICMP Echo messages sent.629Sent Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were sent.631Sent Timestamp/sec is the rate, in incidents per second, at which ICMP Timestamp Request messages were sent.633Sent Timestamp Reply/sec is the rate, in incidents per second,  at which ICMP Timestamp Reply messages were sent.635Sent Address Mask is the number of ICMP Address Mask Request messages sent.637Sent Address Mask Reply is the number of ICMP Address Mask Reply messages sent.639The TCP performance object consists of counters that measure the rates at which TCP Segments are sent and received by using the TCP protocol.  It includes counters that monitor the number of TCP connections in each TCP connection state.641Segments/sec is the rate at which TCP segments are sent or received using the TCP protocol.643Connections Established is the number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.645Connections Active is the number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. In other words, it shows a number of connections which are initiated by the local computer. The value is a cumulative total.647Connections Passive is the number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state. In other words, it shows a number of connections to the local computer, which are initiated by remote computers. The value is a cumulative total.649Connection Failures is the number of times TCP connections have made a direct transition to the CLOSED state from the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.651Connections Reset is the number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.653Segments Received/sec is the rate at which segments are received, including those received in error.  This count includes segments received on currently established connections.655Segments Sent/sec is the rate at which segments are sent, including those on current connections, but excluding those containing only retransmitted bytes.657Segments Retransmitted/sec is the rate at which segments are retransmitted, that is, segments transmitted containing one or more previously transmitted bytes.659The UDP performance object consists of counters that measure the rates at which UDP datagrams are sent and received by using the UDP protocol.  It includes counters that monitor UDP protocol errors.661Datagrams/sec is the rate at which UDP datagrams are sent or received by the entity.663Datagrams Received/sec is the rate at which UDP datagrams are delivered to UDP users.665Datagrams No Port/sec is the rate of received UDP datagrams for which there was no application at the destination port.667Datagrams Received Errors is the number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.669Datagrams Sent/sec is the rate at which UDP datagrams are sent from the entity.671Disk Storage device statistics from the foreign computer673The number of allocation failures reported by the disk storage device675System Up Time is the elapsed time (in seconds) that the computer has been running since it was last started.  This counter displays the difference between the start time and the current time.677The current number of system handles in use.679Free System Page Table Entries is the number of page table entries not currently in used by the system.  This counter displays the last observed value only; it is not an average.681The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.683The current base priority of this process. Threads within a process can raise and lower their own base priority relative to the process' base priority.685The total elapsed time, in seconds, that this process has been running.687Alignment Fixups/sec is the rate, in incidents per seconds, at alignment faults were fixed by the system.689Exception Dispatches/sec is the rate, in incidents per second, at which exceptions were dispatched by the system.691Floating Emulations/sec is the rate of floating emulations performed by the system.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.693Logon/sec is the rate of all server logons.695The current dynamic priority of this thread.  The system can raise the thread's dynamic priority above the base priority if the thread is handling user input, or lower it towards the base priority if the thread becomes compute bound.697The current base priority of this thread.  The system can raise the thread's dynamic priority above the base priority if the thread is handling user input, or lower it towards the base priority if the thread becomes compute bound.699The total elapsed time (in seconds) this thread has been running.701The Paging File performance object consists of counters that monitor the paging file(s) on the computer.  The paging file is a reserved space on disk that backs up committed physical memory on the computer.703The amount of the Page File instance in use in percent.  See also Process\\Page File Bytes.705The peak usage of the Page File instance in percent.  See also Process\\Page File Bytes Peak.707Starting virtual address for this thread.709Current User Program Counter for this thread.711Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.713Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.715Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Read/Write protection allows a process to read, modify and write to these pages.717Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have write access to this shared memory, a copy of that memory is made.719Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.721Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Execute/Read Only memory is memory that can be executed as well as read.723Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Execute/Read/Write memory is memory that can be executed by programs as well as read and modified.725Mapped Space is virtual memory that has been mapped  to a specific virtual address (or range of virtual addresses) in the process' virtual address space.  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.727Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.729Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.731Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Read/Write protection allows a process to read, modify and write to these pages.733Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made.735Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.737Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Execute/Read Only memory is memory that can be executed as well as read.739Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Execute/Read/Write memory is memory that can be executed by programs as well as read and modified.741The Image performance object consists of counters that monitor the virtual address usage of images executed by processes on the computer.743Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed.  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.745Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.747Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.749Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Read/Write protection allows a process to read, modify and write to these pages.751Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.753Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.755Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Execute/Read Only memory is memory that can be executed as well as read.757Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Execute/Read/Write memory is memory that can be executed by programs as well as read and written.759Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process.  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.761Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.763Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.765Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Read/Write protection allows a process to read, modify and write to these pages.767Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.769Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.771Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Execute/Read-Only memory is memory that can be executed as well as read.773Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Execute/Read/Write memory is memory that can be executed by programs as well as read and written and modified.775Image Space is the virtual address space in use by the images being executed by the process.  This is the sum of all the address space with this protection allocated by images run by the selected process  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.777Bytes Image Reserved is the sum of all virtual memory reserved by images within this process.779Bytes Image Free is the amount of virtual address space that is not in use or reserved by images within this process.781Bytes Reserved is the total amount of virtual memory reserved for future use by this process.783Bytes Free is the total unused virtual address space of this process.785ID Process is the unique identifier of this process. ID Process numbers are reused, so they only identify a process for the lifetime of that process.787The Process Address Space performance object consists of counters that monitor memory allocation and use  for a selected process.789Image Space is the virtual address space in use by the selected image with this protection.  No Access protection prevents a process from writing or reading these pages and will generate an access violation if either is attempted.791Image Space is the virtual address space in use by the selected image with this protection.  Read Only protection prevents the contents of these pages from being modified.  Any attempts to write or modify these pages will generate an access violation.793Image Space is the virtual address space in use by the selected image with this protection.  Read/Write protection allows a process to read, modify and write to these pages.795Image Space is the virtual address space in use by the selected image with this protection.  Write Copy protection is used when memory is shared for reading but not for writing.  When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.797Image Space is the virtual address space in use by the selected image with this protection.  Executable memory is memory that can be executed by programs, but cannot be read or written.  This type of protection is not supported by all processor types.799Image Space is the virtual address space in use by the selected image with this protection.  Execute/Read Only memory is memory that can be executed as well as read.801Image Space is the virtual address space in use by the selected image with this protection.  Execute/Read/Write memory is memory that can be executed by programs as well as read and written.803Image Space is the virtual address space in use by the selected image with this protection.  Execute Write Copy is memory that can be executed by programs as well as read and written.  This type of protection is used when memory needs to be shared between processes.  If the sharing processes only read the memory, then they will all use the same memory.  If a sharing process desires write access, then a copy of this memory will be made for that process.805ID Thread is the unique identifier of this thread.  ID Thread numbers are reused, so they only identify a thread for the lifetime of that thread.807Mailslot Opens Failed/sec indicates the rate at which mailslot messages to be delivered to mailslots that are not present are received by this workstation.809Duplicate Master Announcements indicates the number of times that the master browser has detected another master browser on the same domain.811Illegal Datagrams/sec is the rate at which incorrectly formatted datagrams have been received by the workstation.813Announcements Total/sec is the sum of Announcements Server/sec and Announcements Domain/sec.815Enumerations Total/sec is the rate at which browse requests have been processed by this workstation.  This is the sum of Enumerations Server/sec, Enumerations Domain/sec, and Enumerations Other/sec.817The Thread Details performance object  consists of counters that measure aspects of thread behavior that are difficult or time-consuming or collect.  These counters are distinguished from those in the Thread object by their high overhead.819Cache Bytes the size, in bytes, of the portion of the system file cache which is currently resident and active in physical memory. The Cache Bytes and Memory\\System Cache Resident Bytes counters are equivalent.  This counter displays the last observed value only; it is not an average.821Cache Bytes Peak is the maximum number of bytes used by the system file cache since the system was last restarted. This might be larger than the current size of the cache. This counter displays the last observed value only; it is not an average.823Pages Input/sec is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation. Compare the value of Memory\\Pages Input/sec to the value of  Memory\\Page Reads/sec to determine the average number of pages read into memory during each read operation.825Transition Pages RePurposed is the rate at which the number of transition cache pages were reused for a different purpose.  These pages would have otherwise remained in the page cache to provide a (fast) soft fault (instead of retrieving it from backing store) in the event the page was accessed in the future.  Note these pages can contain private or sharable memory.873The number of bytes transmitted total for this connection.875The number of bytes received total for this connection.877The number of data frames transmitted total for this connection.879The number of data frames received total for this connection.881The compression ratio for bytes being transmitted.883The compression ratio for bytes being received.885The total number of CRC Errors for this connection.  CRC Errors occur when the frame received contains erroneous data.887The total number of Timeout Errors for this connection.  Timeout Errors occur when an expected is not received in time.889The total number of Serial Overrun Errors for this connection.  Serial Overrun Errors occur when the hardware cannot handle the rate at which data is received.891The total number of Alignment Errors for this connection.  Alignment Errors occur when a byte received is different from the byte expected.893The total number of Buffer Overrun Errors for this connection.  Buffer Overrun Errors when the software cannot handle the rate at which data is received.895The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.897The number of bytes transmitted per second.899The number of bytes received per second.901The number of frames transmitted per second.903The number of frames received per second.905The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.909The total number of Remote Access connections.921The WINS Server performance object consists of counters that monitor communications using the WINS Server service.923Unique Registrations/sec is the rate at which unique registration are received by the WINS server.925Group Registrations/sec is the rate at which group registration are received by the WINS server.927Total Number of Registrations/sec is the sum of the Unique and Group registrations per sec.  This is the total rate at which registration are received by the WINS server.929Unique Renewals/sec is the rate at which unique renewals are received by the WINS server.931Group Renewals/sec is the rate at which group renewals are received by the WINS server.933Total Number of Renewals/sec is the sum of the Unique and Group renewals per sec.  This is the total rate at which renewals are received by the WINS server.935Total Number of Releases/sec is the rate at which releases are received by the WINS server.937Total Number of Queries/sec is the rate at which queries are received by the WINS server.939Unique Conflicts/sec is the rate at which unique registrations/renewals received by the WINS server resulted in conflicts with records in the database.941Group Conflicts/sec is the rate at which group registration received by the WINS server resulted in conflicts with records in the database.943Total Number of Conflicts/sec is the sum of the Unique and Group conflicts per sec.  This is the total rate at which conflicts were seen by the WINS server.945Total Number of Successful Releases/sec947Total Number of Failed Releases/sec949Total Number of Successful Queries/sec951Total Number of Failed Queries/sec953The total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in this process.1001Services for Macintosh AFP File Server.1003The maximum amount of paged memory resources used by the MacFile Server.1005The current amount of paged memory resources used by the MacFile Server.1007The maximum amount of nonpaged memory resources use by the MacFile Server.1009The current amount of nonpaged memory resources used by the MacFile Server.1011The number of sessions currently connected to the MacFile server.  Indicates current server activity.1013The maximum number of sessions connected at one time to the MacFile server.  Indicates usage level of server.1015The number of internal files currently open in the MacFile server.  This count does not include files opened on behalf of Macintosh clients.1017The maximum number of internal files open at one time in the MacFile server.  This count does not include files opened on behalf of Macintosh clients.1019The number of failed logon attempts to the MacFile server.  Can indicate whether password guessing programs are being used to crack the security on the server.1021The number of bytes read from disk per second.1023The number of bytes written to disk per second.1025The number of bytes received from the network per second.  Indicates how busy the server is.1027The number of bytes sent on the network per second.  Indicates how busy the server is.1029The number of outstanding work items waiting to be processed.1031The maximum number of outstanding work items waiting at one time.1033The current number of threads used by MacFile server.  Indicates how busy the server is.1035The maximum number of threads used by MacFile server.  Indicates peak usage level of server.1051AppleTalk Protocol1053Number of packets received per second by Appletalk on this port.1055Number of packets sent per second by Appletalk on this port.1057Number of bytes received per second by Appletalk on this port.1059Number of bytes sent per second by Appletalk on this port.1061Average time in milliseconds to process a DDP packet on this port.1063Number of DDP packets per second received by Appletalk on this port.1065Average time in milliseconds to process an AARP packet on this port.1067Number of AARP packets per second received by Appletalk on this port.1069Average time in milliseconds to process an ATP packet on this port.1071Number of ATP packets per second received by Appletalk on this port.1073Average time in milliseconds to process an NBP packet on this port.1075Number of NBP packets per second received by Appletalk on this port.1077Average time in milliseconds to process a ZIP packet on this port.1079Number of ZIP packets per second received by Appletalk on this port.1081Average time in milliseconds to process an RTMP packet on this port.1083Number of RTMP packets per second received by Appletalk on this port.1085Number of ATP requests retransmitted on this port.1087Number of ATP release timers that have expired on this port.1089Number of ATP Exactly-once transaction responses per second on this port.1091Number of ATP At-least-once transaction responses per second on this port.1093Number of ATP transaction release packets per second received on this port.1095The current amount of nonpaged memory resources used by AppleTalk.1097Number of packets routed in on this port.1099Number of packets dropped due to resource limitations on this port.1101Number of ATP requests retransmitted to this port.1103Number of packets routed out on this port.1111Provides Network Statistics for the local network segment via the Network Monitor Service.1113The total number of frames received per second on this network segment.1115The number of bytes received per second on this network segment.1117The number of Broadcast frames received per second on this network segment.1119The number of Multicast frames received per second on this network segment.1121Percentage of network bandwidth in use on this network segment.1125Percentage of network bandwidth which is made up of broadcast traffic on this network segment.1127Percentage of network bandwidth which is made up of multicast traffic on this network segment.1151The Telephony System1153The number of telephone lines serviced by this computer.1155The number of telephone devices serviced by this computer.1157The number of telephone lines serviced by this computer that are currently active.1159The number of telephone devices that are currently being monitored.1161The rate of outgoing calls made by this computer.1163The rate of incoming calls answered by this computer.1165The number of applications that are currently using telephony services.1167Current outgoing calls being serviced by this computer.1169Current incoming calls being serviced by this computer.1233Packet Burst Read NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Read.  Packet Burst is a windowing protocol that improves performance.1235Packet Burst Read Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Read Request because the NetWare server took too long to respond.1237Packet Burst Write NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Write.  Packet Burst is a windowing protocol that improves performance.1239Packet Burst Write Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Write Request because the NetWare server took too long to respond.1241Packet Burst IO/sec is the sum of Packet Burst Read NCPs/sec and Packet Burst Write NCPs/sec.1261Logon Total indicates the total session setup attempts, including all successful logon and failed logons since the server service is started.1263The total number of durable handle disconnects that have occurred.1265The total number of durable handles that are successfully reconnected. The ratio of "reconnected durable handles"/"total durable handles" indicates the stability gain from reconnect durable handles.1267The number of SMB BranchCache hash requests that were for the header only received by the server. This indicates how many requests are being done to validate hashes that are already cached by the client.1269The number of SMB BranchCache hash generation requests that were sent by SRV2 to the SMB Hash Generation service because a client requested hashes for the file and there was either no hash content for the file or the existing hashes were out of date.1271The number of SMB BranchCache hash requests that were received by the server.1273The number of SMB BranchCache hash responses that have been sent from the server.1275The amount of SMB BranchCache hash data sent from the server. This includes bytes transferred for both hash header requests and full hash data requests.1277The total number of resilient handle disconnect that have occurred.1279The total number of resilient handles that are successfully reconnected. The ratio of "reconnected resilient handles"/"total resilient handles" indicates the stability gain from reconnect resilient handles.1301The Server Work Queues performance object consists of counters that monitor the length of the queues and objects in the queues.1303Queue length is the current number of workitem in Blocking queues and Nonblocking queues, which indicates how busy the server is to process outstanding workitems for this CPU. A sustained queue length greater than four might indicate processor congestion.  This is an instantaneous count, not an average over time.1305Active Threads is the number of threads currently working on a request from the server client for this CPU.  The system keeps this number as low as possible to minimize unnecessary context switching.  This is an instantaneous count for the CPU, not an average over time.1307Available Threads is the number of server threads on this CPU not currently working on requests from a client.  The server dynamically adjusts the number of threads to maximize server performance.1309Every request from a client is represented in the server as a 'work item,' and the server maintains a pool of available work items per CPU to speed processing.  This is the instantaneous number of available work items for this CPU.  A sustained near-zero value indicates the need to increase the MinFreeWorkItems registry value for the Server service.  This value will always be 0 in the SMB1 Blocking Queue instance.1311Every request from a client is represented in the server as a 'work item,' and the server maintains a pool of available work items per CPU to speed processing.  When a CPU runs out of work items, it borrows a free work item from another CPU.  An increasing value of this running counter might indicate the need to increase the 'MaxWorkItems' or 'MinFreeWorkItems' registry values for the Server service.  This value will always be 0 in the Blocking Queue and SMB2 Queue instances.1313Every request from a client is represented in the server as a 'work item,' and the server maintains a pool of available work items per CPU to speed processing.  A sustained value greater than zero indicates the need to increase the 'MaxWorkItems' registry value for the Server service.  This value will always be 0 in the Blocking Queue and SMB2 Queue instances.1315Current Clients is the instantaneous count of the clients being serviced by this CPU.  The server actively balances the client load across all of the CPU's in the system.  This value will always be 0 in the Blocking Queue instance.1317The rate at which the Server is receiving bytes from the network clients on this CPU.  This value is a measure of how busy the Server is.1319The rate at which the Server is sending bytes to the network clients on this CPU.  This value is a measure of how busy the Server is.1321The rate at which the Server is sending and receiving bytes with the network clients on this CPU.  This value is a measure of how busy the Server is.1323Read Operations/sec is the rate the server is performing file read operations for the clients on this CPU.  This value is a measure of how busy the Server is.  This value will always be 0 in the Blocking Queue instance.1325Read Bytes/sec is the rate the server is reading data from files for the clients on this CPU.  This value is a measure of how busy the Server is.1327Write Operations/sec is the rate the server is performing file write operations for the clients on this CPU.  This value is a measure of how busy the Server is.  This value will always be 0 in the Blocking Queue instance.1329Write Bytes/sec is the rate the server is writing data to files for the clients on this CPU.  This value is a measure of how busy the Server is.1331Total Bytes/sec is the rate the Server is reading and writing data to and from the files for the clients on this CPU.  This value is a measure of how busy the Server is.1333Total Operations/sec is the rate the Server is performing file read and file write operations for the clients on this CPU.  This value is a measure of how busy the Server is.  This value will always be 0 in the Blocking Queue instance.1335DPCs Queued/sec is the average rate, in incidents per second, at which deferred procedure calls (DPCs) were added to the processor's DPC queue. DPCs are interrupts that run at a lower priority than standard interrupts.  Each processor has its own DPC queue. This counter measures the rate that DPCs are added to the queue, not the number of DPCs in the queue.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.1337DPC Rate is the rate at which deferred procedure calls (DPCs) were added to the processors DPC queues between the timer ticks of the processor clock. DPCs are interrupts that run at alower priority than standard interrupts.  Each processor has its own DPC queue. This counter measures the rate that DPCs were added to the queue, not the number of DPCs in the queue. This counter displays the last observed value only; it is not an average.1343Total DPCs Queued/sec is the combined rate at which deferred procedure calls (DPCs) are added to the DPC queue of all processors on the computer.  (DPCs are interrupts that run at a lower priority than standard interrupts). Each processor has its own DPC queue.  This counter measures the rate at which DPCs are added to the queue, not the number of DPCs in the queue.  It is the sum of Processor: DPCs Queued/sec for all processors on the computer, divided by the number of processors.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.1345Total DPC Rate is the combined rate at which deferred procedure calls (DPCs) are added to the DPC queues of all processors between timer ticks of each processor's system clock.  (DPCs are interrupts that run at a lower priority than standard interrupts). Each processor has its own DPC queue.  This counter measures the rate at which DPCs are added to the queue, not the number of DPCs in the queue.  It is the sum of Processor: DPC Rate for all processors on the computer, divided by the number of processors.  This counter displays the last observed value only; it is not an average.1351% Registry Quota In Use is the percentage of the Total Registry Quota Allowed that is currently being used by the system.  This counter displays the current percentage value only; it is not an average.1361Counters that indicate the status of local and system Very Large memory allocations.1363VLM % Virtual Size In Use1365Current size of the process VLM Virtual memory space in bytes.1367The peak size of the process VLM virtual memory space in bytes.  This value indicates the maximum size of the process VLM virtual memory since the process started.1369The current size of the process VLM virtual memory space in bytes that may be allocated.  Note that the maximum allocation allowed may be smaller than this value due to fragmentation of the memory space.1371The current size of committed VLM memory space for the current process in bytes.1373The peak size of the committed VLM memory space in bytes for the current process since the process started.1375The current size of all committed VLM memory space in bytes for the system.1377The peak size of all committed VLM memory space in bytes since the system was started.1379The current size of all committed shared VLM memory space in bytes for the system.1381Available KBytes is the amount of physical memory, in Kilobytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists.1383Available MBytes is the amount of physical memory, in Megabytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists.1401Avg. Disk Queue Length is the average number of both read and write requests that were queued for the selected disk during the sample interval.1403Avg. Disk Read Queue Length is the average number of read requests that were queued for the selected disk during the sample interval.1405Avg. Disk Write Queue Length is the average number of write requests that were queued for the selected disk during the sample interval.1407% Committed Bytes In Use is the ratio of Memory\\Committed Bytes to the Memory\\Commit Limit. Committed memory is the physical memory in use for which space has been reserved in the paging file should it need to be written to disk. The commit limit is determined by the size of the paging file.  If the paging file is enlarged, the commit limit increases, and the ratio is reduced). This counter displays the current percentage value only; it is not an average.1409The Full Image performance object consists of counters that monitor the virtual address usage of images executed by processes on the computer.  Full Image counters are the same counters as contained in Image object with the only difference being the instance name.  In the Full Image object, the instance name includes the full file path name of the loaded modules, while in the Image object only the filename is displayed.1411The Creating Process ID value is the Process ID of the process that created the process. The creating process may have terminated, so this value may no longer identify a running process.1413The rate at which the process is issuing read I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.1415The rate at which the process is issuing write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.1417The rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.1419The rate at which the process is issuing I/O operations that are neither read nor write operations (for example, a control function). This counter counts all I/O activity generated by the process to include file, network and device I/Os.1421The rate at which the process is reading bytes from I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.1423The rate at which the process is writing bytes to I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.1425The rate at which the process is reading and writing bytes in I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.1427The rate at which the process is issuing bytes to I/O operations that do not involve data such as control operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.1451Displays performance statistics about a Print Queue.1453Total number of jobs printed on a print queue since the last restart.1455Number of bytes per second printed on a print queue.1457Total number of pages printed through GDI on a print queue since the last restart.1459Current number of jobs in a print queue.1461Current number of references (open handles) to this printer.1463Peak number of references (open handles) to this printer.1465Current number of spooling jobs in a print queue.1467Maximum number of spooling jobs in a print queue since last restart.1469Total number of out of paper errors in a print queue since the last restart.1471Total number of printer not ready errors in a print queue since the last restart.1473Total number of job errors in a print queue since last restart.1475Total number of calls from browse clients to this print server to request network browse lists since last restart.1477Total number of calls from other print servers to add shared network printers to this server since last restart.1479Working Set - Private displays the size of the working set, in bytes, that is use for this process only and not shared nor sharable by other processes.1481Working Set - Shared displays the size of the working set, in bytes, that is sharable and may be used by other processes.  Because a portion of a process' working set is shareable, does not necessarily mean that other processes are using it.1483% Idle Time reports the percentage of time during the sample interval that the disk was idle.1485Split IO/Sec reports the rate at which I/Os to the disk were split into multiple I/Os. A split I/O may result from requesting data of a size that is too large to fit into a single I/O or that the disk is fragmented.1501Reports the accounting and processor usage data collected by each active named Job object.1503Current % Processor Time shows the percentage of the sample interval that the processes in the Job object spent executing code.1505Current % User mode Time shows the percentage of the sample interval that the processes in the Job object spent executing code in user mode.1507Current % Kernel mode Time shows the percentage of the sample interval that the processes in the Job object spent executing code in kernel or privileged mode.1509This Period mSec - Processor shows the time, in milliseconds, of processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since a time limit on the Job was established.1511This Period mSec - User mode shows the time, in milliseconds, of user mode processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since a time limit on the Job was established.1513This Period mSec - Kernel mode shows the time, in milliseconds, of kernel mode processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since a time limit on the Job was established.1515Pages/Sec shows the page fault rate of all the processes in the Job object.1517Process Count - Total shows the number of processes, both active and terminated, that are or have been associated with the Job object.1519Process Count - Active shows the number of processes that are currently associated with the Job object.1521Process Count - Terminated shows the number of processes that have been terminated because of a limit violation.1523Total mSec - Processor shows the time, in milliseconds, of processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since the Job object was created.1525Total mSec - User mode shows the time, in milliseconds, of user mode processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since the Job object was created.1527Total mSec - Kernel mode shows the time, in milliseconds, of kernel mode processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since the Job object was created.1537Received Packet Too Big is the number of received packets thatare larger than anticipated.1539Received Membership Query is the number of packets received thatquery their membership to a group.1541Received Membership Report is the number of packets received thatreport their membership to a group.1543Received Membership Reduction is the number of packets received thatcancelled their membership to a group.1545Received Router Solicit is the number of packets received thatsolicit the router.1547Received Router Advert is the number of packets received thatadvert the router.1549% Job object Details shows detailed performance information about the active processes that make up a Job object.1551Received Neighbor Solicit is the number of packets received thatsolicit a neighbor.1553Received Neighbor Advert is the number of packets received thatadvert a neighbor.1555Sent Packet Too Big is the number of sent packets thatare larger than anticipated.1557Sent Membership Query is the number of packets sent thatquery their membership to a group.1559Sent Membership Report is the number of packets sent thatreport their membership to a group.1561Sent Membership Reduction is the number of packets sent thatcancelled their membership to a group.1563Sent Router Solicit is the number of packets sent thatsolicit the router.1565Sent Router Advert is the number of packets sent thatadvert the router.1567Sent Neighbor Solicit is the number of packets sent thatsolicit a neighbor.1569Sent Neighbor Advert is the number of packets sent thatadvert a neighbor.1571These counters track authentication performance on a per second basis.1573This counter tracks the number of NTLM authentications processed per second for the AD on this DC or for local accounts on this member server.1575This counter tracks the number of times that clients use a ticket to authenticate to this computer per second.1577This counter tracks the number of Authentication Service (AS) requests that are being processed by the Key Distribution Center (KDC) per second. Clients use AS requests to obtain a ticket-granting ticket.1579This counter tracks the number of ticket-granting service (TGS) requests that are being processed by the Key Distribution Center (KDC) per second. Clients use these TGS requests to obtain a service ticket, which allows a client to access resources on other computers.1581This counter tracks the number of Secure Sockets Layer (SSL) entries that are currently stored in the secure channel (Schannel) session cache.  The Schannel session cache stores information about successfully established sessions, such as SSL session IDs.  Clients can use this information to reconnect to a server without performing a full SSL handshake.1583This counter tracks the number of Secure Sockets Layer (SSL) entries that are currently stored in the secure channel (Schannel) session cache and that are currently in use.  The Schannel session cache stores information about successfully established sessions, such as SSL session IDs.  Clients can use this information to reconnect to a server without performaing a full SSL handshake.1585This counter tracks the number of Secure Sockets Layer (SSL) full client-side handshakes that are being processed per second.  During a handshake, signals are exchanged to acknowledge that communication can occur between computers or other devices.1587This counter tracks the number of Secure Sockets Layer (SSL) client-side reconnect handshakes that are being processed per second.  Reconnect handshakes allow session keys from previous SSL sessions to be used to resume a client/server connection, and they require less memory to process than full handshakes.1589This counter tracks the number of Secure Sockets Layer (SSL) full server-side handshakes that are being processed per second.  During a handshake, signals are exchanged to acknowledge that communication can occur between computers or other devices.1591This counter tracks the number of Secure Sockets Layer (SSL) server-side reconnect handshakes that are being processed per second.  Reconnect handshakes allow session keys from previous SSL sessions to be used to resume a client/server connection, and they require less memory to process than full handshakes.1593This counter tracks the number of Digest authentications that are being processed per second.1595This counter tracks the number of Kerberos requests that a read-only domain controller (RODC) forwards to its hub, per second.  This counter is tracked only on a RODC.1597Offloaded Connections is the number of TCP connections (over both IPv4 and IPv6) that are currently handled by the TCP chimney offload capable network adapter.1599TCP Active RSC Connections is the number of TCP connections (over both IPv4 and IPv6) that are currently receiving large packets from the RSC capable network adapter on this network interface.1601TCP RSC Coalesced Packets/sec shows the large packet receive rate across all TCP connections on this network interface.1603TCP RSC Exceptions/sec shows the RSC exception rate for receive packets across all TCP connections on this network interface.1605TCP RSC Average Packet Size is the average size in bytes of received packets across all TCP connections on this network interface.1621This counter tracks the number of armored Authentication Service (AS) requests that are being processed by the Key Distribution Center (KDC) per second.1623This counter tracks the number of armored ticket-granting service (TGS) requests that are being processed by the Key Distribution Center (KDC) per second.1625This counter tracks the number of Authentication Service (AS) requests explicitly requesting claims that are being processed by the Key Distribution Center (KDC) per second.1627This counter tracks the number of service asserted identity (S4U2Self) TGS requests that are explicitly requesting claims. These requests are being processed by the Key Distribution Center (KDC) per second.1629This counter tracks the number of constrained delegation (S4U2Proxy) TGS requests that are being processed by the Key Distribution Center (KDC) by checking classic type constrained delegation configuration per second. The classic type constrained delegation is restricted to a single domain and configures the backend services SPN on the middle-tier service�s account object.1631This counter tracks the number of constrained delegation (S4U2Proxy) TGS requests that are being processed by the Key Distribution Center (KDC) by checking the resource type constrained delegation per second. The resource type constrained delegation can cross domain boundaries and configures the middle-tier�s account on the backend service�s account object.1633This counter tracks the number of claims-aware ticket-granting service (TGS) requests that are being processed by the Key Distribution Center (KDC) per second. A claims-aware Kerberos client will always request claims during Authentication Service (AS) exchanges.1635This counter tracks the number of key trust Authentication Service (AS) requests that are being processed by the Key Distribution Center (KDC) per second.1671These counters track the number of security resources and handles used per process.1673This counter tracks the number of credential handles in use by a given process.  Credential handles are handles to pre-existing credentials, such as a password, that are associated with a user and are established through a system logon.1675This counter tracks the number of context handles in use by a given process.  Context handles are associated with security contexts established between a client application and a remote peer.1677Free & Zero Page List Bytes is the amount of physical memory, in bytes, that is assigned to the free and zero page lists. This memory does not contain cached data. It is immediately available for allocation to a process or for system use.1679Modified Page List Bytes is the amount of physical memory, in bytes, that is assigned to the modified page list. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. This memory needs to be written out before it will be available for allocation to a process or for system use.1681Standby Cache Reserve Bytes is the amount of physical memory, in bytes, that is assigned to the reserve standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.1683Standby Cache Normal Priority Bytes is the amount of physical memory, in bytes, that is assigned to the normal priority standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.1685Standby Cache Core Bytes is the amount of physical memory, in bytes, that is assigned to the core standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.1687Long-Term Average Standby Cache Lifetime, in seconds. The average lifetime of data in the standby cache over a long interval is measured.1747% Idle Time is the percentage of time the processor is idle during the sample interval1749% C1 Time is the percentage of time the processor spends in the C1 low-power idle state. % C1 Time is a subset of the total processor idle time. C1 low-power idle state enables the processor to maintain its entire context and quickly return to the running state. Not all systems support the % C1 state.1751% C2 Time is the percentage of time the processor spends in the C2 low-power idle state. % C2 Time is a subset of the total processor idle time. C2 low-power idle state enables the processor to maintain the context of the system caches. The C2 power state is a lower power and higher exit latency state than C1. Not all systems support the C2 state.1753% C3 Time is the percentage of time the processor spends in the C3 low-power idle state. % C3 Time is a subset of the total processor idle time. When the processor is in the C3 low-power idle state it is unable to maintain the coherency of its caches. The C3 power state is a lower power and higher exit latency state than C2. Not all systems support the C3 state.1755C1 Transitions/sec is the rate that the CPU enters the C1 low-power idle state. The CPU enters the C1 state when it is sufficiently idle and exits this state on any interrupt. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.1757C2 Transitions/sec is the rate that the CPU enters the C2 low-power idle state. The CPU enters the C2 state when it is sufficiently idle and exits this state on any interrupt. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.1759C3 Transitions/sec is the rate that the CPU enters the C3 low-power idle state. The CPU enters the C3 state when it is sufficiently idle and exits this state on any interrupt. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.1761Heap performance counters for must used heaps1763Memory actively used by this heap (FreeBytes + AllocatedBytes)1765Total virtual address space reserved for this heap (includes uncommitted ranges)1767ReservedBytes minus last uncommitted range in each segment1769Memory on freelists in this heap (does not include uncommitted ranges or blocks in heap cache)1771Number of blocks on the list of free blocks >1k in size17731/Average time per allocation (excluding allocs from heap cache)17751/Average time per free (excluding frees to heap cache)1777Number of uncommitted ranges in the reserved virtual address1779Difference between number of allocations and frees (for leak detection)1781Allocations/sec from heap cache1783Frees/sec from heap cache1785Allocations/sec of size <1k bytes (including heap cache)1787Frees/sec of size <1k bytes (including heap cache)1789Allocations/sec of size 1-8k bytes1791Frees/sec of size 1-8k bytes1793Allocations/sec of size over 8k bytes1795Frees/sec of size over 8k bytes1797Allocations/sec (including from heap cache)1799Frees/sec (including to heap cache)1801Total number of blocks in the heap cache1803Largest number of blocks of any one size in the heap cache1805(FreeBytes / CommittedBytes) *1001807(VirtualBytes / ReservedBytes) * 1001809Collisions/sec on the heap lock1811Total number of dirty pages on the system cache1813Threshold for number of dirty pages on system cache1815Counters that report approximate memory utilization statistics per node on NUMA systems.1817Total amount of physical memory associated with a NUMA node in megabytes.1819Approximate amount of physical memory on the free and zero page lists for a NUMA node, in megabytes.1821The Network Adapter performance object consists of counters that measure the rates at which bytes and packets are sent and received over a physical or virtual network connection.  It includes counters that monitor connection errors.1823Approximate amount of physical memory on the standby page list for a NUMA node, in megabytes. This counter is available only on 64-bit systems.1825Approximate amount of physical memory available for allocation for a NUMA node, in megabytes. Computed as the sum of memory on the zeroed, free, and standby lists for a NUMA node. This counter is available only on 64-bit systems.1827The number of SMB BranchCache hash V2 requests that were for the header only received by the server. This indicates how many requests are being done to validate hashes that are already cached by the client.1829The number of SMB BranchCache hash V2 generation requests that were sent by SRV2 to the SMB Hash Generation service because a client requested hashes for the file and there was either no hash content for the file or the existing hashes were out of date.1831The number of SMB BranchCache hash V2 requests that were received by the server.1833The number of SMB BranchCache hash V2 responses that have been sent from the server.1835The amount of SMB BranchCache hash V2 data sent from the server. This includes bytes transferred for both hash header requests and full hash data requests.1837The amount of SMB BranchCache hash V2 requests that were served from dedup store by the server.1847End Marker1849.Net CLR Data1851Current number of connections, pooled or not.1853Current number of connections in all pools associated with the process.1855Current number of pools associated with the process.1857The highest number of connections in all pools since the process started.1859The total number of connection open attempts that have failed for any reason.1861The total number of command executes that have failed for any reason.1863Counters for System.Data.SqlClient1865The number of actual connections per second that are being made to servers1867The number of actual disconnects per second that are being made to servers1869The number of connections we get from the pool per second1871The number of connections we return to the pool per second1873The number of connections that are not using connection pooling1875The number of connections that are managed by the connection pooler1877The number of unique connection strings1879The number of unique connection strings waiting for pruning1881The number of active connection pools1883The number of inactive connection pools1885The number of connections currently in-use1887The number of connections currently available for use1889The number of connections currently waiting to be made ready for use1891The number of connections we reclaim from GCed external connections1893Terminal Services per-session resource monitoring.1895Microsoft Distributed Transaction Coordinator performance counters1897Number of currently active transactions1899Number of committed transactions1901Number of aborted transactions1903Number of in doubt transactions1905Maximum number of transactions ever concurrently active1907Number of transactions committed by the system administrator1909Number of transactions aborted by the system administrator1911Minimum time delta between transaction begin and commit1913Average time delta between transaction begin and commit1915Maximum time delta between transaction begin and commit1917Transactions performed per second1919Transactions committed per second1921Transactions aborted per second1923MSDTC Bridge 4.0.0.0 performance counters1925The number of WS-AT protocol messages that the WS-AT service failed to send per second.1927The number of Prepare retry messages that the WS-AT service has sent per second.1929The number of Commit retry messages that the WS-AT service has sent per second.1931The number of Prepared retry messages that the WS-AT service has sent per second.1933The number of Replay retry messages that the WS-AT service has sent per second.1935The number of Fault messages that the WS-AT service has received per second.1937The number of Fault messages that the WS-AT service has sent per second.1939Average time in milliseconds for the WS-AT service to receive a Prepare message response from a participant.1941Base counter for the 'Average participant prepare response time' counter.1943Average time in milliseconds for the WS-AT service to receive a Commit message response from a participant.1945Base counter for the 'Average participant commit response time' counter.1947Help not available.1949The cumulative total number of socket connections established for this process since the process was started.1951The cumulative total number of bytes received over all open socket connections since the process was started. This number includes data and any protocol information that is not defined by the TCP/IP protocol.1953The cumulative total number of bytes sent over all open socket connections since the process was started. This number includes data and any protocol information that is not defined by the TCP/IP protocol.1955The cumulative total number of datagram packets received since the process was started.1957The cumulative total number of datagram packets sent since the process was started.1959Displays the current bulk transfer rate in bytes/sec.1961Displays the current isochronous transfer rate in bytes/sec.1963Displays the current interrupt transfer rate in bytes/sec.1965Displays the current control transfer rate in bytes/sec.1967Displays the rate of PCI interrupt generation by the USB controller. For controller instances only.1969Displays the current rate Work Signals generated per second by the usbport driver.  For controller instances only.1971Displays the percentage of BW reserved for interrupt transfers1973Displays the percentage of BW reserved for ISO transfers1975USB I/O Counters1977Displays the average size of all transfer URBs. For device instances only.1979Number of ISO packets that are NOT late, but complete with an error. For device instances only.1981Avg number of ms between the current frame and the start frame of an ISO transfer when scheduled.  For device instances only.1983Number of Transfer URBs completing with an error status. For device instances only.1985Non-zero value if the host controller is not running(idle).1987Non-Zero value if the host controller async schedule is not running(idle).1989Incremented each time the controller async cache is flushed.1991Non-Zero if the periodic schedule is not running(idle).1993Incremented each time the controller periodic cache is flushed.1995System.Runtime.Caching.MemoryCache Performance Counters1997The number of cache hits.1999The number of cache misses.2001The percentage of cache hits in the total number of cache requests.2003Cache Hit Ratio Base2005Total number of entries removed from the cache due to memory pressure or Trim invocations.2007The number of entries within the cache.2009The number of entries added to the cache or removed from the cache per second.2011Windows Workflow Foundation Performance Counters2013Total number of workflows created.2015Rate of workflows created per second.2017Total number of workflows unloaded.2019Rate of workflows unloaded per second.2021Total number of workflows loaded.2023Rate of workflows loaded per second.2025Total number of workflows completed.2027Rate of workflows completed per second.2029Total number of workflows suspended.2031Rate of workflows suspended per second.2033Total number of workflows terminated.2035Rate of workflows terminated per second.2037Total number of workflows in memory.2039Total number of workflows aborted.2041Rate of workflows aborted per second.2043Total number of workflows persisted.2045Rate of workflows persisted per second.2047Total number of workflow instances actively executing.2049Rate of workflows becoming idle per second.2051Total number of workflows ready to execute.2053Total number of workflows waiting for a thread.2055Counters for System.Data.OracleClient2057The number of actual connections per second that are being made to servers2059The number of actual disconnects per second that are being made to servers2061The number of connections we get from the pool per second2063The number of connections we return to the pool per second2065The number of connections that are not using connection pooling2067The number of connections that are managed by the connection pooler2069The number of unique connection strings2071The number of unique connection strings waiting for pruning2073The number of active connection pools2075The number of inactive connection pools2077The number of connections currently in-use2079The number of connections currently available for use2081The number of connections currently waiting to be made ready for use2083The number of connections we reclaim from GCed external connections2085Process Level Statistics for User Input Delay2087Session Level Statistics for User Input Delay2089Maximum value for queuing delay across all user input waiting to be picked-up by the process during a target time interval2091Maximum value for queuing delay across all user input waiting to be picked-up by any process in the session during a target time interval2093Counters for classes in the System.Net namespace.2095The cumulative total number of socket connections established for this process since the process was started.2097The cumulative total number of bytes received over all open socket connections since the process was started. This number includes data and any protocol information that is not defined by the TCP/IP protocol.2099The cumulative total number of bytes sent over all open socket connections since the process was started. This number includes data and any protocol information that is not defined by the TCP/IP protocol.2101The cumulative total number of datagram packets received since the process was started.2103The cumulative total number of datagram packets sent since the process was started.2105The number of HttpWebRequest objects created during the last sample interval (typically 1 sec).2107The average lifetime of all web requests completed during the last sample interval. The lifetime is defined as the time between the creation of the HttpWebRequest object and the closing of either the HttpWebResponse object or the response stream object. Values are shown in milliseconds.2109HttpWebRequests Average Lifetime Base2111The number of HttpWebRequest objects added to a waiting queue during the last sample interval (typically 1 sec). A request is added to a waiting queue if all connections to the server are already in use when the request is submitted.2113The average time HttpWebRequest objects spent in a waiting queue. A request is added to a waiting queue if all connections to the server are already in use when the request is submitted, and remains there until a connection becomes available. Values are shown in milliseconds.2115HttpWebRequests Average Queue Time Base2117The number of HttpWebRequest objects aborted during the last sample interval (typically 1 sec). Typically requests are aborted either by calling HttpWebRequest.Abort() or if the request times out.2119The number of HttpWebRequest objects failed during the last sample interval (typically 1 sec). A request is considered failed, if after starting the request processing one of the following methods throw an exception: HttpWebRequest.EndGetRequestStream(), HttpWebRequest.GetRequestStream(), HttpWebRequest.EndGetResponse(), HttpWebRequest.GetResponse()2121Database provides performance statistics for each process using the ESE high performance embedded database management system.2123Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.2125Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.2127Defragmentation Tasks Postponed is the count of background database defragmentation tasks that could not be registered for imminent execution, and have been persisted in a table for later execution. [Dev Only]2129Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]2131Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]2133Heap Allocs/sec is the number of memory allocations from the MP Heaps per second.  [Dev Only]2135Heap Frees/sec is the number of memory frees to the MP Heaps per second.  [Dev Only]2137Heap Allocations is the current number of memory allocations in the MP Heaps.  [Dev Only]2139Heap Bytes Allocated is the size of all memory allocations in the MP Heaps discounting heap managemnt overhead.  [Dev Only]2141Page Bytes Reserved is the size of all explicitly reserved virtual address space.  [Dev Only]2143Page Bytes Committed is the size of all explicitly committed virtual memory backing store (page file and physical memory).  [Dev Only]2145FCB Async Scan/sec is the number of cached schema records (FCBs) scanned during asynchronous schema record cleanup. These records are scanned to age out older schema definitions. [Dev Only]2147FCB Async Purge/sec is the number of cached schema records (FCBs) purged during asynchronous schema record cleanup. These records are purged to age out older schema definitions. [Dev Only]2149FCB Async Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]2151FCB Sync Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second.  [Dev Only]2153FCB Sync Purge Stalls/sec is the number of stalls encountered while waiting for exclusive ownership of cached schema records (FCBs) in order to synchronously purge them.  [Dev Only]2155FCB Allocations Wait For Version Cleanup/sec is the number FCB allocations that must first wait for version cleanup in an attempt to free used FCBs for re-use. [Dev Only]2157FCB Purge On Cursor Close/sec is the number of cached schema records (FCBs) being synchronously purged when the cursor is closed (instead of leaving the schema record cached) each second.  [Dev Only]2159FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache.  No file operations were required.  [Dev Only]2161No text2163FCB Cache Stalls/sec is the number of stalls encountered while waiting for exclusive ownership of cached schema records (FCBs) in order to update their reference count.  [Dev Only]2165FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache.  [Dev Only]2167FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache.  [Dev Only]2169FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated.  [Dev Only]2171FCB Cache Allocated/sec is the number of cached schema records (FCBs) currently allocated per second.  [Dev Only]2173FCB Cache Available is the number of cached schema records (FCBs) currently allocated but not in use.  These records will be used and/or purged as required.  [Dev Only]2175FCB Attached RCEs is the number of revision control entries (RCEs)  attached to cached schema records (FCBs) [Dev Only]2177Sessions In Use is the number of database sessions currently open for use by client threads.2179Sessions % Used is the percentage of database sessions currently open for use by client threads.2181No text2183Resource Manager FCB Allocated indicates the amount of memory in Bytes of allocated FCBs [Dev Only]2185Resource Manager FCB Allocated Used indicates the amount of memory in Bytes of allocated and used FCBs [Dev Only]2187Resource Manager FCB Quota indicates the maximum amount of memory in Bytes for FCBs [Dev Only]2189Resource Manager FUCB Allocated indicates the amount of memory in Bytes of allocated FUCBs [Dev Only]2191Resource Manager FUCB Allocated Used indicates the amount of memory in Bytes of allocated and used FUCBs [Dev Only]2193Resource Manager FUCB Quota indicates the maximum amount of memory in Bytes for FUCBs [Dev Only]2195Resource Manager TDB Allocated indicates the amount of memory in Bytes of allocated TDBs [Dev Only]2197Resource Manager TDB Allocated Used indicates the amount of memory in Bytes of allocated and used TDBs [Dev Only]2199Resource Manager TDB Quota indicates the maximum amount of memory in Bytes for TDBs [Dev Only]2201Resource Manager IDB Allocated indicates the amount of memory in Bytes of allocated IDBs [Dev Only]2203Resource Manager IDB Allocated Used indicates the amount of memory in Bytes of allocated and used IDBs [Dev Only]2205Resource Manager IDB Quota indicates the maximum amount of memory in Bytes for IDBs [Dev Only]2207Table Open Cache % Hit is the percentage of database tables opened using cached schema information.  If this percentage is too low, the table cache size may be too small.2209No text2211Table Open Cache Hits/sec is the number of database tables opened using cached schema information per second.  If this rate is too low, the table cache size may be too small.2213Table Open Cache Misses/sec is the number of database tables opened without using cached schema information per second.  If this rate is too high, the table cache size may be too small.2215Table Open Pages Read/sec is the number of database pages read without using cached schema information per second.  If this rate is too high, the table cache size may be too small. [Dev Only]2217Table Open Pages Preread/sec is the number of database pages pre-read without using cached schema information per second.  If this rate is too high, the table cache size may be too small. [Dev Only]2219Table Opens/sec is the number of database tables opened per second.2221Table Closes/sec is the number of database tables closed per second.2223Tables Open is the number of database tables opened.2225Log Bytes Write per second is the rate bytes are written to the log.2227Log Bytes Generated per second is the rate at which data is added to the log.  This is different from Log Bytes Write per second in that each byte is generated only once whereas each byte may be written many times.2229Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs.  [Dev Only]2231Log Buffer Bytes Free is the amount of free space available in the log buffers.  [Dev Only]2233Log Buffer Bytes Committed is total number of committedbytes of log buffer.  [Dev Only]2235Log Threads Waiting is the number of threads waiting for their data to be written to the log in order to complete an update of the database.  If this number is too high, the log may be a bottleneck.2237Log Checkpoint Depth represents the amount of work, in bytes, that will need to be redone or undone to the database file(s) if the process crashes.  [Dev Only]2239Log Generation Checkpoint Depth represents the amount of work, in count of log files, that will need to be redone or undone to the database file(s) if the process crashes.  [Dev Only]2241Log Checkpoint Maintenance Outstanding IO Max represents how aggressive, in terms of outstanding IOs, the database engine will be to maintain the preferred checkpoint. This is a function of how far the checkpoint has fallen behind. [Dev Only]2243User Read Only Transaction Commits to Level 0/sec is the count of fully committed transactions started by the calling process that do not modify any data stored in the database engine.  [Dev Only]2245User Read/Write Transaction Commits to Level 0 (Durable)/sec is the count of fully committed transactions started by the calling process that modify data stored in the database engine.  [Dev Only]2247User Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of transactions started by the calling process and committed to log buffer.  [Dev Only]2249User Wait All Transaction Commits/sec is the count of signals to flush all pending transactions started by the calling process that modify data stored in the database engine.  [Dev Only]2251User Wait Last Transaction Commits/sec is the count of signals to flush a specific sessions pending transactions.  [Dev Only]2253User Transaction Commits to Level 0/sec is the count of fully committed transactions started by the calling process that access data stored in the database engine.  [Dev Only]2255User Read Only Transaction Rollbacks to Level 0/sec is the count of aborted transactions started by the calling process that do not modify any data stored in the database engine.  [Dev Only]2257User Read/Write Transaction Rollbacks to Level 0/sec is the count of aborted transactions started by the calling process that modify data stored in the database engine.  [Dev Only]2259User Transaction Rollbacks to Level 0/sec is the count of aborted transactions started by the calling process that access data stored in the database engine.  [Dev Only]2261System Read Only Transaction Commits to Level 0/sec is the count of fully committed transactions started internally that do not modify any data stored in the database engine.  [Dev Only]2263System Read/Write Transaction Commits to Level 0 (Durable)/sec is the count of fully committed transactions started internally that modify data stored in the database engine.  [Dev Only]2265System Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of internal transactions committed to log buffer.  [Dev Only]2267System Transaction Commits to Level 0/sec is the count of fully committed transactions started internally that access data stored in the database engine.  [Dev Only]2269System Read Only Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that do not modify any data stored in the database engine.  [Dev Only]2271System Read/Write Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that modify data stored in the database engine.  [Dev Only]2273System Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that access data stored in the database engine.  [Dev Only]2275Recovery Stalls for Read-only Transactions/sec is the number of times per second recovery had to pause to allow an older read-only transaction to complete.  [Dev Only]2277Recovery Long Stalls for Read-only Transactions/sec is the number of times per second recovery had to pause for an extended time to allow an older read-only transaction to complete.  [Dev Only]2279Recovery Stalls for Read-only Transactions (ms)/sec is the amount of time (in milliseconds per second) recovery had to pause to allow an older read-only transaction to complete.  [Dev Only]2281Recovery Throttles For IO Smoothing/sec is the number of times per second recovery had to pause to not recover a file faster than it was generated.  [Dev Only]2283Recovery Throttles For IO Smoothing Time (ms)/sec is the amount of time (in milliseconds per second) recovery had to pause to not recover a file faster than it was generated.  [Dev Only]2285Database Page Allocation File Extension Stalls/sec is the rate of attempts to extend the database file that stall.  [Dev Only]2287Log Records/sec is the count of records written to the database log buffers per second.  [Dev Only]2289Log Buffer Capacity Writes/sec is the count of times the database log buffers must be written per second because they are full.  [Dev Only]2291Log Buffer Commit Writes/sec is the count of times the database log buffers must be written per second because a transaction is fully committing its changes.  [Dev Only]2293Log Buffer Writes Skipped/sec is the count of times the database log buffers were intended to be written, but we skipped it due to the  desired log data already having been written.  [Dev Only]2295Log Buffer Writes Blocked/sec is the count of times the database log buffers were intended to be written, but we skipped it due to the  log buffer being locked for and being written by another thread.  [Dev Only]2297Log Writes/sec is the number of times the log buffers are written to the log file(s) per second.  If this number approaches the maximum write rate for the media holding the log file(s), the log may be a bottleneck.2299Log Full Segment Writes/sec is the number of times full log segments are written to the log file(s) per second. [Dev Only]2301Log Partial Segment Writes/sec is the number of times that a log segment that is only partially full of data is written to the log file(s) per second. [Dev Only]2303Log Bytes Wasted/sec is the number of bytes wasted by not reusing a partially written sector (and instead fill it up with NOPs).  [Dev Only]2305Log Record Stalls/sec is the number of log records that cannot be added to the log buffers per second because they are full.  If this counter is non-zero most of the time, the log buffer size may be a bottleneck.2307Version Buckets Allocated is the total number of version buckets allocated.2309Total number of version buckets allocated for FlagDelete RCEs  [Dev Only]2311VER Bucket Allocations Wait For Version Cleanup/sec is the number of version bucket allocations that must first wait for version cleanup in an attempt to free used version buckets  for re-use. [Dev Only]2313Average length of bookmark in RCE  [Dev Only]2315Number of times per second we look in the version store for a node whose version bit is set but which has no versions  [Dev Only]2317Number of times per second a version store clean task is dispatched asynchronously to be performed  [Dev Only]2319Number of times per second a version store clean task is performed synchronously  [Dev Only]2321Number of times per second a version store clean task was discarded due to load concerns  [Dev Only]2323Number of times per second a dispatched version store cleanup task fails  [Dev Only]2325Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]2327Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]2329Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]2331Record Unnecessary Replaces/sec is the rate at which updates to records in database tables are being discarded because the update did not actually modify the contents of the record.  [Dev Only]2333Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]2335Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]2337Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]2339False Index Column Updates/sec is the number of times per second an attempt was made to update an index because an update to at least one of the indexed columns was detected, only to discover that none of the indexed columns had actually changed (and therefore no index update was actually required).  [Dev Only]2341False Tuple Index Column Updates/sec is the number of times per second an attempt was made to update a tuple index because an update to the tuple-indexed column was detected, only to discover that the column had not actually changed (and therefore no index update was actually required).  [Dev Only]2343Record Intrinsic Long-Values Updated/sec is the rate at which intrinsic long-values are added to or replaced in records of database tables.  [Dev Only]2345Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]2347Record Separated Long-Values Forced/sec is the rate at which separated long-values are added to records of a database table because they could not be accommodated in the record itself.  [Dev Only]2349Record Separated Long-Values All Forced/sec is the rate at which all intrinsic long-values are separated out of a record of a database table in order to accommodate updates to the record.  [Dev Only]2351Record Separated Long-Values Reference All/sec is the rate at which a reference is added for all the separated long-values associated with a record of a database table.  [Dev Only]2353Record Separated Long-Values Dereference All/sec is the rate at which a reference is removed for all the separated long-values associated with a record of a database table.  [Dev Only]2355Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]2357Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]2359Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]2361Long-Value Maximum LID is the largest LID that has been used by the database engine.  [Dev Only]2363Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]2365Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]2367Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]2369Separated Long-Value Chunk Seeks/sec is the rate at which seeks for a particular chunk of a separated long-value in a database table are performed.  [Dev Only]2371Separated Long-Value Chunk Retrieves/sec is the rate at which retrievals of a chunk of a separated long-value in a database table are performed.  [Dev Only]2373Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]2375Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]2377Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]2379Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]2381B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]2383B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]2385B+ Tree Right Hotpoint Splits/sec is the count of times a page is split right in a database B+ Tree, but which is treated as an append at a local "hotpoint" in the B+ Tree per second.  [Dev Only]2387B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]2389B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]2391B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]2393Right Merges/sec is the count of pages removed from a database B+ Tree per second by moving all its records to the next page to the right.  [Dev Only]2395B+ Tree Partial Merges/sec is the count of pages where some of its records are moved to a page on the right in a database B+ Tree per second.  [Dev Only]2397B+ Tree Left Merges/sec is the count of pages removed from a database B+ Tree per second by moving all its records to the previous page to the left.  [Dev Only]2399B+ Tree Partial Left Merges/sec is the count of pages where some of its records are moved to a page on the left in a database B+ Tree per second.  [Dev Only]2401B+ Tree Page Moves/sec is the count of B+ Tree pages per second where all the records are moved to a new page. [Dev Only]2403B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]2405B+ Tree Failed Simple Page Cleanup Attempts/sec is the rate that attempts to reclaim deleted node space on a page are unsuccessful due to a conflict when attempting to write-latch the page. The cleanup is re-tried by locking the root of the B+ Tree.  [Dev Only]2407B+ Tree Seek Short Circuits/sec is the count of repeated seeks to the same record in a database B+ Tree that are saved by jumping directly to the cached physical location of that record per second.  [Dev Only]2409B+ Tree Opportune Prereads/sec is the number of pages per second that are preread because they are adjacent to a page read by a seek.  [Dev Only]2411B+ Tree Unnecessary Sibling Latches/sec is the count of sibling pages latched during a database B+ Tree Delete in the hopes of performing a merge where a merge is not possible, making that latch unnecessary.  [Dev Only]2413B+ Tree Move Nexts/sec is the count of times the database engine moves to the next record in a B+ Tree per second.  [Dev Only]2415B+ Tree Move Nexts (Non-Visible Nodes Skipped)/sec is the count of times the database engine skips non-visible records while attempting to move to the next visible record in a B+ Tree per second.  [Dev Only]2417B+ Tree Move Nexts (Nodes Filtered)/sec is the count of times the database engine filters records while attempting to move to the next record in a B+ Tree per second.  [Dev Only]2419B+ Tree Move Prevs/sec is the count of times the database engine moves to the previous record in a B+ Tree per second.  [Dev Only]2421B+ Tree Move Prevs (Non-Visible Nodes Skipped)/sec is the count of times the database engine skips non-visible records while attempting to move to the previous visible record in a B+ Tree per second.  [Dev Only]2423B+ Tree Move Prevs (Nodes Filtered)/sec is the count of times the database engine filters records while attempting to move to the previous record in a B+ Tree per second.  [Dev Only]2425B+ Tree Seeks/sec is the count of times a record is seeked to by a key in a database B+ Tree per second.  [Dev Only]2427B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]2429B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]2431B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]2433B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]2435B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]2437Pages Trimmed/sec is the number of database pages that are trimmed and the allocated space is released to the file system.  [Dev Only]2439Pages Not Trimmed Unaligned/sec is the number of database pages that are not trimmed because the trim request was not on an aligned boundary that the operating system supports. For example, if the supported trim granulariy is 64k, and the requested trim range is from (64k-1 page) to (128k+1 page), then this counter is increased by two. [Dev Only]2441Database Cache Misses per second is the rate at which database file page requests were fulfilled by the database cache by causing a file operation.  If this rate is high then the database cache size may be too small.2443Database Cache % Hit is the percentage of database file page requests that were fulfilled by the database cache without causing a file operation.  If this percentage is too low, the database cache size may be too small.2445No text2447Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.2449No text2451Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.2453Database Cache Requests/sec is the rate that pages are requested from the database cache.2455Database Cache % Pinned is the percentage of the database cache that pinned in the memory.  [Dev Only]2457No text2459Database Cache % Clean is the percentage of the database cache that does not contain modified data.  [Dev Only]2461No text2463Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]2465Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]2467Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]2469Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]2471Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]2473Database Opportune Write Issued (Total) is the count of IO operationshas been issued for opportune write. [Dev Only]2475Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]2477Database Pages Non-Resident Trimmed by OS/sec is the number of databases pages trimmed or partially trimmed per second from the buffer cache.  [Dev Only]2479Database Pages Non-Resident Reclaimed (Soft Faulted)/sec is the number  of OS soft faults attempted and succeeded against database pages in the buffer cache. [Dev Only]2481Database Pages Non-Resident Reclaimed (Failed)/sec is the number of OS soft faults attempted and failed against database pages in the buffer cache. [Dev Only]2483Database Pages Non-Resident Re-read/sec is the number of pages that could not be reclaimed by soft fault, and must be redirected to the database file as a re-read of the page. [Dev Only]2485Database Pages Non-Resident Evicted (Normally)/sec is the number of pages that were paged / trimmed by the OS memory manager, and got evicted normally before being re-used or re-latched. [Dev Only]2487Database Pages Non-Resident Reclaimed (Hard Faulted)/sec is the number of (probably) hard fault operations per second. [Dev Only]2489Database Pages Non-Resident Hard Faulted In Latency (us)/sec is the length of time, in microseconds, spent in OS Memory Manager hard fault operations  per sec. [Dev Only]2491Database Page Latches/sec is the rate that database pages are latched for access to their data.  [Dev Only]2493Database Page Fast Latches/sec is the rate that database pages are latched for access to their data using a hint to tell the cache manager where that page might be in memory.  [Dev Only]2495Database Page Bad Latch Hints/sec is the rate that incorrect hints to the location of a given page in the cache are given to the cache manager.  These hints are used to perform fast latches.  [Dev Only]2497Database Cache % Fast Latch is the percentage of database pages latched for access to their data using a hint to tell the cache manager where that page might be in memory.  Ideally, this percentage should match Database Cache % Hit.  [Dev Only]2499No text2501Database Pages Colded (Ext) per second is the rate at which database pages are deprioritized by sub-components other than the buffer manager to send  for early eviction.  [Dev Only]2503Database Pages Colded (Int) per second is the rate at which database pages are deprioritized by the buffer manager itself to maintain minimal  cache usage.  [Dev Only]2505Database Page Latch Conflicts/sec is the rate that users latching a database page for access to its data fail due to a conflicting latch owned on that same page by another user.  [Dev Only]2507Database Page Latch Stalls/sec is the rate that users latching a database page for access to its data must wait for another user to release a latch on that same page.  [Dev Only]2509Database Cache % Available is the percentage of the database cache that can be allocated to cache database pages that are newly created or read in from the database file(s).  [Dev Only]2511No text2513Database Page Faults/sec is the rate that database file page requests require the database cache manager to allocate a new page from the database cache.2515Database Page Evictions/sec is the rate that database file page requests, which require the database cache manager to allocate a new page from the database cache, force another database page out of the cache.  The eviction count is charged when the page is allocated and not when the previous owner of that page was actually evicted from the cache.  If this rate is too high, the database cache size may be too small.2517Database Page Evictions (Preread Untouched)/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache that were subsequently thrown out without being used. This is non-ideal behavior that represents a waste of I/O bandwidth and processing time.  [Dev Only]2519Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]2521Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]2523Database Page Evictions (Scavenging.AvailPool)/sec is the rate at which cached pages are evicted during scavenging to replenish the pool of available buffers.  [Dev Only]2525Database Page Evictions (Scavenging.SuperCold.Int)/sec is the rate at which internally deprioritized cached pages (such as older version pages) are evicted  during scavenging.  [Dev Only]2527Database Page Evictions (Scavenging.SuperCold.Ext)/sec is the rate at which  externally deprioritized cached pages (such as those scaned by DB maintenance)  are evicted during scavenging.  [Dev Only]2529Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]2531Database Page Evictions (Other)/sec is the rate that cached pages are evicted due to do-time page patching or purging a cached context / database or individual pages at runtime.  [Dev Only]2533Database Page Fault Stalls/sec is the rate of page faults that cannot be serviced because there are no pages available for allocation from the database cache.  If this counter is nonzero most of the time, the clean threshold may be too low.2535Database Cache Size (MB) is the amount of system memory, in megabytes, used by the database cache manager to hold commonly used information from the database file(s) to prevent file operations. If the database cache size seems to be too small for optimal performance, and there is very little available memory on the system (see Memory/Available Bytes), an increase of memory in the system may increase performance. If there is a large amount of available memory on the system, and the database cache size is not growing beyond a certain point, the database cache size may be capped at an artificially low limit. An increase in this limit may increase performance.2537Database Cache Size is the amount of system memory used by the database cache manager to hold commonly used information from the database file(s) to prevent file operations. If the database cache size seems to be too small for optimal performance and there is very little available memory on the system (see Memory/Available Bytes), adding more memory to the system may increase performance. If there is lots of available memory on the system and the database cache size is not growing beyond a certain point, the database cache size may be capped at an artificially low limit. Increasing this limit may increase performance.2539Database Cache Size Effective (MB) is the amount of system memory, in megabytes, that, hypothetically, would be used by the database cache manager if all used dehydrated/compressed database cache buffers were rehydrated/uncompressed.2541Database Cache Size Effective is the amount of system memory that, hypothetically, would be used by the database cache manager if all used dehydrated/compressed database cache buffers were rehydrated/uncompressed.2543Database Cache Memory Committed (MB) is the amount of memory (in megabytes) committed and ready to use or already in use by the database cache manager. If view-cache is enabled, this counter reflects the expected amount of Windows file cache memory consumed by this application to host database data.2545Database Cache Memory Committed is the amount of memory  committed and ready to use or already in use by the database cache manager. If view-cache is enabled, this counter reflects the expected amount of Windows file cache memory consumed by this application to host database data.2547Database Cache Memory Reserved (MB) is the amount of memory (in megabytes) reserved for use by the database cache manager. If view-cache is enabled, this counter is zero because the Windows file cache is used to host database data.2549Database Cache Memory Reserved is the amount of memory reserved for use by the database cache manager. If view-cache is enabled, this counter is zero because the Windows file cache is used to host database data.2551Database Cache Size Target (MB) is the amount of system memory (in MegaBytes) that the database cache manager considers to be ideal to use, given the configuration parameters provided by the application and the overall memory usage of the system. [Dev Only]2553Database Cache Size Target is the amount of system memory that the database cache manager considers to be ideal to use, given the configuration parameters provided by the application and the overall memory usage of the system. [Dev Only]2555Database Cache Size Min is the minimum amount of system memory configured for use by the database cache manager to hold commonly used information from the database file(s) to prevent file operations.  [Dev Only]2557Database Cache Size Max is the maximum amount of system memory configured for use by the database cache manager to hold commonly used information from the database file(s) to prevent file operations.  [Dev Only]2559Database Cache Size Resident is the amount of system memory used by the database cache that is currently part of the working set of the process.  If Database Cache Size Resident is ever significantly smaller than Database Cache Size then the operating system has chosen to reclaim that system memory for use in other parts of the system.  The database cache will recover from this event but if this is a common occurrence then it can lead to significant performance problems.2561Database Cache Size Resident (MB) is the amount of system memory (in megabytes) used by the database cache that is currently part of the working set of the process.  If Database Cache Size Resident (MB) is ever significantly smaller than Database Cache Size (MB) then the operating system has chosen to reclaim that system memory for use in other parts of the system.  The database cache will recover from this event but if this is a common occurrence then it can lead to significant performance problems.2563Database Cache Size Unattached (MB) is the amount of system memory (in MegaBytes) that the database cache manager is holding in case the database gets  re-attached and the cache becomes useful again. [Dev Only]2565Database Cache Sizing Duration is the time elapsed, in seconds, since a currently outstanding cache sizing operation started. This counter displays zero if cache sizing is not running. [Dev Only]2567Database Cache % Available Min is the minimum percentage of the database cache that is kept to be allocated to cache database pages that are newly created or read in from the database file(s).  If the percentage of available pages drops below this minimum, pages are thrown out of the database cache until the maximum percentage of available pages is reached.  This percentage should be set as low as possible without causing the actual percentage to drop to zero, causing cache fault stalls.  [Dev Only]2569No text2571Database Cache % Available Max is the maximum percentage of the database cache that is kept to be allocated to cache database pages that are newly created or read in from the database file(s).  This percentage should be set as low as possible but far enough above the minimum percentage so that efficient production of availible pages is possible.  [Dev Only]2573No text2575Database Pages Preread/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache.  [Dev Only]2577Database Page Preread Stalls/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache but did not complete preread before intended use.  [Dev Only]2579Database Pages Preread (Unnecessary)/sec is the rate that pages are  requested in anticipation of future use but that are already cached by the database cache.  [Dev Only]2581Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]2583Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]2585Database Pages Versioned/sec is the rate at which pages in the database cache are being copied into new pages in the cache for the purpose of being asynchronously written while the current version of that page in the database file is still being modified.  This feature is primarily used to avoid cycles, branches, or long chains of flush order dependencies without requiring the pages involved to be synchronously written to disk.  [Dev Only]2587Database Pages Version Copied/sec is the rate at which pages in the database cache are being copied into new pages in the cache for the purpose of being asynchronously written while the current version of that page in the database file is still being modified.  This feature is primarily used to avoid cycles, branches, or long chains of flush order dependencies without requiring the pages involved to be synchronously written to disk.  [Dev Only]2589Database Cache % Versioned is the percentage of the database cache that contains older versions of currently cached pages that have not yet been written to disk and thrown out of the cache.  [Dev Only]2591No text2593Database Pages Repeatedly Written/sec is the rate that pages are written to the database file(s) from the database cache more than once in their lifetime in the cache.  These page writes represent extra writes above the theoretical minimum and can therefore be considered overhead.  [Dev Only]2595Database Pages Flushed (Scavenging.Shrink)/sec is the rate that pages are written to the database file(s) from the database cache during scavenging because the cache size  must shrink.  [Dev Only]2597Database Pages Flushed (Checkpoint)/sec is the rate that pages are written to the database file(s) from the database cache to keep the checkpoint depth down to configured levels.  [Dev Only]2599Database Pages Flushed (Checkpoint Foreground)/sec is the rate that pages are written to the database file(s) from the database cache to keep the checkpoint depth down to configured levels.  [Dev Only]2601Database Pages Flushed (Context Flush)/sec is the rate that pages are written to the database file(s) from the database cache due to a requested flush of a buffer context.  [Dev Only]2603Database Pages Flushed (Filthy Foreground)/sec is the rate that pages are written to the database file(s) from the database cache because they are marked for filthy / immediate flush.  [Dev Only]2605Database Pages Flushed (Scavenging.AvailPool)/sec is the rate at which pages are written to the database file(s) from the database cache during scavenging to replenish the pool of available buffers.  [Dev Only]2607Database Pages Flushed (Scavenging.SuperCold.Int)/sec is the rate at which  internally deprioritized cached pages (such as older version pages) are  written to the database file(s) from the database cache during to scavenging.  [Dev Only]2609Database Pages Flushed (Scavenging.SuperCold.Ext)/sec is the rate at which  externally deprioritized cached pages (such as those scaned by DB maintenance)  are written to the database file(s) from the database cache during to scavenging.  [Dev Only]2611Database Pages Flushed Opportunely/sec is the rate that pages are written to the database file(s) from the database cache because they happen to be near other pages that must be written.  These additional writes are performed before they must happen in the hope that the total number of IOs required to write all the pages is reduced.  [Dev Only]2613Database Pages Flushed Opportunely Clean/sec is the rate that clean pages are opportunely written to the database file(s) from the database  cache because they happen to be betweeen two other pages that must  be written.  These additional writes are performed in the hope that the total number of IOs required to write all the dirty pages is reduced.  [Dev Only]2615Database Pages Coalesced Written/sec is the rate that pages are written to the database file(s) from the database cache coalesced with another page. [Dev Only]2617Database Pages Coalesced Read/sec is the rate that pages are read from the database file(s) to the database cache coalesced with another page. [Dev Only]2619Provides an estimate of the database cache lifetime, based on the most recently evicted resource.  A database page which is currently entering the cache should expect to remain in the cache for approximately this amount of time (in seconds) if not requested multiple times afterwards (i.e., if it doesn't become "hot").  [Dev Only]2621Provides an estimate of the database cache lifetime, based on the most recently evicted resource, though not considering resources which are out of order in our eviction queue.  A database page which is currently entering the cache should expect to remain in the cache for approximately this amount of time (in seconds) if not requested multiple times afterwards (i.e., if it doesn't become "hot").  [Dev Only]2623Provides an estimate of the database cache lifetime, based on the oldest most recently scanned resource.  A database page which is currently entering the cache should expect to remain in the cache for approximately this amount of time (in seconds) if not requested multiple times afterwards (i.e., if it doesn't become "hot").  [Dev Only]2625Provides the delta (in ms) of "Database Cache Lifetime" and "Database Cache Lifetime (smooth)".  [Dev Only]2627Provides the database cache lifetime (in seconds) of the most recently evicted resource that was cached and subsequently used only a single time.  It can also be viewed as the expected cache lifetime of singly-touched resources.  [Dev Only]2629Provides the database cache lifetime (in seconds) of the most recently evicted resource that was cached and subsequently used twice or more.  It can also be viewed as the expected cache lifetime of doubly-touched resources.  Note that this counter also captures the lifetime of resources that were touched more than twice, in which case the true lifetime reported is below the actual lifetime of such resources.  [Dev Only]2631Database Cache Scan Pages Evaluated/sec is the rate at which database pages are considered for eviction from the database page cache.  [Dev Only]2633Database Cache Scan Pages Moved/sec is the rate at which database pages are evaluated for returning from the database eviction data structure but instead re-indexed.  [Dev Only]2635Database Cache Scan Page Evaluated Out-of-order/sec is the rate at which database pages are considered for eviction from the database page cache in a priority counter to the page replacement algorithm.  [Dev Only]2637No text2639Provides the number of entries returned by LRU-k.  [Dev Only]2641Provides the number of buckets required to evaluate by LRU-k to do the  last scan.  [Dev Only]2643Provides the number of buckets that were empty to evaluate LRU-k during the last scan.  [Dev Only]2645Provides the raw ID range from the approximate index covered during last scan.  [Dev Only]2647Provides the scan range in seconds evaluated from the LRU-k.  [Dev Only]2649Provides the delta (in ms) between the first found resource during scavenge scan and the last evicted resource.  [Dev Only]2651Provides the number of currently super colded resources.  It is not hundred percent accurate.  [Dev Only]2653Provides the rate at which the engine is attempting to mark pages super  cold, for immediate eviction.  [Dev Only]2655Provides the rate at which the engine has successfully marked pages super  cold, for immediate eviction.  [Dev Only]2657Database Page History Records is the current number of database page access history records retained for supporting the LRU-K page replacment algorithm.  [Dev Only]2659Database Page History % Hit is the percentage of database page access history record lookups that were successful.  [Dev Only]2661No text2663Database Cache % Resident is the percentage of the database cache that are currently in the process's working set.  [Dev Only]2665No text2667Database Cache % Dehydrated is the percentage of pages in the database  cache that are currently compressed.2669No text2671Database Pages Repeatedly Read/sec is the rate that pages are read from the database file(s) into the database cache more than once a short period of time / within history tracking.  [Dev Only]2673Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups.  [Dev Only]2675Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]2677Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation.  [Dev Only]2679Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]2681Pages Freed/sec is the number of pages per second that are freed from the database by the online defragmentation process [Dev Only]2683Data Moves/sec is the number of times per second that data is moved from one page to another by the online defragmentation process [Dev Only]2685Online Defrag Pages Moved/sec is the number of times per second that data is moved from one page to a new page by the online defragmentation process [Dev Only]2687Online Defrag Log Bytes/sec is the rate at which online defragmentation is generating log bytes.  [Dev Only]2689Database Maintenance Duration is the number of hours that have passed since maintenance last completed for this database.2691Database Maintenance Pages Read is the number of pages read by database maintenance. [Dev Only]2693Database Maintenance Pages Read/sec is the rate at which pages are read by database maintenance. [Dev Only]2695Database Maintenance Pages Zeroed is the number of pages zeroed/scrubbed by database maintenance. [Dev Only]2697Database Maintenance Pages Zeroed/sec is the rate at which pages are zeroed/scrubbed by database maintenance. [Dev Only]2699Database Maintenance Zero Ref Count LVs is the number of zero ref counted LVs deleted by database maintenance. [Dev Only]2701Database Maintenance Pages with Flag Deleted LVs Reclaimed  is the number of LV pages with flag deleted LVs reclaimed  by database maintenance. [Dev Only]2703Database Maintenance IO Reads/sec is the approximate number of Database Maintenance read IO operations generated/sec. [Dev Only]2705Database Maintenance IO Reads Average Bytes is the approximate average size in bytes of Database Maintenance read IO. [Dev Only]2707No text2709Database Maintenance IO Re-Reads/sec is the approximate number of Database Maintenance read IO operations for pages already cached in the buffer manager generated/sec. [Dev Only]2711Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]2713Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]2715Database Tasks Pages Preread/sec is the rate at which database pages are read in anticipation of future use by background database tasks.  [Dev Only]2717Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]2719Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications.  [Dev Only]2721Database Tasks Log Records/sec is the rate at which background database tasks are generating log records.  [Dev Only]2723Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks.  [Dev Only]2725No text2727Database Tasks Log Bytes/sec is the rate at which background database tasks are generating log bytes.  [Dev Only]2729I/O Database Reads (Attached)/sec is the rate of database read operations completed.2731I/O Database Reads (Attached) Average Latency is the average length of time,  in milliseconds, per database read operation.2733No text2735I/O Database Reads (Attached) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]2737No text2739I/O Database Reads (Attached) In Heap is the number of database read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2741I/O Database Reads (Attached) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]2743I/O Database Reads (Recovery)/sec is the rate of database read operations completed.2745I/O Database Reads (Recovery) Average Latency is the average length of time,  in milliseconds, per database read operation.2747No text2749I/O Database Reads (Recovery) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]2751No text2753I/O Database Reads (Recovery) In Heap is the number of database read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2755I/O Database Reads (Recovery) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]2757I/O Database Reads/sec is the rate of database read operations completed.2759I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.2761No text2763I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]2765No text2767I/O Database Reads In Heap is the number of database read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2769I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]2771I/O Log Reads/sec is the rate of logfile read operations completed.2773I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation.2775No text2777I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation.  [Dev Only]2779No text2781I/O Log Reads In Heap is the number of logfile read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2783I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion.  [Dev Only]2785I/O Snapshot Reads/sec is the rate of snapshot read operations completed.  [Dev Only]2787I/O Snapshot Reads Average Latency is the average length of time, in milliseconds, per snapshot read operation.  [Dev Only]2789No text2791I/O Snapshot Reads Average Bytes is the average number of bytes transferred per snapshot read operation.  [Dev Only]2793No text2795I/O Snapshot Reads In Heap is the number of snapshot read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2797I/O Snapshot Reads Async Pending is the number of snapshot read operations asynchronously pending completion.  [Dev Only]2799I/O Database Writes (Attached)/sec is the rate of database write operations completed.2801I/O Database Writes (Attached) Average Latency is the average length of time,  in milliseconds, per database write operation.2803No text2805I/O Database Writes (Attached) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]2807No text2809I/O Database Writes (Attached) In Heap is the number of database write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2811I/O Database Writes (Attached) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]2813I/O Database Writes (Recovery)/sec is the rate of database write operations completed.2815I/O Database Writes (Recovery) Average Latency is the average length of time,  in milliseconds, per database write operation.2817No text2819I/O Database Writes (Recovery) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]2821No text2823I/O Database Writes (Recovery) In Heap is the number of database write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2825I/O Database Writes (Recovery) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]2827I/O Database Writes/sec is the rate of database write operations completed.2829I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.2831No text2833I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]2835No text2837I/O Database Writes In Heap is the number of database write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2839I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]2841I/O Flush Map Writes/sec is the rate of flush map write operations completed.2843I/O Flush Map Writes Average Latency is the average length of time,  in milliseconds, per flush map write operation.2845No text2847I/O Flush Map Writes Average Bytes is the average number of bytes transferred per flush map write operation.  [Dev Only]2849No text2851I/O Log Writes/sec is the rate of log file write operations completed.2853I/O Log Writes Average Latency is the average length of time, in milliseconds, per log file write operation.2855No text2857I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation.  [Dev Only]2859No text2861I/O Log Writes In Heap is the number of logfile write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2863I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion.  [Dev Only]2865I/O Snapshot Writes/sec is the rate of snapshot write operations completed.  [Dev Only]2867I/O Snapshot Writes Average Latency is the average length of time, in milliseconds, per snapshot write operation.  [Dev Only]2869No text2871I/O Snapshot Writes Average Bytes is the average number of bytes transferred per snapshot write operation.  [Dev Only]2873No text2875I/O Snapshot Writes In Heap is the number of snapshot write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]2877I/O Snapshot Writes Async Pending is the number of snapshot write operations asynchronously pending completion.  [Dev Only]2879FlushFileBuffers ops/sec is the rate of FlushFileBuffers operations completed.  [Dev Only]2881FlushFileBuffers Average Latency is the average length of time, in milliseconds, per FlushFileBuffers operation.  [Dev Only]2883No text2885Threads Blocked/sec is the rate at which the execution of threads are suspended to wait for a specific event to occur or for the acquisition of a resource currently owned by another thread. [Dev Only]2887Threads Blocked is the current number of threads whose execution has been suspended to wait for a specific event to occur or for the acquisition of a resource currently owned by another thread. [Dev Only]2889Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]2891Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]2893Encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]2895No text2897Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]2899Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]2901Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]2903No text2905Pages Reorganized (Other)/sec is the number of times per second a page was reorganized for some other / unknown reason.  [Dev Only]2907Pages Reorganized (Free Space Request)/sec is the number of times per second a page was reorganized due to a free space request that could not be satisfied by the existing contiguous space on the page.  [Dev Only]2909Pages Reorganized (Page Move Logging)/sec is the number of times per second a page was reorganized for minimizing a page size for logging page move.  [Dev Only]2911Pages Reorganized (Dehydrate Buffer)/sec is the number of times per second a page is reorganized to minimize our in-memory buffer usage.  [Dev Only]2913Program Marker is a generic marker that may be set by some clients to delimit program execution, usually for debugging or testing purposes. [Dev Only]2915Database Cache Miss (Attached) Average Latency is the average length of time, in milliseconds, per page cache miss that is satisfied by waiting for a database read operation to be completed.2917No text2919Database Cache Size Unused is the amount of system memory used by the database cache manager to hold information from the database file(s) that may be used in the near future but that hasn�t yet been referenced.  [Dev Only]2921Statistics for the ESE high performance embedded database management system by Table Class.2923Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]2925Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]2927Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]2929Record Unnecessary Replaces/sec is the rate at which updates to records in database tables are being discarded because the update did not actually modify the contents of the record.  [Dev Only]2931Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]2933Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]2935Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]2937False Index Column Updates/sec is the number of times per second an attempt was made to update an index because an update to at least one of the indexed columns was detected, only to discover that none of the indexed columns had actually changed (and therefore no index update was actually required).  [Dev Only]2939False Tuple Index Column Updates/sec is the number of times per second an attempt was made to update a tuple index because an update to the tuple-indexed column was detected, only to discover that the column had not actually changed (and therefore no index update was actually required).  [Dev Only]2941Record Intrinsic Long-Values Updated/sec is the rate at which intrinsic long-values are added to or replaced in records of database tables.  [Dev Only]2943Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]2945Record Separated Long-Values Forced/sec is the rate at which separated long-values are added to records of a database table because they could not be accommodated in the record itself.  [Dev Only]2947Record Separated Long-Values All Forced/sec is the rate at which all intrinsic long-values are separated out of a record of a database table in order to accommodate updates to the record.  [Dev Only]2949Record Separated Long-Values Reference All/sec is the rate at which a reference is added for all the separated long-values associated with a record of a database table.  [Dev Only]2951Record Separated Long-Values Dereference All/sec is the rate at which a reference is removed for all the separated long-values associated with a record of a database table.  [Dev Only]2953Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]2955Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]2957Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]2959Long-Value Maximum LID is the largest LID that has been used by the database engine for this table class.  [Dev Only]2961Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]2963Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]2965Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]2967Separated Long-Value Chunk Seeks/sec is the rate at which seeks for a particular chunk of a separated long-value in a database table are performed.  [Dev Only]2969Separated Long-Value Chunk Retrieves/sec is the rate at which retrievals of a chunk of a separated long-value in a database table are performed.  [Dev Only]2971Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]2973Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]2975Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]2977Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]2979B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]2981B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]2983B+ Tree Right Hotpoint Splits/sec is the count of times a page is split right in a database B+ Tree, but which is treated as an append at a local "hotpoint" in the B+ Tree per second.  [Dev Only]2985B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]2987B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]2989B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]2991Right Merges/sec is the count of pages removed from a database B+ Tree per second by moving all its records to the next page to the right.  [Dev Only]2993B+ Tree Partial Merges/sec is the count of pages where some of its records are moved to a page on the right in a database B+ Tree per second.  [Dev Only]2995B+ Tree Left Merges/sec is the count of pages removed from a database B+ Tree per second by moving all its records to the previous page to the left.  [Dev Only]2997B+ Tree Partial Left Merges/sec is the count of pages where some of its records are moved to a page on the left in a database B+ Tree per second.  [Dev Only]2999B+ Tree Page Moves/sec is the count of B+ Tree pages per second where all the records are moved to a new page. [Dev Only]3001B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]3003B+ Tree Failed Simple Page Cleanup Attempts/sec is the rate that attempts to reclaim deleted node space on a page are unsuccessful due to a conflict when attempting to write-latch the page. The cleanup is re-tried by locking the root of the B+ Tree.  [Dev Only]3005B+ Tree Seek Short Circuits/sec is the count of repeated seeks to the same record in a database B+ Tree that are saved by jumping directly to the cached physical location of that record per second.  [Dev Only]3007B+ Tree Opportune Prereads/sec is the number of pages per second that are preread because they are adjacent to a page read by a seek.  [Dev Only]3009B+ Tree Unnecessary Sibling Latches/sec is the count of sibling pages latched during a database B+ Tree Delete in the hopes of performing a merge where a merge is not possible, making that latch unnecessary.  [Dev Only]3011B+ Tree Move Nexts/sec is the count of times the database engine moves to the next record in a B+ Tree per second.  [Dev Only]3013B+ Tree Move Nexts (Non-Visible Nodes Skipped)/sec is the count of times the database engine skips non-visible records while attempting to move to the next visible record in a B+ Tree per second.  [Dev Only]3015B+ Tree Move Nexts (Nodes Filtered)/sec is the count of times the database engine filters records while attempting to move to the next record in a B+ Tree per second.  [Dev Only]3017B+ Tree Move Prevs/sec is the count of times the database engine moves to the previous record in a B+ Tree per second.  [Dev Only]3019B+ Tree Move Prevs (Non-Visible Nodes Skipped)/sec is the count of times the database engine skips non-visible records while attempting to move to the previous visible record in a B+ Tree per second.  [Dev Only]3021B+ Tree Move Prevs (Nodes Filtered)/sec is the count of times the database engine filters records while attempting to move to the previous record in a B+ Tree per second.  [Dev Only]3023B+ Tree Seeks/sec is the count of times a record is seeked to by a key in a database B+ Tree per second.  [Dev Only]3025B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]3027B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]3029B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]3031B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]3033B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]3035Database Pages Preread Untouched/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache that were subsequently thrown out without being used. This is non-ideal behavior that represents a waste of I/O bandwidth and processing time .  [Dev Only]3037Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]3039Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]3041Database Page Evictions (Scavenging.AvailPool)/sec is the rate at which cached pages are evicted during scavenging to replenish the pool of available buffers.  [Dev Only]3043Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]3045Database Page Evictions (Other)/sec is the rate that cached pages are evicted due to do-time page patching or purging a cached context / database or individual pages at runtime.  [Dev Only]3047Database Cache Size (MB) is the amount of system memory (in megabytes) used by the database cache manager to hold commonly used information from the database file(s) to prevent file operations.  If the database cache size seems to be too small for optimal performance and there is very little available memory on the system (see Memory/Available Bytes), adding more memory to the system may increase performance.  If there is a lot of available memory on the system and the database cache size is not growing beyond a certain point, the database cache size may be capped at an artificially low limit.  Increasing this limit may increase performance.3049Database Cache Size is the amount of system memory used by the database cache manager to hold commonly used information from the database file(s) to prevent file operations.  If the database cache size seems to be too small for optimal performance and there is very little available memory on the system (see Memory/Available Bytes), adding more memory to the system may increase performance.  If there is a lot of available memory on the system and the database cache size is not growing beyond a certain point, the database cache size may be capped at an artificially low limit.  Increasing this limit may increase performance.3051Database Cache Misses per second is the rate at which database file page requests were fulfilled by the database cache by causing a file operation.  If this rate is high, then the database cache size may be too small.3053Database Cache % Hit is the percentage of database file page requests that were fulfilled by the database cache without causing a file operation.  If this percentage is too low, the database cache size may be too small.3055No text3057Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.3059No text3061Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.3063Database Cache Requests/sec is the rate that pages are requested from the database cache.3065Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]3067Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]3069Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]3071Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]3073Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]3075Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]3077Database Pages Colded (Ext) per second is the rate at which database pages are deprioritized by sub-components other than the buffer manager to send  for early eviction.  [Dev Only]3079Database Pages Colded (Int) per second is the rate at which database pages are deprioritized by the buffer manager itself to maintain minimal  cache usage.  [Dev Only]3081Database Pages Preread/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache.  [Dev Only]3083Database Page Preread Stalls/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache but did not complete preread before intended use.  [Dev Only]3085Database Pages Preread (Unnecessary)/sec is the rate that pages are  requested in anticipation of future use but that are already cached by the database cache.  [Dev Only]3087Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]3089Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]3091Database Pages Versioned/sec is the rate at which pages in the database cache are being copied into new pages in the cache for the purpose of being asynchronously written while the current version of that page in the database file is still being modified.  This feature is primarily used to avoid cycles, branches, or long chains of flush order dependencies without requiring the pages involved to be synchronously written to disk.  [Dev Only]3093Database Pages Version Copied/sec is the rate at which pages in the database cache are being copied into new pages in the cache for the purpose of being asynchronously written while the current version of that page in the database file is still being modified.  This feature is primarily used to avoid cycles, branches, or long chains of flush order dependencies without requiring the pages involved to be synchronously written to disk.  [Dev Only]3095Database Pages Repeatedly Written/sec is the rate that pages are written to the database file(s) from the database cache more than once in their lifetime in the cache.  These page writes represent extra writes above the theoretical minimum and can therefore be considered overhead.  [Dev Only]3097Database Pages Flushed (Scavenging.Shrink)/sec is the rate that pages are written to the database file(s) from the database cache during scavenging because the cache size  must shrink.  [Dev Only]3099Database Pages Flushed (Checkpoint)/sec is the rate that pages are written to the database file(s) from the database cache to keep the checkpoint depth down to configured levels.  [Dev Only]3101Database Pages Flushed (Checkpoint Foreground)/sec is the rate that pages are written to the database file(s) from the database cache to keep the checkpoint depth down to configured levels.  [Dev Only]3103Database Pages Flushed (Context Flush)/sec is the rate that pages are written to the database file(s) from the database cache due to a requested flush of a buffer context.  [Dev Only]3105Database Pages Flushed (Filthy Foreground)/sec is the rate that pages are written to the database file(s) from the database cache because they are marked for filthy / immediate flush.  [Dev Only]3107Database Pages Flushed (Scavenging.AvailPool)/sec is the rate at which pages are written to the database file(s) from the database cache during scavenging to replenish the pool of available buffers.  [Dev Only]3109Database Pages Flushed Opportunely/sec is the rate that pages are written to the database file(s) from the database cache because they happen to be near other pages that must be written.  These additional writes are performed before they must happen in the hope that the total number of IOs required to write all the pages is reduced.  [Dev Only]3111Database Pages Flushed Opportunely Clean/sec is the rate that clean pages are opportunely written to the database file(s) from the database  cache because they happen to be betweeen two other pages that must  be written.  These additional writes are performed in the hope that the total number of IOs required to write all the dirty pages is reduced.  [Dev Only]3113Database Pages Coalesced Written/sec is the rate that pages are written to the database file(s) from the database cache coalesced with another page. [Dev Only]3115Database Pages Coalesced Read/sec is the rate that pages are read from the database file(s) to the database cache coalesced with another page. [Dev Only]3117Database Pages Repeatedly Read/sec is the rate that pages are read from the database file(s) into the database cache more than once a short period of time / within history tracking.  [Dev Only]3119FCB Async Scan/sec is the number of cached schema records (FCBs) scanned during asynchronous schema record cleanup. These records are scanned to age out older schema definitions. [Dev Only]3121FCB Async Purge/sec is the number of cached schema records (FCBs) purged during asynchronous schema record cleanup. These records are purged to age out older schema definitions. [Dev Only]3123FCB Async Threshold Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]3125Table Open Pages Read/sec is the number of database pages read without using cached schema information per second.  If this rate is too high, the table cache size may be too small. [Dev Only]3127Table Open Pages Preread/sec is the number of database pages pre-read without using cached schema information per second.  If this rate is too high, the table cache size may be too small. [Dev Only]3129Database Cache Miss (Attached) Average Latency is the average length of time, in milliseconds, per page cache miss that is satisfied by waiting for a database read operation to be completed.3131No text3133Database Cache Size Unused is the amount of system memory used by the database cache manager to hold information from the database file(s) that may be used in the near future but that hasn�t yet been referenced.  [Dev Only]3135Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]3137Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]3139Encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]3141No text3143Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]3145Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]3147Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]3149No text3151Instances in this process3153Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.3155Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.3157Defragmentation Tasks Postponed is the count of background database defragmentation tasks that could not be registered for imminent execution, and have been persisted in a table for later execution. [Dev Only]3159Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]3161Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]3163FCB Async Scan/sec is the number of cached schema records (FCBs) scanned during asynchronous schema record cleanup. These records are scanned to age out older schema definitions. [Dev Only]3165FCB Async Purge/sec is the number of cached schema records (FCBs) purged during asynchronous schema record cleanup. These records are purged to age out older schema definitions. [Dev Only]3167FCB Async Threshold Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]3169FCB Sync Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second.  [Dev Only]3171FCB Sync Purge Stalls/sec is the number of stalls encountered while waiting for exclusive ownership of cached schema records (FCBs) in order to synchronously purge them.  [Dev Only]3173FCB Allocations Wait For Version Cleanup/sec is the number of FCB allocations that must first wait for version cleanup in an attempt to free used FCBs for re-use. [Dev Only]3175FCB Purge On Cursor Close/sec is the number of cached schema records (FCBs) being synchronously purged when the cursor is closed (instead of leaving the schema record cached) each second.  [Dev Only]3177FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache.  No file operations were required.  [Dev Only]3179No text3181FCB Cache Stalls/sec is the number of stalls encountered while waiting for exclusive ownership of cached schema records (FCBs) in order to update their reference count.  [Dev Only]3183FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache.  [Dev Only]3185FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache.  [Dev Only]3187FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated.  [Dev Only]3189FCB Cache Allocated/sec is the number of cached schema records (FCBs) currently allocated per second.  [Dev Only]3191FCB Cache Available is the number of cached schema records (FCBs) currently allocated but not in use.  These records will be used and/or purged as required.  [Dev Only]3193FCB Cache Allocations Failed is the number of schema records (FCBs) attempts that fail to allocate. [Dev Only]3195FCB Cache Allocation Average Latency (ms) is the average latency in allocating cached schema records (FCBs).  [Dev Only]3197No text3199FCB Attached RCEs is the number of revision control entries (RCEs)  attached to cached schema records (FCBs) [Dev Only]3201Sessions In Use is the number of database sessions currently open for use by client threads.3203Sessions % Used is the percentage of database sessions currently open for use by client threads.3205No text3207Table Open Cache % Hit is the percentage of database tables opened using cached schema information.  If this percentage is too low, the table cache size may be too small.3209No text3211Table Open Cache Hits/sec is the number of database tables opened using cached schema information per second.  If this rate is too low, the table cache size may be too small.3213Table Open Cache Misses/sec is the number of database tables opened without using cached schema information per second.  If this rate is too high, the table cache size may be too small.3215Table Open Pages Read/sec is the number of database pages read without using cached schema information per second.  If this rate is too high, the table cache size may be too small. [Dev Only]3217Table Open Pages Preread/sec is the number of database pages pre-read without using cached schema information per second.  If this rate is too high, the table cache size may be too small. [Dev Only]3219Table Opens/sec is the number of database tables opened per second.3221Table Closes/sec is the number of database tables closed per second.3223Tables Open is the number of database tables opened.3225Log Bytes Write per second is the rate bytes are written to the log.3227Log Bytes Generated per second is the rate at which data is added to the log.  This is different from Log Bytes Write per second in that each byte is generated only once whereas each byte may be written many times.3229Log Buffer Size is the amount of memory, in bytes, allocated for the database log buffers.  [Dev Only]3231Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs.  [Dev Only]3233Log Buffer Bytes Free is the amount of free space available in the log buffers.  [Dev Only]3235Log Buffer Bytes Committed is total number of committedbytes of log buffer.  [Dev Only]3237Log Threads Waiting is the number of threads waiting for their data to be written to the log in order to complete an update of the database.  If this number is too high, the log may be a bottleneck.3239Log File Size is the size, in bytes, of the database log files.  [Dev Only]3241Log Checkpoint Depth represents the amount of work, in bytes, that will need to be redone or undone to the database file(s) if the process crashes.  [Dev Only]3243Log Generation Checkpoint Depth represents the amount of work, in count of log files, that will need to be redone or undone to the database file(s) if the process crashes.3245Log Generation Database Consistency Depth represents the amount of work, in count of log files, that will need to be redone or undone to the database file(s) if the process crashes and rebuilding the associated persisted flush map(s) is not required. [Dev Only]3247Log Checkpoint Maintenance Outstanding IO Max represents how aggressive, in terms of outstanding IOs, the database engine will be to maintain the preferred checkpoint. This is a function of how far the checkpoint has fallen behind. [Dev Only]3249Log Generation Checkpoint Depth Target represents the ideal target for the amount of work, in number of log files, that may be redone or undone to the database file(s) if the process crashes.3251Log Checkpoint Depth as a % of Target is an expression of the current checkpoint depth in terms of a percentage of the checkpoint depth target.  For example, if the current checkpoint depth is 5 generations and the checkpoint depth target is 4 generations then this will be reported as 125% of target.3253No text3255Log Generation Checkpoint Depth Max represents the maximum allowable amount of work, in number of log files, that may be redone or undone to the database file(s) if the process crashes.3257Log Generation Loss Resiliency Depth represents the amount of work, in number of log files, that may be lost while still allowing the database file(s) to recover (with data loss) if the process crashes.3259Log Files Generated represents the total number of log files generated by an instance since that instance was last initialized.3261Log Files Generated Prematurely represents the total number of log files generated by an instance since that instance was last initialized and that have not been entirely filled with useful data.  Under certain conditions the database engine will choose to switch to a new log file before it has been completely filled with useful data.3263Log File Current Generation gives the generation number of the current log file of an instance.3265User Read Only Transaction Commits to Level 0/sec is the count of fully committed transactions started by the calling process that do not modify any data stored in the database engine.  [Dev Only]3267User Read/Write Transaction Commits to Level 0 (Durable)/sec is the count of fully committed transactions started by the calling process that modify data stored in the database engine.  [Dev Only]3269User Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of transactions started by the calling process and committed to log buffer.  [Dev Only]3271User Wait All Transaction Commits/sec is the count of signals to flush all pending transactions started by the calling process that modify data stored in the database engine.  [Dev Only]3273User Wait Last Transaction Commits/sec is the count of signals to flush a specific sessions pending transactions.  [Dev Only]3275User Transaction Commits to Level 0/sec is the count of fully committed transactions started by the calling process that access data stored in the database engine.  [Dev Only]3277User Read Only Transaction Rollbacks to Level 0/sec is the count of aborted transactions started by the calling process that do not modify any data stored in the database engine.  [Dev Only]3279User Read/Write Transaction Rollbacks to Level 0/sec is the count of aborted transactions started by the calling process that modify data stored in the database engine.  [Dev Only]3281User Transaction Rollbacks to Level 0/sec is the count of aborted transactions started by the calling process that access data stored in the database engine.  [Dev Only]3283System Read Only Transaction Commits to Level 0/sec is the count of fully committed transactions started internally that do not modify any data stored in the database engine.  [Dev Only]3285System Read/Write Transaction Commits to Level 0 (Durable)/sec is the count of fully committed transactions started internally that modify data stored in the database engine.  [Dev Only]3287System Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of internal transactions committed to log buffer.  [Dev Only]3289System Transaction Commits to Level 0/sec is the count of fully committed transactions started internally that access data stored in the database engine.  [Dev Only]3291System Read Only Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that do not modify any data stored in the database engine.  [Dev Only]3293System Read/Write Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that modify data stored in the database engine.  [Dev Only]3295System Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that access data stored in the database engine.  [Dev Only]3297Recovery Stalls for Read-only Transactions/sec is the number of times per second recovery had to pause to allow an older read-only transaction to complete.  [Dev Only]3299Recovery Long Stalls for Read-only Transactions/sec is the number of times per second recovery had to pause for an extended time to allow an older read-only transaction to complete.  [Dev Only]3301Recovery Stalls for Read-only Transactions (ms)/sec is the amount of time (in milliseconds per second) recovery had to pause to allow an older read-only transaction to complete.  [Dev Only]3303Recovery Throttles For IO Smoothing/sec is the number of times per second recovery had to pause to not recover a file faster than it was generated.  [Dev Only]3305Recovery Throttles For IO Smoothing Time (ms)/sec is the amount of time (in milliseconds per second) recovery had to pause to not recover a file faster than it was generated.  [Dev Only]3307Database Page Allocation File Extension Stalls/sec is the rate of page allocations from a database file that must be serviced by extending the database file and which stall when doing so.  [Dev Only]3309Log Records/sec is the count of records written to the database log buffers per second.  [Dev Only]3311Log Buffer Capacity Writes/sec is the count of times the database log buffers must be written per second because they are full.  [Dev Only]3313Log Buffer Commit Writes/sec is the count of times the database log buffers must be written per second because a transaction is fully committing its changes.  [Dev Only]3315Log Buffer Writes Skipped/sec is the count of times the database log buffers were intended to be written, but we skipped it due to the  desired log data already having been written.  [Dev Only]3317Log Buffer Writes Blocked/sec is the count of times the database log buffers were intended to be written, but we skipped it due to the  log buffer being locked for and being written by another thread.  [Dev Only]3319Log Writes/sec is the number of times the log buffers are written to the log file(s) per second.  If this number approaches the maximum write rate for the media holding the log file(s), the log may be a bottleneck.3321Log Full Segment Writes/sec is the number of times full log segments are written to the log file(s) per second.  [Dev Only]3323Log Partial Segment Writes/sec is the number of times that a log segment that is only partially full of data is written to the log file(s) per second.  [Dev Only]3325Log Bytes Wasted/sec is the number of bytes wasted by not reusing a partially written sector (and instead fill it up with NOPs). [Dev Only]3327Log Record Stalls/sec is the number of log records that cannot be added to the log buffers per second because they are full.  If this counter is non-zero most of the time, the log buffer size may be a bottleneck.3329Total number of version buckets allocated3331Total number of version buckets allocated for FlagDelete RCEs  [Dev Only]3333VER Bucket Allocations Wait For Version Cleanup/sec is the number of version bucket allocations that must first wait for version cleanup in an attempt to free used version buckets  for re-use. [Dev Only]3335Average length of bookmark in RCE  [Dev Only]3337Number of times per second we look in the version store for a node whose version bit is set but which has no versions  [Dev Only]3339Number of times per second a version store clean task is dispatched asynchronously to be performed  [Dev Only]3341Number of times per second a version store clean task is performed synchronously  [Dev Only]3343Number of times per second a version store clean task was discarded due to load concerns  [Dev Only]3345Number of times per second a dispatched version store cleanup task fails  [Dev Only]3347Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]3349Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]3351Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]3353Record Unnecessary Replaces/sec is the rate at which updates to records in database tables are being discarded because the update did not actually modify the contents of the record.  [Dev Only]3355Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]3357Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]3359Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]3361False Index Column Updates/sec is the number of times per second an attempt was made to update an index because an update to at least one of the indexed columns was detected, only to discover that none of the indexed columns had actually changed (and therefore no index update was actually required).  [Dev Only]3363False Tuple Index Column Updates/sec is the number of times per second an attempt was made to update a tuple index because an update to the tuple-indexed column was detected, only to discover that the column had not actually changed (and therefore no index update was actually required).  [Dev Only]3365Record Intrinsic Long-Values Updated/sec is the rate at which intrinsic long-values are added to or replaced in records of database tables.  [Dev Only]3367Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]3369Record Separated Long-Values Forced/sec is the rate at which separated long-values are added to records of a database table because they could not be accommodated in the record itself.  [Dev Only]3371Record Separated Long-Values All Forced/sec is the rate at which all intrinsic long-values are separated out of a record of a database table in order to accommodate updates to the record.  [Dev Only]3373Record Separated Long-Values Reference All/sec is the rate at which a reference is added for all the separated long-values associated with a record of a database table.  [Dev Only]3375Record Separated Long-Values Dereference All/sec is the rate at which a reference is removed for all the separated long-values associated with a record of a database table.  [Dev Only]3377Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]3379Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]3381Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]3383Long-Value Maximum LID is the largest LID that has been used by the database engine for this instance.  [Dev Only]3385Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]3387Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]3389Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]3391Separated Long-Value Chunk Seeks/sec is the rate at which seeks for a particular chunk of a separated long-value in a database table are performed.  [Dev Only]3393Separated Long-Value Chunk Retrieves/sec is the rate at which retrievals of a chunk of a separated long-value in a database table are performed.  [Dev Only]3395Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]3397Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]3399Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]3401Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]3403B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]3405B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]3407B+ Tree Right Hotpoint Splits/sec is the count of times a page is split right in a database B+ Tree, but which is treated as an append at a local "hotpoint" in the B+ Tree per second.  [Dev Only]3409B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]3411B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]3413B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]3415Right Merges/sec is the count of pages removed from a database B+ Tree per second by moving all its records to the next page to the right.  [Dev Only]3417B+ Tree Partial Merges/sec is the count of pages where some of its records are moved to a page on the right in a database B+ Tree per second.  [Dev Only]3419B+ Tree Left Merges/sec is the count of pages removed from a database B+ Tree per second by moving all its records to the previous page to the left.  [Dev Only]3421B+ Tree Partial Left Merges/sec is the count of pages where some of its records are moved to a page on the left in a database B+ Tree per second.  [Dev Only]3423B+ Tree Page Moves/sec is the count of B+ Tree pages per second where all the records are moved to a new page. [Dev Only]3425B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]3427B+ Tree Failed Simple Page Cleanup Attempts/sec is the rate that attempts to reclaim deleted node space on a page are unsuccessful due to a conflict when attempting to write-latch the page. The cleanup is re-tried by locking the root of the B+ Tree.  [Dev Only]3429B+ Tree Seek Short Circuits/sec is the count of repeated seeks to the same record in a database B+ Tree that are saved by jumping directly to the cached physical location of that record per second.  [Dev Only]3431B+ Tree Opportune Prereads/sec is the number of pages per second that are preread because they are adjacent to a page read by a seek.  [Dev Only]3433B+ Tree Unnecessary Sibling Latches/sec is the count of sibling pages latched during a database B+ Tree Delete in the hopes of performing a merge where a merge is not possible, making that latch unnecessary.  [Dev Only]3435B+ Tree Move Nexts/sec is the count of times the database engine moves to the next record in a B+ Tree per second.  [Dev Only]3437B+ Tree Move Nexts (Non-Visible Nodes Skipped)/sec is the count of times the database engine skips non-visible records while attempting to move to the next visible record in a B+ Tree per second.  [Dev Only]3439B+ Tree Move Nexts (Nodes Filtered)/sec is the count of times the database engine filters records while attempting to move to the next record in a B+ Tree per second.  [Dev Only]3441B+ Tree Move Prevs/sec is the count of times the database engine moves to the previous record in a B+ Tree per second.  [Dev Only]3443B+ Tree Move Prevs (Non-Visible Nodes Skipped)/sec is the count of times the database engine skips non-visible records while attempting to move to the previous visible record in a B+ Tree per second.  [Dev Only]3445B+ Tree Move Prevs (Nodes Filtered)/sec is the count of times the database engine filters records while attempting to move to the previous record in a B+ Tree per second.  [Dev Only]3447B+ Tree Seeks/sec is the count of times a record is seeked to by a key in a database B+ Tree per second.  [Dev Only]3449B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]3451B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]3453B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]3455B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]3457B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]3459Pages Trimmed/sec is the number of database pages that are trimmed and the allocated space is released to the file system.  [Dev Only]3461Pages Not Trimmed Unaligned/sec is the number of database pages that are not trimmed because the trim request was not on an aligned boundary that the operating system supports. For example, if the supported trim granulariy is 64k, and the requested trim range is from (64k-1 page) to (128k+1 page), then this counter is increased by two. [Dev Only]3463Database Pages Preread Untouched/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache that were subsequently thrown out without being used. This is non-ideal behavior that represents a waste of I/O bandwidth and processing time.  [Dev Only]3465Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]3467Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]3469Database Page Evictions (Scavenging.AvailPool)/sec is the rate at which cached pages are evicted during scavenging to replenish the pool of available buffers.  [Dev Only]3471Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]3473Database Page Evictions (Other)/sec is the rate that cached pages are evicted due to do-time page patching or purging a cached context / database or individual pages at runtime.  [Dev Only]3475Database Cache Size (MB) is the amount of system memory (in megabytes) used by the database cache manager to hold commonly used information from the database file(s) to prevent file operations.  If the database cache size seems to be too small for optimal performance and there is very little available memory on the system (see Memory/Available Bytes), adding more memory to the system may increase performance.  If there is a lot of available memory on the system and the database cache size is not growing beyond a certain point, the database cache size may be capped at an artificially low limit.  Increasing this limit may increase performance.3477Database Cache Misses per second is the rate at which database file page requests were fulfilled by the database cache by causing a file operation.  If this rate is high, then the database cache size may be too small.3479Database Cache % Hit is the percentage of database file page requests that were fulfilled by the database cache without causing a file operation.  If this percentage is too low, the database cache size may be too small.3481No text3483Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.3485No text3487Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.3489Database Cache Requests/sec is the rate that pages are requested from the database cache.3491Instance Status indicates the current runtime state of the instance. Values are 1 (recovery redo), 2 (recovery undo), 3 (runtime),  4 (shutdown), 5 (error).  [Dev Only]3493Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]3495Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]3497Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]3499Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]3501Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]3503Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]3505Database Pages Colded (Ext) per second is the rate at which database pages are deprioritized by sub-components other than the buffer manager to send  for early eviction.  [Dev Only]3507Database Pages Colded (Int) per second is the rate at which database pages are deprioritized by the buffer manager itself to maintain minimal  cache usage.  [Dev Only]3509Database Pages Preread/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache.  [Dev Only]3511Database Page Preread Stalls/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache but did not complete preread before intended use.  [Dev Only]3513Database Pages Preread (Unnecessary)/sec is the rate that pages are  requested in anticipation of future use but that are already cached by the database cache.  [Dev Only]3515Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]3517Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]3519Database Pages Versioned/sec is the rate at which pages in the database cache are being copied into new pages in the cache for the purpose of being asynchronously written while the current version of that page in the database file is still being modified.  This feature is primarily used to avoid cycles, branches, or long chains of flush order dependencies without requiring the pages involved to be synchronously written to disk.  [Dev Only]3521Database Pages Version Copied/sec is the rate at which pages in the database cache are being copied into new pages in the cache for the purpose of being asynchronously written while the current version of that page in the database file is still being modified.  This feature is primarily used to avoid cycles, branches, or long chains of flush order dependencies without requiring the pages involved to be synchronously written to disk.  [Dev Only]3523Database Pages Repeatedly Written/sec is the rate that pages are written to the database file(s) from the database cache more than once in their lifetime in the cache.  These page writes represent extra writes above the theoretical minimum and can therefore be considered overhead.  [Dev Only]3525Database Pages Flushed (Scavenging.Shrink)/sec is the rate that pages are written to the database file(s) from the database cache during scavenging because the cache size  must shrink.  [Dev Only]3527Database Pages Flushed (Checkpoint)/sec is the rate that pages are written to the database file(s) from the database cache to keep the checkpoint depth down to configured levels.  [Dev Only]3529Database Pages Flushed (Checkpoint Foreground)/sec is the rate that pages are written to the database file(s) from the database cache to keep the checkpoint depth down to configured levels.  [Dev Only]3531Database Pages Flushed (Context Flush)/sec is the rate that pages are written to the database file(s) from the database cache due to a requested flush of a buffer context.  [Dev Only]3533Database Pages Flushed (Filthy Foreground)/sec is the rate that pages are written to the database file(s) from the database cache because they are marked for filthy / immediate flush.  [Dev Only]3535Database Pages Flushed (Scavenging.AvailPool)/sec is the rate at which pages are written to the database file(s) from the database cache during scavenging to replenish the pool of available buffers.  [Dev Only]3537Database Pages Flushed Opportunely/sec is the rate that pages are written to the database file(s) from the database cache because they happen to be near other pages that must be written.  These additional writes are performed before they must happen in the hope that the total number of IOs required to write all the pages is reduced.  [Dev Only]3539Database Pages Flushed Opportunely Clean/sec is the rate that clean pages are opportunely written to the database file(s) from the database  cache because they happen to be betweeen two other pages that must  be written.  These additional writes are performed in the hope that the total number of IOs required to write all the dirty pages is reduced.  [Dev Only]3541Database Pages Coalesced Written/sec is the rate that pages are written to the database file(s) from the database cache coalesced with another page. [Dev Only]3543Database Pages Coalesced Read/sec is the rate that pages are read from the database file(s) to the database cache coalesced with another page. [Dev Only]3545Database Pages Repeatedly Read/sec is the rate that pages are read from the database file(s) into the database cache more than once a short period of time / within history tracking.  [Dev Only]3547Flush Map % Dirty is the percentage of the flush map that has been modified and not persisted since the associated database was attached.  [Dev Only]3549No text3551Flush Map Pages Written Async/sec is the rate at which flush map pages are asynchronously written to the flush map file.  [Dev Only]3553Flush Map Pages Written Sync/sec is the rate at which flush map pages are synchronously written to the flush map file.  [Dev Only]3555Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups.3557Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]3559Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation.  [Dev Only]3561Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]3563Pages Freed/sec is the number of pages per second that are freed from the database by the online defragmentation process [Dev Only]3565Data Moves/sec is the number of times per second that data is moved from one page to another by the online defragmentation process [Dev Only]3567Online Defrag Pages Moved/sec is the number of times per second that data is moved from one page to a new page by the online defragmentation process [Dev Only]3569Online Defrag Log Bytes/sec is the rate at which online defragmentation is generating log bytes.  [Dev Only]3571Database Maintenance Duration is the number of hours that have passed since maintenance last completed for this database.3573Database Maintenance Pages Read is the number of pages read by database maintenance. [Dev Only]3575Database Maintenance Pages Read/sec is the rate at which pages are read by database maintenance. [Dev Only]3577Database Maintenance Pages Zeroed is the number of pages zeroed/scrubbed by database maintenance. [Dev Only]3579Database Maintenance Pages Zeroed/sec is the rate at which pages are zeroed/scrubbed by database maintenance. [Dev Only]3581Database Maintenance Zero Ref Count LVs is the number of zero ref counted LVs deleted by database maintenance. [Dev Only]3583Database Maintenance Pages with Flag Deleted LVs Reclaimed  is the number of LV pages with flag deleted LVs reclaimed  by database maintenance. [Dev Only]3585Database Maintenance IO Reads/sec is the approximate number of Database Maintenance read IO operations generated/sec. [Dev Only]3587Database Maintenance IO Reads Average Bytes is the approximate average size in bytes of Database Maintenance read IO. [Dev Only]3589No text3591Database Maintenance Throttle Setting is the current Database Maintenance throttle setting. [Dev Only]3593Database Maintenance IO Re-Reads/sec is the approximate number of Database Maintenance read IO operations for pages already cached in the buffer manager generated/sec. [Dev Only]3595Database Maintenance Pages Skipped by Recovery is the number of pages that were not scanned as instructed by the transaction log, typically because urgent recovery is needed.  [Dev Only]3597Database Maintenance Pages Skipped by Recovery/sec is the  rate at which pages instructed by the transaction log to be scanned were skipped, typically because urgent recovery is needed.  [Dev Only]3599Database Maintenance Pages Checked for Divergences is the number of pages that were scanned for possible divergence against the tracked scan check log records. [Dev Only]3601Database Maintenance Pages Checked for Divergences/sec is the rate at which pages were scanned for possible divergence against the tracked scan check log records. [Dev Only]3603Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]3605Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]3607Database Tasks Pages Preread/sec is the rate at which database pages are read in anticipation of future use by background database tasks.  [Dev Only]3609Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]3611Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications.  [Dev Only]3613Database Tasks Log Records/sec is the rate at which background database tasks are generating log records.  [Dev Only]3615Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks.  [Dev Only]3617No text3619Database Tasks Log Bytes/sec is the rate at which background database tasks are generating log bytes.  [Dev Only]3621I/O Database Reads (Attached)/sec is the rate of database read operations completed.3623I/O Database Reads (Attached) Average Latency is the average length of time,  in milliseconds, per database read operation.3625No text3627I/O Database Reads (Attached) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]3629No text3631I/O Database Reads (Attached) In Heap is the number of database read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3633I/O Database Reads (Attached) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]3635I/O Database Reads (Recovery)/sec is the rate of database read operations completed.3637I/O Database Reads (Recovery) Average Latency is the average length of time,  in milliseconds, per database read operation.3639No text3641I/O Database Reads (Recovery) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]3643No text3645I/O Database Reads (Recovery) In Heap is the number of database read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3647I/O Database Reads (Recovery) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]3649I/O Database Reads/sec is the rate of database read operations completed.3651I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.3653No text3655I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]3657No text3659I/O Database Reads In Heap is the number of database read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3661I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]3663I/O Log Reads/sec is the rate of logfile read operations completed.3665I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation.3667No text3669I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation.  [Dev Only]3671No text3673I/O Log Reads In Heap is the number of logfile read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3675I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion.  [Dev Only]3677I/O Snapshot Reads/sec is the rate of snapshot read operations completed.  [Dev Only]3679I/O Snapshot Reads Average Latency is the average length of time, in milliseconds, per snapshot read operation.  [Dev Only]3681No text3683I/O Snapshot Reads Average Bytes is the average number of bytes transferred per snapshot read operation.  [Dev Only]3685No text3687I/O Snapshot Reads In Heap is the number of snapshot read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3689I/O Snapshot Reads Async Pending is the number of snapshot read operations asynchronously pending completion.  [Dev Only]3691I/O Database Writes (Attached)/sec is the rate of database write operations completed.3693I/O Database Writes (Attached) Average Latency is the average length of time,  in milliseconds, per database write operation.3695No text3697I/O Database Writes (Attached) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]3699No text3701I/O Database Writes (Attached) In Heap is the number of database write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3703I/O Database Writes (Attached) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]3705I/O Database Writes (Recovery)/sec is the rate of database write operations completed.3707I/O Database Writes (Recovery) Average Latency is the average length of time,  in milliseconds, per database write operation.3709No text3711I/O Database Writes (Recovery) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]3713No text3715I/O Database Writes (Recovery) In Heap is the number of database write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3717I/O Database Writes (Recovery) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]3719I/O Database Writes/sec is the rate of database write operations completed.3721I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.3723No text3725I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]3727No text3729I/O Database Writes In Heap is the number of database write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3731I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]3733I/O Flush Map Writes/sec is the rate of flush map write operations completed.3735I/O Flush Map Writes Average Latency is the average length of time,  in milliseconds, per flush map write operation.3737No text3739I/O Flush Map Writes Average Bytes is the average number of bytes transferred per flush map write operation.  [Dev Only]3741No text3743I/O Log Writes/sec is the rate of log file write operations completed.3745I/O Log Writes Average Latency is the average length of time, in milliseconds, per log file write operation.3747No text3749I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation.  [Dev Only]3751No text3753I/O Log Writes In Heap is the number of logfile write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3755I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion.  [Dev Only]3757I/O Snapshot Writes/sec is the rate of snapshot write operations completed.  [Dev Only]3759I/O Snapshot Writes Average Latency is the average length of time, in milliseconds, per snapshot write operation.  [Dev Only]3761No text3763I/O Snapshot Writes Average Bytes is the average number of bytes transferred per snapshot write operation.  [Dev Only]3765No text3767I/O Snapshot Writes In Heap is the number of snapshot write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]3769I/O Snapshot Writes Async Pending is the number of snapshot write operations asynchronously pending completion.  [Dev Only]3771FlushFileBuffers ops/sec is the rate of FlushFileBuffers operations completed.  [Dev Only]3773FlushFileBuffers Average Latency is the average length of time, in milliseconds, per FlushFileBuffers operation.  [Dev Only]3775No text3777Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]3779Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]3781encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]3783No text3785Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]3787Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]3789Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]3791No text3793Compressed Bytes/sec is the number of bytes per second that were compressed during DML operations.  [Dev Only]3795Compression Ops/sec is the number of compression operations per second that were performed during DML operations.  [Dev Only]3797Average latency per compression operation in microseconds.  [Dev Only]3799No text3801Compression ratio calculated as: uncompressed size / compressed size.  [Dev Only]3803No text3805Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations.  [Dev Only]3807Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations.  [Dev Only]3809Average latency per decompression operation in microseconds.  [Dev Only]3811No text3813Cpu Xpress9 Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations using Xpress9 on the system cpu.  [Dev Only]3815Cpu Xpress9 Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations using Xpress9 on the system cpu.  [Dev Only]3817Cpu Xpress9 Average latency per decompression operation in microseconds.  [Dev Only]3819No text3821Xpress10 Software Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations using Xpress10 software implementation.  [Dev Only]3823Xpress10 Software Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations using Xpress10 software implementation.  [Dev Only]3825Xpress10 Software Average latency per decompression operation in microseconds.  [Dev Only]3827No text3829Xpress10 Corsica Compressed Bytes/sec is the number of bytes per second that were compressed during DML operations using Xpress10 on the Corsica hardware.  [Dev Only]3831Xpress10 Corsica Compression Ops/sec is the number of compression operations per second that were performed during DML operations using Xpress10 on the Corsica hardware.  [Dev Only]3833Xpress10 Corsica Average latency per compression operation in microseconds.  [Dev Only]3835No text3837Xpress10 Corsica Average latency in hardware per compression operation in microseconds.  [Dev Only]3839No text3841Xpress10 Corsica Compression ratio calculated as: original size / compressed size.  [Dev Only]3843No text3845Xpress10 Corsica Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations using Xpress10 on the Corsica hardware.  [Dev Only]3847Xpress10 Corsica Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations using Xpress10 on the Corsica hardware.  [Dev Only]3849Xpress10 Corsica Average latency per decompression operation in microseconds.  [Dev Only]3851No text3853Xpress10 Corsica Average latency in hardware per decompression operation in microseconds.  [Dev Only]3855No text3857Pages Reorganized (Other)/sec is the number of times per second a page was reorganized for some other / unknown reason.  [Dev Only]3859Pages Reorganized (Free Space Request)/sec is the number of times per second a page was reorganized due to a free space request that could not be satisfied by the existing contiguous space on the page.  [Dev Only]3861Pages Reorganized (Page Move Logging)/sec is the number of times per second a page was reorganized for minimizing a page size for logging page move.  [Dev Only]3863Pages Reorganized (Dehydrate Buffer)/sec is the number of times per second a page is reorganized to minimize our in-memory buffer usage.  [Dev Only]3865Database Cache Miss (Attached) Average Latency is the average length of time, in milliseconds, per page cache miss that is satisfied by waiting for a database read operation to be completed.3867No text3869Database Cache Size Unused is the amount of system memory used by the database cache manager to hold information from the database file(s) that may be used in the near future but that hasn�t yet been referenced.  [Dev Only]3871Provides an estimate of the oldest running transaction by elapsed time in milliseconds.3873New Pages/sec is the number of new pages used per second.  [Dev Only]3875Space Trees Deleted/sec is the number of space trees deleted per second.  [Dev Only]3877Space Trees Deleted Freed Pages/sec is the number of pages freed by space trees deletes per second.  [Dev Only]3879Space Trees Deleted Freed Extents/sec is the number of extents freed by space trees deletes per second.  [Dev Only]3881Databases attached to this process3883Database Cache Size (MB) is the amount of system memory, in megabytes, used by the database cache manager to hold commonly used information from the database file(s) to prevent file operations. If the database cache size seems to be too small for optimal performance, and there is very little available memory on the system (see Memory/Available Bytes), an increase of memory in the system may increase performance. If there is a large amount of available memory on the system, and the database cache size is not growing beyond a certain point, the database cache size may be capped at an artificially low limit. An increase in this limit may increase performance.3885I/O Database Reads/sec is the rate of database read operations completed.3887I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.3889No text3891I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]3893No text3895I/O Database Writes/sec is the rate of database write operations completed.3897I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.3899No text3901I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation. [Dev Only]3903No text3905I/O Database Reads (Transactional) Total IO is the number of IOs accumulated   for the database read operation latency counters. [Dev Only]3907I/O Database Reads (Transactional) Mean Latency is the average length of time,  in microseconds, per database read operation. [Dev Only]3909I/O Database Reads (Transactional) 50th Pct Latency is the length of time for  the median or 50th percentile IO, in microseconds, per database read  operation. [Dev Only]3911I/O Database Reads (Transactional) 90th Pct Latency is the length of time for,  the 90th percentile IO, in microseconds, per database read operation. [Dev Only]3913I/O Database Reads (Transactional) 99th Pct Latency is the length of time for,  the 99th percentile IO, in microseconds, per database read operation. [Dev Only]3915I/O Database Reads (Transactional) Max Pct Latency is the length of time for,  the max or 100th percentile IO latency, in microseconds, per database read operation. [Dev Only]3917I/O Database Reads (Maintenance) Total IO is the number of IOs accumulated   for the database read operation latency counters. [Dev Only]3919I/O Database Reads (Maintenance) Mean Latency is the average length of time,  in microseconds, per database read operation. [Dev Only]3921I/O Database Reads (Maintenance) 50th Pct Latency is the length of time for  the median or 50th percentile IO, in microseconds, per database read  operation. [Dev Only]3923I/O Database Reads (Maintenance) 90th Pct Latency is the length of time for,  the 90th percentile IO, in microseconds, per database read operation. [Dev Only]3925I/O Database Reads (Maintenance) 99th Pct Latency is the length of time for,  the 99th percentile IO, in microseconds, per database read operation. [Dev Only]3927I/O Database Reads (Maintenance) Max Pct Latency is the length of time for,  the max or 100th percentile IO latency, in microseconds, per database read operation. [Dev Only]3929I/O Database Writes (Transactional) Total IO is the number of IOs accumulated   for the database write operation latency counters. [Dev Only]3931I/O Database Writes (Transactional) Mean Latency is the average length of time,  in microseconds, per database write operation. [Dev Only]3933I/O Database Writes (Transactional) 50th Pct Latency is the length of time for  the median or 50th percentile IO, in microseconds, per database write  operation. [Dev Only]3935I/O Database Writes (Transactional) 90th Pct Latency is the length of time for,  the 90th percentile IO, in microseconds, per database write operation. [Dev Only]3937I/O Database Writes (Transactional) 99th Pct Latency is the length of time for,  the 99th percentile IO, in microseconds, per database write operation. [Dev Only]3939I/O Database Writes (Transactional) Max Pct Latency is the length of time for,  the max or 100th percentile IO latency, in microseconds, per database write operation. [Dev Only]3941I/O Database Writes (Maintenance) Total IO is the number of IOs accumulated   for the database write operation latency counters. [Dev Only]3943I/O Database Writes (Maintenance) Mean Latency is the average length of time,  in microseconds, per database write operation. [Dev Only]3945I/O Database Writes (Maintenance) 50th Pct Latency is the length of time for  the median or 50th percentile IO, in microseconds, per database write  operation. [Dev Only]3947I/O Database Writes (Maintenance) 90th Pct Latency is the length of time for,  the 90th percentile IO, in microseconds, per database write operation. [Dev Only]3949I/O Database Writes (Maintenance) 99th Pct Latency is the length of time for,  the 99th percentile IO, in microseconds, per database write operation. [Dev Only]3951I/O Database Writes (Maintenance) Max Pct Latency is the length of time for,  the max or 100th percentile IO latency, in microseconds, per database write operation. [Dev Only]3953I/O Database Meted Queue Depth is queued and pending IO operations awaiting an open async IO slot. [Dev Only]3955I/O Database Meted Outstanding Max is the limit on number of Meted Queue IO operations that may be outstanding or issued to the OS at any given time. [Dev Only]3957I/O Database Async Read Pending is the number of async read IO operations outstanding to the OS. [Dev Only]3959Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.3961No text3963Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.3965The RAS Object Type handles individual ports of the RAS device on your system.3967The number of bytes transmitted total for this connection.3969The number of bytes received total for this connection.3971The number of data frames transmitted total for this connection.3973The number of data frames received total for this connection.3975The compression ratio for bytes being transmitted.3977The compression ratio for bytes being received.3979The total number of CRC Errors for this connection.  CRC Errors occur when the frame received contains erroneous data.3981The total number of Timeout Errors for this connection.  Timeout Errors occur when an expected is not received in time.3983The total number of Serial Overrun Errors for this connection.  Serial Overrun Errors occur when the hardware cannot handle the rate at which data is received.3985The total number of Alignment Errors for this connection.  Alignment Errors occur when a byte received is different from the byte expected.3987The total number of Buffer Overrun Errors for this connection.  Buffer Overrun Errors when the software cannot handle the rate at which data is received.3989The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.3991The number of bytes transmitted per second.3993The number of bytes received per second.3995The number of frames transmitted per second.3997The number of frames received per second.3999The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.4001The RAS Object Type handles all combined ports of the RAS device on your system.4003The total number of Remote Access connections.4005Counters for the Windows Search Service Gatherer Project object4007The number of add notifications.4009The number of document additions per second.4011The number of delete notifications.4013The number of document deletes per second.4015The number of modify notifications.4017The number of modify notifications per second.4019The number of documents waiting to be processed. When this number goes to zero the catalog is idle. This number indicates the total queue size of unprocessed documents in the gatherer.4021The number of documents in progress.4023The number of documents on hold because a document with the same URL is currently in process.4025The number of documents delayed due to site hit frequency rules.4027The number of files (URLs) in the history list. This indicates the total size of your document corpus that was indexed.4029The number of documents processed since the history has been reset.4031The number of documents processed per second.4033The number of successfully filtered documents.4035The number of successfully filtered documents per second.4037The number of filtered documents which returned an error.4039The number of filtered documents which returned an error per second.4045The number of file protocol errors received while getting documents.4047The number of file protocol errors received per second.4053The number of documents accessed via file system.4055The number of documents accessed via file system per second.4061The number of office documents filtered.4063The number of office documents filtered per second.4065The number of text documents filtered.4067The number of text documents filtered per second.4069Number of crawls in progress.4071The Gatherer paused flag indicates if the Gatherer has been paused.4073The recovery in progress flag indicates if recovery is currently in progress. Indexing will not be resumed until this flag is off.4075The number of documents which were not filtered because no modification was detected since the last crawl.4077The Iterating history in progress flag indicates if the Gatherer is currently iterating over the URL history.4079Number of incremental crawls in progress.4081The number of documents currently being filtered.4083The number of documents initiated into the Gatherer service. This includes the number of documents on hold, in the active queue, and currently filtered. When this number goes to zero during a crawl, it means the crawl will be done soon.4085The total number of times a document access has been retried. Having this number high may indicate a problem with accessing the data.4087The number of retries per second.4095Documents incorrectly rejected by adaptive crawl4101Documents which have changed since the last crawl4103The number of Move/Rename notifications.4105The number of document Moves and Renames per second.4107Number of unique documents in the system. Documents are considered not unique if their contents is the same.4109Percentage of the history recovery completed4111Counters for the Windows Search Service Gathering service object4113Currently connected external notification sources.4115The total number of notifications received from all notification sources excluding file system.4117The rate of external notifications received per second.4119The number of currently connected administrative clients.4121The total number of heartbeats counted since startup. A heartbeat occurs once every 10 seconds while the service is running. If the service is not running there will be no heartbeat and the number of ticks will not be incremented.4123Displays one heartbeat every 10 seconds.4125The total number of filtering threads in the system. This number is calculated based on your system resources.4127The number of threads waiting for documents.4129The number of document entries currently in memory. Zero means no indexing activity is going on.4131Indicates the level of the amount of system resources that the Gatherer service is allowed to use.4133The number of documents waiting for robot threads. If this number is not 0, all threads should be filtering.4135The number of filtering processes in the system.4137The maximum number of filtering processes that have existed in the system since startup.4139The total number of times a filter process was created or restarted. Having too many filter processes created indicates that filtering is having trouble with the data in the documents.4141The number of documents delayed due to site hit frequency rules.4143The number of servers recently accessed by the system.4145The number of times a new server object had to be created.4147The number of filter objects in the system. Each filter object corresponds to a URL currently being filtered.4149The number of times a filter object was created. This corresponds to the total number of documents filtered in the system since startup.4151The number of documents filtered per second.4153The total number of timeouts detected by the system since startup.4155A server becomes unavailable when a number of requests to that server time out.4157A server becomes unavailable when a number of requests to that server time out.4159The number of threads waiting for a response from the filter process. If no activity is going on and this number is equal to number of filtering threads, it may indicate a network problem or unavailability of the server it is crawling.4161The number of threads waiting for plug-ins to complete an operation.4163The number of documents successfully filtered.4165The number of successfully filtered documents per second.4167The number of documents that will be retried after time-out. When this is non-zero, it means that the local server it is crawling is shut down.4169Number of available cached word breakers instances4171Number of available cached stemmer instances. Too many may indicate a resource usage problem.4173The total number of notifications received from all notification sources including file system.4175The rate of external notifications received per second.4177System IO (disk) traffic rate in KB/s detected by back off logic4179The code describing why the Gatherer service went into back off state. 0 - up and running 1 - high system IO traffic 2 - high notifications rate 3 - delayed recovery in progress (not implemented) 4 - back off due to user activity 5 - Battery Low 6 - Memory Low 99 - back off for some internal reason (forced by Search itself) While backing off, no indexing is performed. To resume the indexing you must eliminate the reason for back off. If the Gatherer service is in back off state, the Search service is paused and there is a message in the event log.4181The number of threads blocked due to back off event4183Indexer PlugIn statistics4185The level of the master index.4187Number of Master Merges to Date4189Master Merge Progress4191Shadow Merge Levels4193Shadow Merge Levels Threshold4195Number of Persistent Indexes4197Size of Index4199Number of Unique Keys4201Number of Documents Filtered4203Number of invalidator work items that were created4205Number of invalidator work items that were deleted4207Number of clean WidSets4209Number of dirty WidSets4211Indicator if a master merge is going on.4213Active Connections4215Number of Queries4217Number of Queries Failed4219Number of Queries Succeeded4221The number of L0 Indexes (Wordlists)4223The number of L0 merges (flushes) in progress at any one moment.4225The average value [documents/hour] computed for the speed of L0 merges (flushes) since the catalog has been loaded4227The number of L0 merges (flushes) since the catalog was loaded4229The last value [documents/hour] computed for the speed of L0 merges (flushes).4231The number of L1 Indexes4233The number of L1 merges in progress at any one moment.4235The average value [documents/hour] computed for the speed of L1 merges since the catalog has been loaded4237The number of L1 merges since the catalog was loaded4239The last value [documents/hour] computed for the speed of L1 merges.4241The number of L2 Indexes4243The number of L2 merges in progress at any one moment.4245The average value [documents/hour] computed for the speed of L2 merges since the catalog has been loaded4247The number of L2 merges since the catalog was loaded4249The last value [documents/hour] computed for the speed of L2 merges.4251The number of L3 Indexes4253The number of L3 merges in progress at any one moment.4255The average value [documents/hour] computed for the speed of L3 merges since the catalog has been loaded4257The number of L3 merges since the catalog was loaded4259The last value [documents/hour] computed for the speed of L3 merges.4261The number of L4 Indexes4263The number of L4 merges in progress at any one moment.4265The average value [documents/hour] computed for the speed of L4 merges since the catalog has been loaded4267The number of L4 merges since the catalog was loaded4269The last value [documents/hour] computed for the speed of L4 merges.4271The number of L5 Indexes4273The number of L5 merges in progress at any one moment.4275The average value [documents/hour] computed for the speed of L5 merges since the catalog has been loaded4277The number of L5 merges since the catalog was loaded4279The last value [documents/hour] computed for the speed of L5 merges.4281The number of L6 Indexes4283The number of L6 merges in progress at any one moment.4285The average value [documents/hour] computed for the speed of L6 merges since the catalog has been loaded4287The number of L6 merges since the catalog was loaded4289The last value [documents/hour] computed for the speed of L6 merges.4291The number of L7 Indexes4293The number of L7 merges in progress at any one moment.4295The average value [documents/hour] computed for the speed of L7 merges since the catalog has been loaded4297The number of L7 merges since the catalog was loaded4299The last value [documents/hour] computed for the speed of L7 merges.4301The number of L8 Indexes4303The number of L8 merges in progress at any one moment.4305The average value [documents/hour] computed for the speed of L8 merges since the catalog has been loaded4307The number of L8 merges since the catalog was loaded4309The last value [documents/hour] computed for the speed of L8 merges.4311SMSvcHost 4.0.0.0 performance counters4313The total number of failures at the protocol layer of net.tcp.4315The total number of failures at the protocol layer of net.pipe.4317The total number of failures dispatching messages received over net.tcp.4319The total number of failures dispatching messages received over net.pipe.4321The total number of connections dispatched over net.tcp.4323The total number of connections dispatched over net.pipe.4325The total number of TCP connections accepted over net.tcp.4327The total number of named pipe connections accepted over net.pipe.4329The number of uri registrations currently active for net.tcp.4331The number of uri registrations currently active for net.pipe.4333The total number of uris that were succesfully registered for net.tcp.4335The total number of uris that were succesfully registered for net.pipe.4337The total number of uris that were succesfully unregistered for net.tcp.4339The total number of uris that were succesfully unregistered for net.pipe.4341Counters for CLR Garbage Collected heap.4343This counter displays the number of times the generation 0 objects (youngest; most recently allocated) are garbage collected (Gen 0 GC) since the start of the application. Gen 0 GC occurs when the available memory in generation 0 is not sufficient to satisfy an allocation request. This counter is incremented at the end of a Gen 0 GC. Higher generation GCs include all lower generation GCs. This counter is explicitly incremented when a higher generation (Gen 1 or Gen 2) GC occurs. _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value.4345This counter displays the number of times the generation 1 objects are garbage collected since the start of the application. The counter is incremented at the end of a Gen 1 GC. Higher generation GCs include all lower generation GCs. This counter is explicitly incremented when a higher generation (Gen 2) GC occurs. _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value.4347This counter displays the number of times the generation 2 objects (older) are garbage collected since the start of the application. The counter is incremented at the end of a Gen 2 GC (also called full GC). _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value.4349This counter displays the bytes of memory that survive garbage collection (GC) and are promoted from generation 0 to generation 1; objects that are promoted just because they are waiting to be finalized are not included in this counter. This counter displays the value observed at the end of the last GC; its not a cumulative counter.4351This counter displays the bytes of memory that survive garbage collection (GC) and are promoted from generation 1 to generation 2; objects that are promoted just because they are waiting to be finalized are not included in this counter. This counter displays the value observed at the end of the last GC; its not a cumulative counter. This counter is reset to 0 if the last GC was a Gen 0 GC only.4353This counter displays the bytes per second that are promoted from generation 0 (youngest) to generation 1; objects that are promoted just because they are waiting to be finalized are not included in this counter. Memory is promoted when it survives a garbage collection. This counter was designed as an indicator of relatively long-lived objects being created per sec. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4355This counter displays the bytes per second that are promoted from generation 1 to generation 2 (oldest); objects that are promoted just because they are waiting to be finalized are not included in this counter. Memory is promoted when it survives a garbage collection. Nothing is promoted from generation 2 since it is the oldest. This counter was designed as an indicator of very long-lived objects being created per sec. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4357This counter displays the bytes of memory that are promoted from generation 0 to generation 1 just because they are waiting to be finalized. This counter displays the value observed at the end of the last GC; its not a cumulative counter.4359This counter displays the process ID of the CLR process instance being monitored. The value displayed will be 0 until after the first garbage collection.4361This counter displays the maximum bytes that can be allocated in generation 0 (Gen 0); its does not indicate the current number of bytes allocated in Gen 0. A Gen 0 GC is triggered when the allocations since the last GC exceed this size. The Gen 0 size is tuned by the Garbage Collector and can change during the execution of the application. At the end of a Gen 0 collection the size of the Gen 0 heap is infact 0 bytes; this counter displays the size (in bytes) of allocations that would trigger the next Gen 0 GC. This counter is updated at the end of a GC; its not updated on every allocation.4363This counter displays the current number of bytes in generation 1 (Gen 1); this counter does not display the maximum size of Gen 1. Objects are not directly allocated in this generation; they are promoted from previous Gen 0 GCs. This counter is updated at the end of a GC; its not updated on every allocation.4365This counter displays the current number of bytes in generation 2 (Gen 2). Objects are not directly allocated in this generation; they are promoted from Gen 1 during previous Gen 1 GCs. This counter is updated at the end of a GC; its not updated on every allocation.4367This counter displays the current size of the Large Object Heap in bytes. Objects greater than a threshold are treated as large objects by the Garbage Collector and are directly allocated in a special heap; they are not promoted through the generations. In CLR v1.1 and above this threshold is equal to 85000 bytes. This counter is updated at the end of a GC; it s not updated on every allocation.4369This counter displays the number of garbage collected objects that survive a collection because they are waiting to be finalized. If these objects hold references to other objects then those objects also survive but are not counted by this counter; the "Promoted Finalization-Memory from Gen 0" and "Promoted Finalization-Memory from Gen 1" counters represent all the memory that survived due to finalization. This counter is not a cumulative counter; its updated at the end of every GC with count of the survivors during that particular GC only. This counter was designed to indicate the extra overhead that the application might incur because of finalization.4371This counter displays the current number of GC Handles in use. GCHandles are handles to resources external to the CLR and the managed environment. Handles occupy small amounts of memory in the GCHeap but potentially expensive unmanaged resources.4373This counter displays the rate of bytes per second allocated on the GC Heap. This counter is updated at the end of every GC; not at each allocation. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4375This counter displays the peak number of times a garbage collection was performed because of an explicit call to GC.Collect. Its a good practice to let the GC tune the frequency of its collections.4377% Time in GC is the percentage of elapsed time that was spent in performing a garbage collection (GC) since the last GC cycle. This counter is usually an indicator of the work done by the Garbage Collector on behalf of the application to collect and compact memory. This counter is updated only at the end of every GC and the counter value reflects the last observed value; its not an average.4379Not Displayed.4381This counter is the sum of four other counters; Gen 0 Heap Size; Gen 1 Heap Size; Gen 2 Heap Size and the Large Object Heap Size. This counter indicates the current memory allocated in bytes on the GC Heaps.4383This counter displays the amount of virtual memory (in bytes) currently committed by the Garbage Collector. (Committed memory is the physical memory for which space has been reserved on the disk paging file).4385This counter displays the amount of virtual memory (in bytes) currently reserved by the Garbage Collector. (Reserved memory is the virtual memory space reserved for the application but no disk or main memory pages have been used.)4387This counter displays the number of pinned objects encountered in the last GC. This counter tracks the pinned objects only in the heaps that were garbage collected e.g. a Gen 0 GC would cause enumeration of pinned objects in the generation 0 heap only. A pinned object is one that the Garbage Collector cannot move in memory.4389This counter displays the current number of sync blocks in use. Sync blocks are per-object data structures allocated for storing synchronization information. Sync blocks hold weak references to managed objects and need to be scanned by the Garbage Collector. Sync blocks are not limited to storing synchronization information and can also store COM interop metadata. This counter was designed to indicate performance problems with heavy use of synchronization primitives.4391Statistics for CLR Class Loader.4393This counter displays the cumulative number of classes loaded in all Assemblies since the start of this application.4395Reserved for future use.4397Reserved for future use.4399This counter displays the peak number of classes that have failed to load since the start of the application. These load failures could be due to many reasons like inadequate security or illegal format. Full details can be found in the profiling services help.4401This counter displays the number of classes that failed to load per second. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval. These load failures could be due to many reasons like inadequate security or illegal format. Full details can be found in the profiling services help.4403This counter displays the current size (in bytes) of the memory committed by the class loader across all AppDomains. (Committed memory is the physical memory for which space has been reserved on the disk paging file.)4405This counter displays the total number of AppDomains unloaded since the start of the application. If an AppDomain is loaded and unloaded multiple times this counter would count each of those unloads as separate.4407This counter displays the number of AppDomains unloaded per second. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4409This counter displays the current number of classes loaded in all Assemblies.4411This counter displays the number of classes loaded per second in all Assemblies. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4413This counter displays the current number of AppDomains loaded in this application. AppDomains (application domains) provide a secure and versatile unit of processing that the CLR can use to provide isolation between applications running in the same process.4415This counter displays the peak number of AppDomains loaded since the start of this application. AppDomains (application domains) provide a secure and versatile unit of processing that the CLR can use to provide isolation between applications running in the same process.4417This counter displays the number of AppDomains loaded per second. AppDomains (application domains) provide a secure and versatile unit of processing that the CLR can use to provide isolation between applications running in the same process. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4419This counter displays the current number of Assemblies loaded across all AppDomains in this application. If the Assembly is loaded as domain-neutral from multiple AppDomains then this counter is incremented once only. Assemblies can be loaded as domain-neutral when their code can be shared by all AppDomains or they can be loaded as domain-specific when their code is private to the AppDomain.4421This counter displays the total number of Assemblies loaded since the start of this application. If the Assembly is loaded as domain-neutral from multiple AppDomains then this counter is incremented once only. Assemblies can be loaded as domain-neutral when their code can be shared by all AppDomains or they can be loaded as domain-specific when their code is private to the AppDomain.4423This counter displays the number of Assemblies loaded across all AppDomains per second. If the Assembly is loaded as domain-neutral from multiple AppDomains then this counter is incremented once only. Assemblies can be loaded as domain-neutral when their code can be shared by all AppDomains or they can be loaded as domain-specific when their code is private to the AppDomain. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4425Stats for CLR Jit.4427This counter displays the total number of methods compiled Just-In-Time (JIT) by the CLR JIT compiler since the start of the application. This counter does not include the pre-jitted methods.4429This counter displays the total IL bytes jitted since the start of the application. This counter is exactly equivalent to the "Total # of IL Bytes Jitted" counter.4431This counter displays the total IL bytes jitted since the start of the application. This counter is exactly equivalent to the "# of IL Bytes Jitted" counter.4433This counter displays the rate at which IL bytes are jitted per second. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4435This counter displays the peak number of methods the JIT compiler has failed to JIT since the start of the application. This failure can occur if the IL cannot be verified or if there was an internal error in the JIT compiler.4437This counter displays the percentage of elapsed time spent in JIT compilation since the last JIT compilation phase. This counter is updated at the end of every JIT compilation phase. A JIT compilation phase is the phase when a method and its dependencies are being compiled.4439Not Displayed.4441Stats for CLR interop.4443This counter displays the current number of Com-Callable-Wrappers (CCWs). A CCW is a proxy for the .NET managed object being referenced from unmanaged COM client(s). This counter was designed to indicate the number of managed objects being referenced by unmanaged COM code.4445This counter displays the current number of stubs created by the CLR. Stubs are responsible for marshalling arguments and return values from managed to unmanaged code and vice versa; during a COM Interop call or PInvoke call.4447This counter displays the total number of times arguments and return values have been marshaled from managed to unmanaged code and vice versa since the start of the application. This counter is not incremented if the stubs are inlined. (Stubs are responsible for marshalling arguments and return values). Stubs usually get inlined if the marshalling overhead is small.4449Reserved for future use.4451Reserved for future use.4453Stats for CLR Locks and Threads.4455This counter displays the total number of times threads in the CLR have attempted to acquire a managed lock unsuccessfully. Managed locks can be acquired in many ways; by the "lock" statement in C# or by calling System.Monitor.Enter or by using MethodImplOptions.Synchronized custom attribute.4457Rate at which threads in the runtime attempt to acquire a managed lock unsuccessfully. Managed locks can be acquired in many ways; by the "lock" statement in C# or by calling System.Monitor.Enter or by using MethodImplOptions.Synchronized custom attribute.4459This counter displays the total number of threads currently waiting to acquire some managed lock in the application. This counter is not an average over time; it displays the last observed value.4461This counter displays the total number of threads that waited to acquire some managed lock since the start of the application.4463This counter displays the number of threads per second waiting to acquire some lock in the application. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4465This counter displays the number of current .NET thread objects in the application. A .NET thread object is created either by new System.Threading.Thread or when an unmanaged thread enters the managed environment. This counters maintains the count of both running and stopped threads. This counter is not an average over time; it just displays the last observed value.4467This counter displays the number of native OS threads created and owned by the CLR to act as underlying threads for .NET thread objects. This counters value does not include the threads used by the CLR in its internal operations; it is a subset of the threads in the OS process.4469This counter displays the number of threads that are currently recognized by the CLR; they have a corresponding .NET thread object associated with them. These threads are not created by the CLR; they are created outside the CLR but have since run inside the CLR at least once. Only unique threads are tracked; threads with same thread ID re-entering the CLR or recreated after thread exit are not counted twice.4471This counter displays the total number of threads that have been recognized by the CLR since the start of this application; these threads have a corresponding .NET thread object associated with them. These threads are not created by the CLR; they are created outside the CLR but have since run inside the CLR at least once. Only unique threads are tracked; threads with same thread ID re-entering the CLR or recreated after thread exit are not counted twice.4473This counter displays the number of threads per second that have been recognized by the CLR; these threads have a corresponding .NET thread object associated with them. These threads are not created by the CLR; they are created outside the CLR but have since run inside the CLR at least once. Only unique threads are tracked; threads with same thread ID re-entering the CLR or recreated after thread exit are not counted twice. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4475Stats for CLR Security.4477This counter displays the total number of runtime Code Access Security (CAS) checks performed since the start of the application. Runtime CAS checks are performed when a caller makes a call to a callee demanding a particular permission; the runtime check is made on every call by the caller; the check is done by examining the current thread stack of the caller. This counter used together with "Stack Walk Depth" is indicative of performance penalty for security checks.4479Reserved for future use.4481This counter displays the total number of linktime Code Access Security (CAS) checks since the start of the application. Linktime CAS checks are performed when a caller makes a call to a callee demanding a particular permission at JIT compile time; linktime check is performed once per caller. This count is not indicative of serious performance issues; its indicative of the security system activity.4483This counter displays the percentage of elapsed time spent in performing runtime Code Access Security (CAS) checks since the last such check. CAS allows code to be trusted to varying degrees and enforces these varying levels of trust depending on code identity. This counter is updated at the end of a runtime security check; it represents the last observed value; its not an average.4485Not Displayed.4487This counter displays the depth of the stack during that last runtime Code Access Security check. Runtime Code Access Security check is performed by crawling the stack. This counter is not an average; it just displays the last observed value.4489Stats for CLR Remoting.4491This counter displays the number of remote procedure calls invoked per second. A remote procedure call is a call on any object outside the caller;s AppDomain. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4493This counter displays the total number of remoting channels registered across all AppDomains since the start of the application. Channels are used to transport messages to and from remote objects.4495This counter displays the total number of remoting proxy objects created in this process since the start of the process. Proxy object acts as a representative of the remote objects and ensures that all calls made on the proxy are forwarded to the correct remote object instance.4497This counter displays the current number of context-bound classes loaded. Classes that can be bound to a context are called context-bound classes; context-bound classes are marked with Context Attributes which provide usage rules for synchronization; thread affinity; transactions etc.4499This counter displays the number of context-bound objects allocated per second. Instances of classes that can be bound to a context are called context-bound objects; context-bound classes are marked with Context Attributes which provide usage rules for synchronization; thread affinity; transactions etc. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4501This counter displays the current number of remoting contexts in the application. A context is a boundary containing a collection of objects with the same usage rules like synchronization; thread affinity; transactions etc.4503This counter displays the total number of remote procedure calls invoked since the start of this application. A remote procedure call is a call on any object outside the caller;s AppDomain.4505Runtime statistics on CLR exception handling.4507This counter displays the total number of exceptions thrown since the start of the application. These include both .NET exceptions and unmanaged exceptions that get converted into .NET exceptions e.g. null pointer reference exception in unmanaged code would get re-thrown in managed code as a .NET System.NullReferenceException; this counter includes both handled and unhandled exceptions. Exceptions that are re-thrown would get counted again. Exceptions should only occur in rare situations and not in the normal control flow of the program.4509This counter displays the number of exceptions thrown per second. These include both .NET exceptions and unmanaged exceptions that get converted into .NET exceptions e.g. null pointer reference exception in unmanaged code would get re-thrown in managed code as a .NET System.NullReferenceException; this counter includes both handled and unhandled exceptions. Exceptions should only occur in rare situations and not in the normal control flow of the program; this counter was designed as an indicator of potential performance problems due to large (>100s) rate of exceptions thrown. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4511This counter displays the number of .NET exception filters executed per second. An exception filter evaluates whether an exception should be handled or not. This counter tracks the rate of exception filters evaluated; irrespective of whether the exception was handled or not. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4513This counter displays the number of finally blocks executed per second. A finally block is guaranteed to be executed regardless of how the try block was exited. Only the finally blocks that are executed for an exception are counted; finally blocks on normal code paths are not counted by this counter. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4515This counter displays the number of stack frames traversed from the frame that threw the .NET exception to the frame that handled the exception per second. This counter resets to 0 when an exception handler is entered; so nested exceptions would show the handler to handler stack depth. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.4517The Telphony System4519The number of telephone lines serviced by this computer.4521The number of telephone devices serviced by this computer.4523the number of telephone lines serviced by this computer that are currently active.4525The number of telephone devices that are currently being monitored.4527The rate of outgoing calls made by this computer.4529The rate of incoming calls answered by this computer.4531The number of applications that are currently using telephony services.4533Current outgoing calls being serviced by this computer.4535Current incoming calls being serviced by this computer.4537BITS Per Job Network Utilization4539Estimate of Remote Server Speed (Bits/Sec)4541Estimate of the local netcard's speed (Bits/Sec)4543Estimate of most recent percent network interface utilization4545Estimate of the IGD's Internet connection speed (Bits/Sec)4547Estimate of most recent percent IGD Internet connection utilization4549Size of the next download block for BITS4551BITS download response interval (msec)4553Estimated bandwidth available to the remote system (Bits/sec)9431ASP.NET global performance counters9433ASP.NET application performance counters9435Number of times the application has been restarted during the web server's lifetime.9437Number of currently running web applications.9439The number of requests disconnected due to communication errors or user terminated.9441The number of milliseconds that it took to execute the most recent request.9443The number of requests rejected because the request queue was full.9445The number of requests waiting to be processed.9447Number of worker processes running on the machine.9449Number of times a worker process has restarted on the machine.9451The number of milliseconds the most recent request was waiting in the queue.9453The current number of sessions currently active.9455The number of sessions that have been explicitly abandoned.9457The number of sessions timed out.9459The number of sessions total.9461The current number of requests, including those that are queued, currently executing, or waiting to be written to the client.  Under the ASP.NET process model, when this counter exceeds the requestQueueLimit defined in the processModel configuration section, ASP.NET will begin rejecting requests.9463Number of audit successes in the application since it was started.9465Number of audit failures in the application since it was started.9467Number of error events raised since the application was started.9469Number of runtime error events raised since the application was started.9471Number of HTTP error events raised since the application was started.9473Requests queued because the concurrency limits have been exceeded.9475Number of requests utilizing anonymous authentication.9477Number of Authentication Anonymous Requests/Sec9479Total number of entries within the cache (both internal and user added)9481Number of additions and removals to the total cache per second.9483Total number of hits from the cache.9485Total number of cache misses.9487Ratio of hits from all cache calls.9489Cache Total Hit Ratio Base9491Total number of entries within the cache added by the user.9493Number of additions and removals to the API cache per second.9495Number of cache hits from user code.9497Number of cache misses called from user code.9499Ratio of hits called from user code.9501Cache API Hit Ratio Base9503Current number of entries in the output cache.9505Number of additions and removals to the output cache per second.9507Total number of output cacheable requests served from the output cache.9509Total number of output cacheable requests not served from the output cache.9511Ratio of hits to requests for output cacheable requests.9513Output Cache Hit Ratio Base9515Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled.9517Number of debugging requests processed.9519Number of errors that have occurred during parsing and configuration.9521Number of errors that have occurred during compilation.9523Number of errors that have occurred during the processing of a request.9525Number of errors not handled by user code, but by the default error handler.9527Rate of unhandled errors.9529Total number of errors occurred.9531Rate of errors occurred.9533Number of active pipeline instances.9535The total size, in bytes, of all requests.9537The total size, in bytes, of responses sent to a client.  This does not include standard HTTP response headers.9539The number of requests currently executing.9541Total number of failed requests.9543The number of requests for resources that were not found.9545Number of requests failed due to unauthorized access.9547The number of requests in the application request queue.9549The number of requests that timed out.9551The number of requests that executed successfully.9553The total number of requests since the application was started.9555The number of requests executed per second.9557The current number of sessions currently active.9559The number of sessions that have been explicitly abandoned.9561The number of sessions timed out.9563Total number of sessions since the application was started.9565The number of transactions aborted.9567The number of transactions committed.9569Number of transactions in progress.9571The total number of transactions since the application was started.9573Transactions started per second.9575The total number of connections to the State Server used by session state.9577The total number of connections to the SQL Server used by session state.9579Total number of instrumentation events raised since the application was started.9581Total number of instrumentation events per second.9583Number of application events raised since the application was started.9585Number of application events raised per second.9587Number of error events raised since the application was started.9589Number of error events per second.9591Number of runtime error events raised since the application was started.9593Number of runtime error events per second.9595Number of HTTP error events raised since the application was started.9597Number of HTTP error events raised per second.9599Number of request events raised since the application was started9601Number of request events raised per second.9603Number of audit successes in the application since it was started.9605Number of audit failures in the application since it was started.9607Number of successful membership credential validations since the application was started.9609Number of failed membership credential validations since the application was started.9611Number of successful forms authentication ticket validations since the application was started.9613Number of failed forms authentication ticket validations since the application was started.9615Number of viewstate MAC validations that failed since the application was started.9617The number of milliseconds that it took to execute the most recent request.9619The number of requests disconnected due to communication errors or user terminated.9621The number of requests rejected because the application request queue was full.9623The number of milliseconds the most recent request was waiting in the queue.9625The amount of physical memory used by the machine divided by the physical memory limit for the cache, as a percentage.  When this reaches 100%, half of the cache entries will be forcibly removed.  The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.9627Cache % Machine Memory Limit Used Base9629The value of private bytes for the worker process divided by the private bytes memory limit for the cache, as a percentage.  When this reaches 100%, half of the cache entries will be forcibly removed.  The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.9631Cache % Process Memory Limit Used Base9633Total number of entries forcibly removed from the cache due to memory pressure.9635Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache using one of the public cache APIs.9637Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache by the output cache feature.9639Estimated percentage of elapsed time that the processor spends executing managed application code.  This counter only tracks processor time of managed threads in the application.  It does not include additional processor time spent executing on non-managed threads.  Note that this counter is only updated with new data every five seconds.9641% Managed Processor Time Base (estimated)9643Estimated managed heap memory consumption (in KB) by the application.  The accuracy of this counter varies depending on the duration of elapsed time since the last full managed memory heap collection.  Note that this counter is only updated with new data every five seconds.9645The total size, in bytes, of data received by ASP.NET on WebSocket connections.9647The total size, in bytes, of data sent to a client on WebSocket connections.9649The number of WebSocket requests currently executing.9651Total number of WebSocket requests that ended up in an aborted state.9653Total number of WebSocket requests that completed gracefully.9655The total number of WebSocket requests since the application was started.9657ASP.NET State Service9883The current number of sessions currently active.9885The number of sessions that have been explicitly abandoned.9887The number of sessions timed out.9889The number of sessions total.9891The Web Service object includes counters specific to the World Wide Web Publishing Service.9893Total Bytes Sent is the number of data bytes that have been sent by the Web service (since service startup).9895Bytes Sent/sec is the rate data bytes are being sent by the Web service.9897Total Bytes Received is the number of data bytes that have been received by the Web service (since service startup).9899Bytes Received/sec is the rate that data bytes are received by the Web service.9901Total bytes either received or sent by the Web service (since service startup).9903Bytes Total/sec is the sum of Bytes Sent/sec and Bytes Received/sec.  This is the total rate of bytes transferred by the Web service.9905Total Files Sent is the total number of files sent by the Web service (since service startup).9907The rate files are sent by the Web service.9909Total Files Received is the total number of files received by the Web service (since service startup).9911The rate files are received by the Web service.9913Total Files Transferred is the sum of Files Sent and Files Received (since service startup).9915The rate files are transferred, that is, sent and received by the Web service.9917Current Anonymous Users is the number of users who currently have an anonymous connection using the Web service.9919Current NonAnonymous Users is the number of users who currently have a non-anonymous connection using the Web service.9921Total Anonymous Users is the total number of users who established an anonymous connection with the Web service (since service startup).9923The rate users are making anonymous connections to the Web service.9925Total NonAnonymous Users is the total number of users who established a non-anonymous connection with the Web service (since service startup).9927The rate users are making non-anonymous connections to the Web service.9929Maximum Anonymous Users is the maximum number of users who established concurrent anonymous connections using the Web service (since service startup).9931Maximum NonAnonymous Users is the maximum number of concurrent non-anonymous connections to the Web service (since service startup).9933Current Connections is the current number of connections established with the Web service.9935Maximum Connections is the maximum number of concurrent connections established with the Web service (since service startup).9937Total Connection Attempts is the number of connections that have been attempted using the Web service (since service startup).  This counter is for all instances listed.9939The rate that connections to the Web service are being attempted.9941Total Logon Attempts is the number of logons attempts to the Web Service (since service startup).9943The rate that logons to the Web service are being attempted.9945Total Options Requests is the number of HTTP requests using the OPTIONS method (since service startup).9947The rate HTTP requests using the OPTIONS method are made.9949Total Get Requests is the number of HTTP requests using the GET method (since service startup).  Get requests are the most common HTTP request.9951The rate HTTP requests using the GET method are made.  Get requests are the most common HTTP request.9953Total Post Requests is the number of HTTP requests using the POST method (since service startup).9955The rate HTTP requests using the POST method are made.9957Total Head Requests is the number of HTTP requests using the HEAD method (since service startup).  Head requests generally indicate a client is querying the state of a document they already have to see if it needs to be refreshed.9959The rate HTTP requests using the HEAD method are made.  Head requests generally indicate a client is querying the state of a document they already have to see if it needs to be refreshed.9961Total Put Requests is the number of HTTP requests using the PUT method (since service startup).9963The rate HTTP requests using the PUT method are made.9965Total Delete Requests is the number of HTTP requests using the DELETE method (since service startup).  Delete requests are generally used for file removals.9967The rate HTTP requests using the DELETE method are made.  Delete requests are generally used for file removals.9969Total Trace Requests is the number of HTTP requests using the TRACE method (since service startup).  Trace requests allow the client to see what is being received at the end of the request chain and use the information for diagnostic purposes.9971The rate HTTP requests using the TRACE method are made.  Trace requests allow the client to see what is being received at the end of the request chain and use the information for diagnostic purposes.9973Total Move Requests is the number of HTTP requests using the MOVE method (since service startup).  Move requests are used for moving files and directories.9975The rate HTTP requests using the MOVE method are made.  Move requests are used for moving files and directories.9977Total Copy Requests is the number of HTTP requests using the COPY method (since service startup).  Copy requests are used for copying files and directories.9979The rate HTTP requests using the COPY method are made.  Copy requests are used for copying files and directories.9981Total Mkcol Requests is the number of HTTP requests using the MKCOL method (since service startup).  Mkcol requests are used to create directories on the server.9983The rate HTTP requests using the MKCOL method are made.  Mkcol requests are used to create directories on the server.9985Total Propfind Requests is the number of HTTP requests using the PROPFIND method (since service startup).  Propfind requests retrieve property values on files and directories.9987The rate HTTP requests using the PROPFIND method are made.  Propfind requests retrieve property values on files and directories.9989Total Proppatch Requests is the number of HTTP requests using the PROPPATCH method (since service startup).  Proppatch requests set property values on files and directories.9991The rate HTTP requests using the PROPPATCH method are made.  Proppatch requests set property values on files and directories.9993Total Search Requests is the number of HTTP requests using the SEARCH method (since service startup).  Search requests are used to query the server to find resources that match a set of conditions provided by the client.9995The rate HTTP requests using the SEARCH method are made.  Search requests are used to query the server to find resources that match a set of conditions provided by the client.9997Total Lock Requests is the number of HTTP requests using the LOCK method (since service startup).  Lock requests are used to lock a file for one user so that only that user can modify the file.9999The rate HTTP requests using the LOCK method are made.  Lock requests are used to lock a file for one user so that only that user can modify the file.10001Total Unlock Requests is the number of HTTP requests using the UNLOCK method (since service startup).  Unlock requests are used to remove locks from files.10003The rate HTTP requests using the UNLOCK method are made.  Unlock requests are used to remove locks from files.10005Total Other Request Methods is the number of HTTP requests that are not OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, MOVE, COPY, MKCOL, PROPFIND, PROPPATCH, SEARCH, LOCK or UNLOCK methods (since service startup).10007The rate HTTP requests are made that do not use the OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, MOVE, COPY, MKCOL, PROPFIND, PROPPATCH, SEARCH, LOCK or UNLOCK methods.10009Total Method Requests is the number of all HTTP requests (since service startup).10011The rate HTTP requests are received.10013Total CGI requests is the total number of CGI requests (since service startup).10015The rate CGI requests are received by the Web service.10017Total ISAPI Extension Requests received (since service startup).10019The rate that ISAPI Extension requests are received by the Web service.10021Total Not Found Errors is the number of requests that couldn't be satisfied by the server because the requested document could not be found (since service startup).  These are generally reported as an HTTP 404 error code to the client.10023The rate of errors due to requests that couldn't be satisfied by the server because the requested document could not be found.  These are generally reported as an HTTP 404 error code to the client.10025Total Locked Errors is the number of requests that couldn't be satisfied by the server because the requested was locked (since service startup).  These are generally reported as an HTTP 423 error code to the client.10027The rate of errors due to requests that couldn't be satisfied by the server because the requested document was locked.  These are generally reported as an HTTP 423 error code to the client.10029Current CGI Requests is the current number of CGI requests being simultaneously processed by the Web service.10031Current ISAPI Extension Requests is the current number of ISAPI requests being simultaneously processed by the Web service.10033Maximum CGI Requests is the maximum number of CGI requests simultaneously processed by the Web service (since service startup).10035Maximum ISAPI Extension Requests is the maximum number of ISAPI requests simultaneously processed by the Web service (since service startup).10037This counter is no longer valid. Value will always be zero.10039This counter is no longer valid. Value will always be zero.10041This counter is no longer valid. Value will always be zero.10043This counter is no longer valid. Value will always be zero.10045This counter is no longer valid. Value will always be zero.10047Total requests temporarily blocked due to bandwidth throttling settings (since service startup).10049Total requests allowed by bandwidth throttling settings (since service startup).10051Total requests rejected due to bandwidth throttling settings (since service startup).10053Current requests temporarily blocked due to bandwidth throttling settings.10055This counter is no longer valid. Value will always be zero.10057Measured bandwidth of asynchronous I/O averaged over a minute.10059Total bytes blocked due to bandwidth throttling settings (since service startup).10061Current bytes temporarily blocked due to bandwidth throttling settings.10063The length of time the Web Service has been running.10065The Web Service Cache Counters object includes cache counters specific to the World Wide Web Publishing Service.10067Current number of files whose content is in the user-mode cache.10069Total number of files whose content was ever added to the user-mode cache (since service startup).10071Total number of successful lookups in the user-mode file cache (since service startup).10073Total number of unsuccessful lookups in the user-mode file cache (since service startup).10075The ratio of user-mode file cache hits to total cache requests (since service startup).10079The number of files removed from the user-mode cache (since service startup).10081Current number of bytes used for the user-mode file cache.10083Maximum number of bytes used for user-mode file cache (since service startup).10085Active Flushed Entries are file handles cached in user-mode that will be closed when all current transfers complete.10087Total Flushed Files is the number of file handles that have been removed from the user-mode cache (since service startup).10089URI information blocks currently in the user-mode cache.10091Total number of URI information blocks added to the user-mode cache (since service startup).10093Total number of successful lookups in the user-mode URI cache (since service startup).10095Total number of unsuccessful lookups in the user-mode URI cache (since service startup).10097The ratio of user-mode URI Cache Hits to total cache requests (since service startup).10101User-mode URI Cache flushes (since service startup).10103The number of URI information blocks that have been removed from the user-mode cache (since service startup).10105Current number of metadata information blocks currently in the user-mode cache.10107Total number of metadata information blocks added to the user-mode cache (since service startup).10109Total number of successful lookups in the user-mode metadata cache (since service startup).10111Total number of unsuccessful lookups in the user-mode metadata cache (since service startup).10113The ratio of user-mode metadata cache hits to total cache requests (since service startup).10117The number of user-mode metadata cache flushes (since service startup).10119Total Flushed Metadata is the number of Metadata information blocks that have been removed from the user-mode cache (since service startup).10121URI information blocks currently cached by the kernel.10123Total number of URI information blocks added to the kernel cache (since service startup).10125Total number of successful lookups in the kernel URI cache (since service startup).10127The rate of kernel URI Cache hits.10129Total number of unsuccessful lookups in the kernel URI cache (since service startup).10131The ratio of kernel URI cache hits to total cache requests (since service startup).10135Kernel URI Cache Flushes (since server startup).10137The number of URI information blocks that have been removed from the kernel cache (since service startup).10139Current memory usage by output cache.10141Number of items currently in output cache.10143Total number of hits in output cache.10145Total number of misses in output cache.10147Total number of flushes in output cache.10149Number of items that have been flushed, but are still being used by outgoing responses so are still taking up memory.10151Total number of items flushed by cache.10153Output Cache current hit ratio. Calculated as (H)/(H+M) where H and M represent Hits and Misses in previous sample interval respectively.10155ASP.NET global performance counters10157ASP.NET application performance counters10159Number of times the application has been restarted during the web server's lifetime.10161Number of currently running web applications.10163The number of requests disconnected due to communication errors or user terminated.10165The number of milliseconds that it took to execute the most recent request.10167The number of requests rejected because the request queue was full.10169The number of requests waiting to be processed.10171Number of worker processes running on the machine.10173Number of times a worker process has restarted on the machine.10175The number of milliseconds the most recent request was waiting in the queue.10177The current number of sessions currently active.10179The number of sessions that have been explicitly abandoned.10181The number of sessions timed out.10183The number of sessions total.10185The current number of requests, including those that are queued, currently executing, or waiting to be written to the client.  Under the ASP.NET process model, when this counter exceeds the requestQueueLimit defined in the processModel configuration section, ASP.NET will begin rejecting requests.10187Number of audit successes in the application since it was started.10189Number of audit failures in the application since it was started.10191Number of error events raised since the application was started.10193Number of runtime error events raised since the application was started.10195Number of HTTP error events raised since the application was started.10197Requests queued because the concurrency limits have been exceeded.10199Number of requests utilizing anonymous authentication.10201Number of Authentication Anonymous Requests/Sec10203Total number of entries within the cache (both internal and user added)10205Number of additions and removals to the total cache per second.10207Total number of hits from the cache.10209Total number of cache misses.10211Ratio of hits from all cache calls.10213Cache Total Hit Ratio Base10215Total number of entries within the cache added by the user.10217Number of additions and removals to the API cache per second.10219Number of cache hits from user code.10221Number of cache misses called from user code.10223Ratio of hits called from user code.10225Cache API Hit Ratio Base10227Current number of entries in the output cache.10229Number of additions and removals to the output cache per second.10231Total number of output cacheable requests served from the output cache.10233Total number of output cacheable requests not served from the output cache.10235Ratio of hits to requests for output cacheable requests.10237Output Cache Hit Ratio Base10239Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled.10241Number of debugging requests processed.10243Number of errors that have occurred during parsing and configuration.10245Number of errors that have occurred during compilation.10247Number of errors that have occurred during the processing of a request.10249Number of errors not handled by user code, but by the default error handler.10251Rate of unhandled errors.10253Total number of errors occurred.10255Rate of errors occurred.10257Number of active pipeline instances.10259The total size, in bytes, of all requests.10261The total size, in bytes, of responses sent to a client.  This does not include standard HTTP response headers.10263The number of requests currently executing.10265Total number of failed requests.10267The number of requests for resources that were not found.10269Number of requests failed due to unauthorized access.10271The number of requests in the application request queue.10273The number of requests that timed out.10275The number of requests that executed successfully.10277The total number of requests since the application was started.10279The number of requests executed per second.10281The current number of sessions currently active.10283The number of sessions that have been explicitly abandoned.10285The number of sessions timed out.10287Total number of sessions since the application was started.10289The number of transactions aborted.10291The number of transactions committed.10293Number of transactions in progress.10295The total number of transactions since the application was started.10297Transactions started per second.10299The total number of connections to the State Server used by session state.10301The total number of connections to the SQL Server used by session state.10303Total number of instrumentation events raised since the application was started.10305Total number of instrumentation events per second.10307Number of application events raised since the application was started.10309Number of application events raised per second.10311Number of error events raised since the application was started.10313Number of error events per second.10315Number of runtime error events raised since the application was started.10317Number of runtime error events per second.10319Number of HTTP error events raised since the application was started.10321Number of HTTP error events raised per second.10323Number of request events raised since the application was started10325Number of request events raised per second.10327Number of audit successes in the application since it was started.10329Number of audit failures in the application since it was started.10331Number of successful membership credential validations since the application was started.10333Number of failed membership credential validations since the application was started.10335Number of successful forms authentication ticket validations since the application was started.10337Number of failed forms authentication ticket validations since the application was started.10339Number of viewstate MAC validations that failed since the application was started.10341The number of milliseconds that it took to execute the most recent request.10343The number of requests disconnected due to communication errors or user terminated.10345The number of requests rejected because the application request queue was full.10347The number of milliseconds the most recent request was waiting in the queue.10349The amount of physical memory used by the machine divided by the physical memory limit for the cache, as a percentage.  When this reaches 100%, half of the cache entries will be forcibly removed.  The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.10351Cache % Machine Memory Limit Used Base10353The value of private bytes for the worker process divided by the private bytes memory limit for the cache, as a percentage.  When this reaches 100%, half of the cache entries will be forcibly removed.  The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.10355Cache % Process Memory Limit Used Base10357Total number of entries forcibly removed from the cache due to memory pressure.10359Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache using one of the public cache APIs.10361Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache by the output cache feature.10363Estimated percentage of elapsed time that the processor spends executing managed application code.  This counter only tracks processor time of managed threads in the application.  It does not include additional processor time spent executing on non-managed threads.  Note that this counter is only updated with new data every five seconds.10365% Managed Processor Time Base (estimated)10367Estimated managed heap memory consumption (in KB) by the application.  The accuracy of this counter varies depending on the duration of elapsed time since the last full managed memory heap collection.  Note that this counter is only updated with new data every five seconds.10369The total size, in bytes, of data received by ASP.NET on WebSocket connections.10371The total size, in bytes, of data sent to a client on WebSocket connections.10373The number of WebSocket requests currently executing.10375Total number of WebSocket requests that ended up in an aborted state.10377Total number of WebSocket requests that completed gracefully.10379The total number of WebSocket requests since the application was started.10767Statistics related to memory broker clerks10769The number of pages evicted from the broker clerk by last periodic eviction10771The internal value of memory for entry count pressure, in ms per page per ms, multiplied by 10 billion and truncated to an integer10773The current size of the clerk simulation, in pages10775The value of memory to the clerk, in ms per page per ms, multiplied by 10 billion and truncated to an integer10777The size of the the clerk, in pages10779The number of pages per second evicted from the broker clerk by memory pressure10781Statistics related to SQL Servers buffer manager10783Percentage of pages that were found in the buffer pool without having to incur a read from disk.10785Number of buffer pool extension page reads/writes outstanding.10787Number of requests that had to wait for a free page.10789Number of buffer pool extension page evictions.10791Number of physical database page writes issued.10793Number of pages in the buffer pool with database content.10795Average seconds a page will stay in the buffer pool extension without references.10797Number of seconds a page will stay in the buffer pool without references.10799Number of pages flushed to enforce the recovery interval settings.10801Base for prior entry10803Number of pages needed to fill the buffer pool extension cache.10805Time (microseconds) spent issuing readahead.10807Number of pages occupying buffer pool extension cache.10809Percentage of the buffer pool extension paging file occupied by buffer manager pages.10811Number of pages flushed by checkpoint or other operations that require all dirty pages to be flushed.10813Number of buffers written by buffer manager's lazy writer.10815Number of buffer pool extension page reads issued.10817Number of physical database page reads issued.10819Number of Extension page writes issued.10821Number of pages read in anticipation of use.10823The slope that integral controller for the buffer pool last used, times -10 billion10825Ideal number of pages in the buffer pool.10827Number of requests to find a page in the buffer pool.10829Statistics related to SQL Server's buffer pool by NUMA node10831Number of lookup requests from this node which were satisfied from other nodes.10833Number of seconds a page will stay in the buffer pool without references.10835Database pages on node.10837Number of lookup requests from this node which were satisfied from this node.10839Server General Statistics10841Number of Mars Deadlocks detected.10843Number of SOAP Session initiate requests started per second.10845Number of trace event notification instances waiting in the internal queue to be sent thru Service Broker10847Number of SOAP Session terminate requests started per second.10849Number of users connected to the system.10851Number of currently blocked processes.10853Number of authenticated HTTP requests started per second.10855Number of temporary tables/table variables created/sec10857Total number of connection resets per second.10859Number of transaction enlistments (local, dtc, and bound).10861Number of temporary tables/table variables in use10863Number of duplicate tempdb recovery unit id generated10865Number of duplicate tempdb rowset id generated10867Number of temporary tables/table variables waiting to be destroyed by the cleanup system thread10869Number of logical connections to the system.10871Number of waits for the File IO Provider lock per second10873Number of non-atomic yields per second.10875Number of empty SOAP requests started per second.10877Total number of logins started per second.10879Number of SOAP Web Service Description Language requests started per second.10881Number of SOAP SQL requests started per second.10883Number of SOAP method invocations started per second.10885Total number of logouts started per second.10887Number of event notifications waiting to be dropped by a system thread10889Describes statistics for individual lock server lock requests10891Number of new locks and lock conversions requested from the lock manager.10893Number of lock requests that timed out. This includes requests for NOWAIT locks.10895Number of lock requests that timed out. This does not include requests for NOWAIT locks.10897Total wait time (milliseconds) for locks in the last second.10899Number of lock requests that resulted in a deadlock.10901Base for Averate Wait Time.10903Number of lock requests that could not be satisfied immediately and required the caller to wait before being granted the lock.10905The average amount of wait time (milliseconds) for each lock request that resulted in a wait.10907This defines a Database manager object for SQL Server10909Bytes read per second from XLog Server.10911Number of bucket misses when checking for stale LSNs.10913Count of committed global transactions in the database10915Average latency in microseconds between log blocks entering the Direct Log Consumer and being retrieved by the XTP controller, per second.10917Number of partitions10919Rate of Log block push fails due to being low on memory.10921Current total active log stored in the shared cache buffer manager in bytes.10923Number of versions generated with in-row diff style.10925Number of secondary partitions10927Number of forwarder pending partitions10929Log disk reads via log pool.10931Number of replica copy requests waiting10933Number of in-delete partitions10935Milliseconds it took to perform the writes of log flushes completed in the last second10937Rate of raw hash entry inserts into the Log Pool.10939Number of log writes by the background log writer.10941Average latency in microseconds for XLog blocks requested.10943Base for DB_LOGPOOL_DIST_FROM_EOL10945Count of global transactions aborted by the user in the database10947Count of aborted global transactions10949KiloBytes bulk copied.10951The cumulative size of all the data files in the database.10953Number of transactions started for the database.10955Replication transaction rate (replicated transactions/sec.).10957Average distance in bytes from end of log per log pool request, for requests in the last VLF.10959Current total memory usage of the shared cache buffer manager in bytes.10961Number of active update transactions for the database.10963The size of the in-memory part of the commit table for the database.10965Log pool cache misses due to block requested being behind truncation LSN.10967Number of records retrieved from the persistent version store.10969Count of global transactions force committed by the user in the database10971Total wait time (milliseconds).10973Percentage of log cache reads that were satisfied from the log cache.10975Count of global transactions that are in doubt10977Reads performed through the log manager cache.10979Max response time for commit request10981Base for DB_XTP_CTRL_DLC_LATENCY10983Total number of log bytes flushed.10985Number of versions generated with in-row diff style.10987The percent of space in the log that is in use.10989Amount of time (microseconds) spent in log writer queue.10991Duration of the last checkpoint for this database10993Log Pool requests that were not in the last VLF of the log.10995Rate of hash lookups failing due to being invalid.10997Number of committed transactions recorded in the commit table for the database.10999Number of log flushes.11001The largest recorded latency, in microseconds, of a fetch from the Direct Log Consumer by the XTP controller.11003Number of records inserted to the persistent version store.11005Rate of Log block push fails due to empty free pool.11007Count of active parallel redo threads11009Total number of log shrinks for this database.11011Number of secondary/forwarder partitions in build11013Read/write throughput for backup/restore of a database.11015Avg resp time for commit request11017Number of transactions which wrote to the database in the last second.11019The cumulative used size of all the log files in the database.11021Number of pages allocated to the persistent version store.11023Log block requests performed through log pool.11025Rate of Log block pushes by log scans, which may come from disk or memory.11027Group stall time (microseconds) per second.11029Maximum count of active global transactions in the database11031Number of rows bulk copied.11033Base for avg commit resp time.11035Rate of flush file buffer calls for WAL enforcement11037Min response time for commit request11039Total number of log truncations for this database.11041Total number of log growths for this database.11043Number of forwarder partitions11045Number of pages deallocated from the persistent version store.11047Number of transactions which committed to the database in the last second but did not harden.11049Base for DB_XLOG_COMPUTE_READ_LATENCY11051Number of bucket misses when adding LSNs to writePageRecorder.11053The amount of memory used by XTP in the database.11055Current log governor tare rate11057Number of nothing partitions11059Number of pending replication transactions in the database.11061Count of active global trans11063Number of commits waiting on log flush.11065The amount of log bytes processed by the XTP controller thread, per second.11067The rate data is being moved by Autoshrink, DBCC SHRINKDATABASE or SHRINKFILE.11069Rate of raw hash entry deletes from the Log Pool.11071Number of primary partitions11073Current log governor usage as percentage of allowance.11075Duration of the recovery for this database in seconds11077Logical read scan rate for DBCC commands11079The cumulative size of all the log files in the database.11081Number of secondary/forwarder partitions in catchup11083Number of bucket swaps in writePageRecorder.11085Rate of Log block pushes by log writer thread.11087Rate of Log block push fails due to free buffer unavailable.11089Log block cache misses from log pool.11091Base for log cache calculations11093Describes statistics for the free pool inside the Log Pool11095Length of the free list.11097Number of buffers being allocated for refill, per second.11099This defines a log host object for SQL Server11101Rate of host log sector payloads being written11103Rate of defunct tenant mapping table cleanup11105Time (microseconds) requests spent in write queue11107Duration of throttled log writes11109Rate of log sectors being written directly to data11111Time spent retrieving log blocks for reads11113Rate of host log being read11115Time (microseconds) spent on long updates by writer thread11117Rate of host log being read found in log11119Time spent looking up mapping entries for reads11121Rate of writes by writer thread11123Rate of long updates by writer thread11125Rate of host log being read found in data11127Rate of host log sectors being written11129How many write requests are queued at time of last enqueue11131Rate of log sectors being cleared during move11133Rate of log sectors being moved to data11135Number of physical reads done against index for mapping update11137Number of physical reads done against base table for mapping update11139Rate of throttled log writes11141Time spent waiting for mapping tran to harden11143Time (microseconds) spent doing mapping table updates for write request11145This defines a Database Mirroring object for SQL Server11147Number of sends initiated per second11149Number of compressed bytes of log sent in the last second.11151Milliseconds messages waited for acknowledgement from the partner per second.11153Total number of kilobytes that redo on the mirror database is behind the hardened log11155Number of compressed bytes of log received in the last second.11157Total number of kilobytes of log that have not been sent to the mirror server11159Number of bytes sent per second11161Number of bytes of log sent per second11163Total number of kilobytes of log that remain to be scanned by the new mirror server after failover.11165Number of mirroring message receives per second11167Milliseconds log blocks waited to be hardened to disk in the last second.11169Number of bytes received per second11171Milliseconds log stream messages waited for send flow control in the last second.11173Number of sent log bytes which were sent from the Database Mirroring log cache in the last second.11175Number of log bytes which were redone from the Database Mirroring log cache per second.11177Number of milliseconds transaction termination waited for acknowledgement per second.11179Number of transactions which wrote to the mirrored database in the last second, that waited for log to be sent to the mirror.11181Number of bytes of log received per second11183Total number of kilobytes of log that have been scanned by the new mirror server after failover.11185Number of bytes of log redone by the mirror database per second11187Number of pages sent per second11189This defines a HADR secondary database object for SQL Server11191The amount of log in kilobytes remaining to finish the undo phase.11193The number of database flow control per sec.11195The number of log blocks compressed per sec.11197Amount of log records redone in the last second to catch up the database replica11199The amount of log in bytes compressed per sec.11201Number of log blocks that is waiting to be applied to the database replica11203Amount of logs received by the availability replica for the database11205Total number of hardened log in kilobytes that is waiting to be redone on the secondary11207Number of transactions which wrote to the mirrored database in the last second, that waited for log to be sent to the mirror.11209Number of times redo gets blocked in the last second11211Number of microseconds all transactions group commit waited11213Amount of filestream data received by the availability replica for the database11215Number of milliseconds transaction termination waited for acknowledgement per second.11217The amount of log in kilobytes remaining to be redone to finish the reverting phase.11219Amount of logs in kilobytes that is waiting to be send to the database replica11221Duration spent in database flow control wait in microseconds.11223The number of log block compression cache misses per sec.11225The amount of log in bytes decompressed per sec.11227The number of log blocks redone in the last second to catch up the database replica11229The number of log block compression cache hits per sec.11231Number of times transactions waited for group commit.11233The number of log blocks decompressed per sec.11235The amount of log in kilobytes that need to be undone.11237Number of log blocks that is waiting and ready to be applied to the database replica11239This defines a HADR availability replica object for SQL Server11241Total sends to the availability replica11243Number of flow control initiated in the last second11245Number of messages being resent in the last second11247Time in milliseconds messages waited on flow control in the last second11249Total bytes receieved from the availability replica11251Total bytes sent to transport for the availabilty replica11253Total sends to transport for the availability replica11255Total bytes sent to the availabilty replica11257Total receives from the availability replica11259Collects statistics associated with internal server latches11261Number of latch requests that could not be granted immediately and had to wait before being granted.11263Number of SuperLatches that have been demoted to regular latches11265Total latch wait time (milliseconds) for latch requests that had to wait in the last second.11267Base for Average Latch Wait Time.11269Number of latches that have been promoted to SuperLatches11271Number of latches that are currently SuperLatches.11273Average latch wait time (milliseconds) for latch requests that had to wait.11275Collects statistics associated with the database server access methods11277The number of times that a leaf page cookie could not be used during an index search since changes happened on the leaf page. The cookie is used to speed up index search.11279Number of ghosted records per second skipped during scans.11281Number of times the scan point had to be revalidated to continue the scan.11283The number of rowsets per second created as a result of aborted online index build operations that were successfully dropped by the background task that cleans up deferred dropped rowsets.11285Count of temporary LOBs created.11287Count of large object (LOB) values that were passed by reference. By-reference lobs are used in certain bulk operations to avoid the cost of passing them by value.11289Number of probe scans per second that are used to find at most one single qualified row in an index or base table directly.11291Count of lob pages on which readahead was issued.11293Number of times a tree page cookie was used successfully during an index search since no change happened on the parent page of the tree page. The cookie is used to speed up index search.11295Percent of worktables from cache base.11297Number of extents allocated per second in all databases in this SQL Server instance.11299Count of values that were pushed from in-row to off-row.11301Number of times a database page was compressed11303The number of batches that completed successfully per second by the background task that cleans up deferred dropped allocation units.11305Percentage of work tables created where the initial two pages of the work table were not allocated but were immediately available from the work table cache.11307Number of qualified range scans through indexes per second.11309Number of attempts to compress a database page per second11311Count of values that were pulled in-row from off-row.11313The number of batches per second that failed and required retry, by the background task that cleans up deferred dropped allocation units. Failure could be due to lack of memory or disk space, hardware failure and other reasons.11315Number of scans per second that were initiated to search for free space within pages already allocated to an allocation unit to insert or modify record fragments. Each scan may find multiple pages.11317The number of times that a tree page cookie could not be used during an index search since changes happened on the parent pages of those tree pages. The cookie is used to speed up index search.11319Number of pages deallocated per second in all databases in this SQL Server instance. These include pages from mixed extents and uniform extents.11321Number of unrestricted full scans. These can either be base table or full index scans.11323The number of times locks on a table were escalated.11325Number of records fetched through forwarded record pointers.11327Count of by-reference lob values that were used. By-reference lobs are used in certain bulk operations to avoid the cost of passing them by value.11329The number of rowsets created as a result of aborted online index build operations that are waiting to be dropped by the background task that cleans up deferred dropped rowsets.11331Number of page splits per second that occur as a result of overflowing index pages.11333Number of times a reader needs to wait for a page because the InSysXact bit is set11335Count of LOB Storage Service Providers truncated.11337The number of rowsets per second created as a result of aborted online index build operations that were skipped by the background task that cleans up deferred dropped rowsets created.11339Number of times a leaf page cookie was used successfully during an index search since no change happened on the leaf page. The cookie is used to speed up index search.11341Number of pages fetched per second by free space scans. These scans search for free space within pages already allocated to an allocation unit, to satisfy requests to insert or modify record fragments.11343The number of allocation units waiting to be dropped by the background task that cleans up deferred dropped allocation units.11345Number of pages allocated per second in all databases in this SQL Server instance. These include pages allocations from both mixed extents and uniform extents.11347Count of LOB Storage Service Providers created. One worktable created per LOB Storage Service Provider.11349Number of work files created per second. For example, work files could be used to store temporary results for hash joins and hash aggregates.11351Number of extents deallocated per second in all databases in this SQL Server instance.11353Count of temporary LOBs destroyed.11355Number of index searches. Index searches are used to start range scans, single index record fetches, and to reposition within an index.11357The number of allocation units per second that were successfully dropped by the background task that cleans up deferred dropped allocation units. Each allocation unit drop requires multiple batches.11359Number of pages allocated per second from mixed extents. These could be used for storing the IAM pages and the first eight pages that are allocated to an allocation unit.11361Number of work tables created per second. For example, work tables could be used to store temporary results for query spool, LOB variables, XML variables, and cursors.11363Count of LOB Storage Service Providers destroyed.11365Statistics about errors in SQL Server11367Number of errors/sec11369Collects statistics associated with SQL requests11371Number of failed auto-parameterizations.11373Number of unsafe auto-parameterizations.11375Number of plan executions per second in which a plan guide could not be honored during plan generation. The plan guide was disregarded and normal compilation was used to generate the executed plan.11377Number of attentions per second.11379Number of statements parameterized by forced parameterization per second.11381Number of safe auto-parameterizations.11383Number of SQL batch requests received by server.11385Number of plan executions per second in which the query plan has been generated by using a plan guide.11387Number of SQL re-compiles.11389Number of SQL compilations.11391Number of auto-parameterization attempts.11393This defines cache counters11395Number of cache objects in the cache11397Base for prior entry11399Number of 8k pages used by cache objects11401Ratio between cache hits and lookups11403Number of cache objects in use11405Counters for cursor properties grouped by type11407Amount of memory consumed by cursors (KB).11409Ratio between cache hits and lookups11411Times each type of cached cursor has been used11413Number of cursor plans.11415Number of cursors of a given type in the cache11417Number of SQL cursor requests received by server.11419Base for prior entry11421Number of worktables used by cursors.11423Number of active cursors.11425Counters for cursor properties not grouped by type11427Number of cursor conversions/sec.11429Total number of times a flush for a cursor xstmt occured.11431Number of cursors being populated asynchronously.11433This defines memory usage.11435Total amount of dynamic memory the server is using for the dynamic SQL cache11437Total amount of memory available for grants to executing processes. This memory is used primarily for hash, sort and create index operations.11439Total amount of dynamic memory the server is using for Log Pool11441The external value of memory, in ms per page per ms, multiplied by 10 billion and truncated to an integer11443Ideal amount of memory the server is willing to consume11445Amount of memory the server is currently not using.11447The current number of allocated lock owner blocks.11449Current number of processes that have successfully acquired a workspace memory grant11451Total amount of dynamic memory the server is currently consuming11453The current number of lock blocks that are in use on the server. Refreshed periodically.11455Amount of memory the server is currently using for the purposes other than the database pages.11457Current number of processes waiting for a workspace memory grant11459Amount of memory the server is currently using for the database cache.11461Total amount of dynamic memory the server is using for locks11463The number of lock owner blocks that are currently in use on the server. Refreshed periodically.11465Total amount of dynamic memory the server is using for maintaining connections11467The current number of allocated lock blocks.11469Total amount of dynamic memory the server is using for query optimization11471Amount of memory the server has reserved for future usage. This counter shows current unused amount of the initial grant shown in Granted Workspace Memory (KB).11473Total amount of memory granted to executing processes. This memory is used for hash, sort and create index operations.11475This defines memory usage per NUMA node.11477Non NUMA-local amount of memory on this node.11479Amount of memory the server is not using on this node.11481Ideal amount of memory for this node.11483Amount of memory the server is using on this node for database pages.11485Total amount of memory the server has committed on this node.11487Amount of memory the server is using on this node for the purposes other than database pages.11489This defines user definable counters11491As defined by the user.11493Replication Summary11495The number of replication agents currently running.11497Replication Merge Agent Statistics11499The number of rows per second merged from the Subscriber to the Publisher.11501The number of conflicts per second occurring during the merge process.11503The number of rows per second merged from the Publisher to the Subscriber.11505Replication Logreader Agent Statistics11507The number of commands per second delivered to the Distributor.11509The current amount of time, in milliseconds, elapsed from when transactions are applied at the Publisher to when they are delivered to the Distributor.11511The number of transactions per second delivered to the Distributor.11513Replication Distribution Agent Statistics11515The number of transactions per second delivered to the Subscriber.11517The number of commands per second delivered to the Subscriber.11519The current amount of time, in milliseconds, elapsed from when transactions are delivered to the Distributor to when they are applied at the Subscriber.11521Replication Snapshot Agent Statistics11523The number of transactions per second delivered to the Distributor.11525The number of commands per second delivered to the Distributor.11527This defines a backup device object for SQL Server11529Read/write throughput for a backup device.11531Statistics related to SQL Server transactions.11533The size of the version store in KB.11535The longest running time of any transaction in seconds.11537The total number of active transactions.11539Truncation of unit in Version Store.11541The total number of active non-snapshot transactions that generate version records.11543The total number of active snapshot transactions.11545The total number of active snapshot transactions that do updates.11547Number of unit in Version Store.11549Creation of new unit in Version Store.11551The version generation rate in KB per seconds.11553The version cleanup rate in KB per seconds.11555The free space in tempdb in KB.11557The fraction of update snapshot transactions that have update conflicts to the total number of update snapshot transactions.11559The total number of update snapshot transactions.11561Service Broker Statistics11563The number of priority 8 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11565The number of priority 3 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11567The number of priority 7 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11569The number of message fragments from the transport that are successfully delivered into local target queues per second. Note that the message can be marked as disabled if it is incomplete and/or out of order.11571The number of priority 4 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11573Total number of SQL SEND commands processed by the Broker.11575Total number of message fragments from the transport that are successfully delivered into local target queues. Note that the message can be marked as disabled if it is incomplete and/or out of order.11577The number of SQL RECEIVE commands processed by the Broker per second.11579Total number of messages from local endpoints and the transport that are successfully delivered into local target queues.11581The number of priority 10 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11583The number of corrupted messages that were received in the instance.11585The number of messages that have been removed from the broker transmission queue per second.11587The number of messages from local endpoints and the transport that are successfully delivered into local target queues per second.11589The number of SQL SEND commands processed by the Broker per second.11591Total number of forwarded messages discarded due to forwarded message memory limits, age limits, etc.11593The number of dialog endpoint related timer events in the Broker.11595The number of times an activation stored procedure exited with an error.11597The number of messages that have been placed into the broker transmission queue per second.11599The number of forwarded message bytes successfully sent per second.11601The number of forwarded messages that have not been successfully sent yet.11603The number of messages that were received in the instance but could not be delivered.11605Total number of SQL RECEIVE commands processed by the Broker.11607The number of messages from the transport that are successfully delivered into local target queues per second. This includes all messages from remote endpoints and messages from local endpoints which go through the transport.11609Total number of messages from local endpoints that are successfully delivered directly into local target queues.11611The number of priority 1 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11613The number of Service Broker related transactions that have rolled back.11615The number of priority 9 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11617The number of forwarded message bytes that have not been successfully sent yet.11619Total number of forwarded messages successfully sent.11621The number of priority 6 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11623The number of messages from local endpoints that are successfully delivered directly into local target queues per second.11625The number of forwarded messages successfully sent per second.11627The number of forwarded messages that were discarded per second due to forwarded message memory limits, age limits, etc.11629The number of priority 5 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11631Total number of messages from the transport that are successfully delivered into local target queues. This includes all messages from remote endpoints and messages from local endpoints which go through the transport.11633Total number of forwarded message bytes successfully sent.11635The number of priority 2 messages from local endpoints and the transport that are successfully delivered into local target queues per second.11637Service Broker/Database Mirroring Transport Statistics11639The average byte size of message fragments received in transport receive I/O operations.11641The current number of message fragments associated with current transport send I/O operations that haven't completed.11643UCS send flow control enters per sec.11645The number of message fragments sent per second in transport send I/O operations.11647The number of transport send I/Os per second. Note that a transport send I/O may contain more than one message fragment.11649The number of transport receive I/O bytes per second.11651The number of priority 6 message fragments sent per second in transport send I/O operations.11653The number of transport decrypted I/O bytes per second.11655The number of priority 7 message fragments sent per second in transport send I/O operations.11657The average byte length of transport send I/O operations.11659The number of priority 5 message fragments sent per second in transport send I/O operations.11661The average byte size of message fragments sent in transport send I/O operations.11663The total number of transport connections currently open.11665The number of transport send I/O bytes per second.11667The number of priority 4 message fragments sent per second in transport send I/O operations.11669UCS send flow control exits per sec.11671The number of times when transport receive I/O operations had to move buffer fragments in memory.11673The average byte length of transport receive I/O operations.11675Base for the average byte length of transport send I/O operations.11677The number of transport encrypted I/O bytes per second.11679Base for the average byte size of message fragments sent in transport send I/O operations.11681UCS receive flow control enters per sec.11683Base for the average byte length of transport receive I/O operations.11685The number of priority 1 message fragments sent per second in transport send I/O operations.11687The number of priority 2 message fragments sent per second in transport send I/O operations.11689The number of bytes associated with in completed transport receive I/O operations whose message fragments haven't been enqueued (or rejected) yet.11691Base for the average byte size of message fragments received in transport receive I/O operations.11693The number of message fragments received per second in transport receive I/O operations.11695The number of priority 3 message fragments sent per second in transport send I/O operations.11697The number of priority 9 message fragments sent per second in transport send I/O operations.11699The number of buffer bytes associated with current transport send I/O operations that haven't completed.11701The current number of message fragments received in transport receive I/O operations that have not been enqueued (or rejected) yet.11703The number of priority 8 message fragments sent per second in transport send I/O operations.11705The number of transport receives I/O per second. Note that a transport receive I/O may contain more than one message fragment.11707The number of priority 10 message fragments sent per second in transport send I/O operations.11709UCS send boxcars pending on flow control gate exit.11711The number of buffer bytes associated with message fragments being marshalled, or marshalled and ready to be sent with send I/O operations.11713The number of transport encrypted I/Os per second. Note that a transport send I/O may contain more than one message fragment.11715The rate at which transport receive I/O operations had to move buffer fragments in memory.11717The current number of message fragments that are being marshalled, or marshalled and ready to be sent via the transport layer.11719UCS receive messages pending on flow control gate exit.11721UCS receive flow control exits per sec.11723The number of bytes associated with current transport receive I/O operations that haven't completed.11725The number of transport decrypted I/Os per second. Note that a transport received I/O may contain more than one message fragment.11727Service Broker Activation11729The number of times the activated task limit on a queue has been reached per second.11731The total number of times the activated task limit on a queue has been reached.11733The total number of activated tasks that are currently running.11735The number of stored procedures that are being invoked per second.11737The number of activated tasks that are being aborted per second.11739The number of activated tasks that are being started per second.11741Service Broker Transmission Object Statistics11743The number of Transmission Objects saved per second.11745Average Number of Transmission Objects saved in a batch.11747Average time to save a Transmission Object batch.11749Average time between Transmission Object batch flushes.11751Average time between Transmission Object batch flushes.11753Average Number of Transmission Objects saved in a batch.11755The number of Transmission Objects marked dirty per second.11757The number of Transmission Objects requested per second.11759Average time to save a Transmission Object batch.11761Wait Statistics11763Statistics relevant to processes synchronizing access to workspace.11765Statistics relevant to non-page latches.11767Statistics relevant to page latches, not including IO latches11769Statistics for processes waiting on thread-safe memory allocators.11771Statistics relevant to page IO latches.11773Statistics relevant to processes waiting for worker to become available.11775Statistics for processes waiting for log buffer to be written.11777Statistics relevant to processes synchronizing access to transaction.11779Statistics for processes waiting on a lock.11781Statistics relevant to wait on network IO.11783Statistics for processes waiting for memory grant to become available.11785Statistics for processes waiting for log buffer to be available.11787Execution statistics for external calls11789Statistics relevant to execution of OLEDB calls.11791Statistics relevant to execution of distributed queries.11793Statistics relevant to execution of DTC calls.11795Statistics relevant to execution of XP calls.11797CLR Execution in SQL Server11799Total Execution time in CLR ( microseconds ).11801This defines a catalog metadata manager object for SQL Server11803Number of entries in the catalog metadata cache11805Ratio between catalog metadata cache hits and lookups11807Base for prior entry11809Number of catalog metadata cache entries that are pinned11811This defines the counters for CloudDB messaging11813The number of messages received per second.11815The number of bytes sent per second.11817The number of messages sent per second.11819The number of bytes received per second.11821This defines the counters for CloudDB replication11823Number of currently active partition delete scans11825The combined size of all the queues on this node.11827Number of currently pending partition copy scans11829Number of currently active partition copy scans11831Number of currently pending partition delete scans11833Number of currently active partition catchup log scans11835The number of transactions committed per second on the secondary.11837The number of transactions committed per second on the primary.11839Statistics for traces11841Events dropped by this trace per second11843Bytes transferred by this trace per second11845Events fired by this trace per second11847Events filtered per second11849Statistics for separate SQL Trace events11851Filtered events per second11853Prefiltered events per second11855CPU usage per second (Requires -T1904)11857Bytes transferred per second11859Events fired per second11861Statistics on deprecated feature usage11863Feature usage since last SQL Server startup11865Statistics associated with workload groups11867System CPU delayed for all requests in the specified instance of the performance object as a percentage of the total time active.11869Number of requests waiting in the queue due to resource governor limits in the workload group.11871Average time, in milliseconds, of a read of data from the disk11873Number of completed requests per second in the workload group.11875Number of IO operations not completed according to reserved capacity11877Number of bytes read from the disk in last second11879System CPU usage by all requests in the specified instance of the performance object as a percentage of the total time active.11881Average time, in milliseconds, of a write of data to the disk11883Number of suboptimal query plans generated per second in the workload group.11885Maximum value of memory grant in kilobytes used by a query in the workload group.11887System CPU usage by all requests in the specified instance of the performance object as a percentage of the total time active.11889System CPU usage by all requests in the specified instance of the performance object.11891Average time, in milliseconds, of a read of data from the disk11893Number of threads used by parallel queries in the workload group. Serial queries and the main thread of parallel queries are not included in this number.11895Average time, in milliseconds, of a write of data to the disk11897Number of bytes written to the disk in last second11899Number of read operations from the disk in last second11901Number of currently running requests in the workload group.11903Number of query optimizations per second occurring in the workload group.11905The difference between the CPU reservation and the effective scheduling percentage.11907System CPU usage by all requests in the specified instance of the performance object as a percentage of the total time active.11909System CPU usage by all requests in the specified instance of the performance object.11911Number of queries per second getting less than ideal amount of memory in the workload group.11913Number of write operations to the disk in last second11915Number of blocked tasks in the workload group.11917Maximum CPU time in milliseconds used by a request in the workload group.11919Statistics associated with resource pools11921Maximum amount of memory in kilobytes the resource pool can have based on the settings and server state.11923Number of query memory grants per second occurring in the resource pool.11925Number of read operations throttled in the last second11927Total amount of granted memory in kilobytes in the resource pool.11929Number of bytes written to the disk in the last second11931Effect of the resource governor on the resource pool calculated as (CPU usage %) / (CPU usage % without RG).11933Used amount of memory in kilobytes in the resource pool.11935Number of write operations issued to the disk in the last second11937Number of write operations to the disk in the last second11939Current memory target for cache memory in kilobytes.11941Number of queries waiting for memory grants in the resource pool.11943Current memory target for query compile in kilobytes.11945System CPU usage by all requests in the specified instance of the performance object.11947Number of bytes read from the disk in the last second11949System CPU usage by all requests in the specified instance of the performance object as a percentage of the total time active.11951Current memory target for query execution memory grant in kilobytes.11953Number of write operations throttled in the last second11955System CPU usage by all requests in the specified instance of the performance object.11957Target amount of memory in kilobytes the resource pool is trying to attain based on the settings and server state.11959Number of query memory grants in the resource pool.11961Target value of 'CPU usage %' for the resource pool based on the configuration settings and the system load.11963Average time, in milliseconds, of a write operation to the disk11965Average time, in milliseconds, of a read operation from the disk11967System CPU usage by all requests in the specified instance of the performance object as a percentage of the total time active.11969System CPU usage by all requests in the specified instance of the performance object as a percentage of the total time active.11971Number of read operations issued to the disk in the last second11973Average time, in milliseconds, of a read operation from the disk11975System CPU delayed for all requests in the specified instance of the performance object as a percentage of the total time active.11977Number of query memory grant timeouts per second occurring in the resource pool.11979The difference between the CPU reservation and the effective scheduling percentage.11981Number of read operations from the disk in the last second11983Average time, in milliseconds, of a write operation to the disk11985Statistics associated with Transaction Coordination Manager (TCM)11987The average time (in milliseconds) it takes to persist an AGE message11989The average time (in milliseconds) it takes to persist an AGE message11991Number of AGE responses received per second11993The average time (in milliseconds) for which an AGE broadcast waited to receive the responses from all agent bricks11995Number of transaction orders broadcast from TCM per second11997The average time (in milliseconds) for which an AGE broadcast waited to receive the responses from all agent bricks11999The average size of an AGE message broadcasted from TCM12001Total number of AGE broadcasts from TCM per second12003The average size of an AGE message broadcasted from TCM12005Statistics associated with the agents of Transaction Coordination Manager12007Total number of federated transactions started locally per second12009The number of bricks participating in a federated transaction per second12011Average time (in milliseconds) taken by a TCM Agent to process an AGE message12013Average transaction requests sent to TCM per AGE message12015Average time (in milliseconds) taken by a TCM Agent to process an AGE message12017Average number of transactions committed or aborted per AGE12019Average transaction requests sent to TCM per AGE message12021Average wait time (in milliseconds) for committing a transaction12023Average time (in milliseconds) it takes to prepare a federated transaction for commit12025Total number of federated transactions committed locally per second12027Number of federated transaction branches created per second12029Average wait time (in milliseconds) for committing a transaction12031Average number of transactions committed or aborted per AGE12033Total number of federated transactions rolled back locally per second12035Average time (in milliseconds) it takes to prepare a transaction for commit (BASE)12037Statistics associated with FileTable and non-transacted access12039Total number of FileTable enumeration requests per second.12041Average time (in milliseconds) spent handling an incoming file I/O request (BASE).12043Average time (in milliseconds) taken for a FileTable enumeration request.12045Average time (in milliseconds) spent handling an outgoing file I/O response (BASE).12047Average time (in milliseconds) taken to rename a FileTable item.12049Total number of outgoing file I/O responses per second.12051Average time (in milliseconds) taken to move a FileTable item.12053Total number of table operational events processed by the FileTable store component per second.12055Total number of FileTable handle kill operations per second.12057Total number of FileTable rename item requests per second.12059Average time (in milliseconds) taken to delete a FileTable item (BASE).12061Average time (in milliseconds) taken to kill a FileTable handle (BASE).12063Average time (in milliseconds) spent handling an incoming file I/O request.12065Average time (in milliseconds) spent handling an outgoing file I/O response.12067Average time (in milliseconds) taken for a FileTable enumeration request (BASE).12069Average time (in milliseconds) taken to update a FileTable item (BASE).12071Total number of FileTable retrieve item requests per second.12073Average time (in milliseconds) taken to retrieve a FileTable item.12075Total number of FileTable move item requests per second.12077Total number of incoming FileTable file I/O requests per second.12079Average time (in milliseconds) taken to move a FileTable item (BASE).12081Average time (in milliseconds) taken to kill a FileTable handle.12083Average time (in milliseconds) taken to retrieve a FileTable item (BASE).12085Total number of database operational events processed by the FileTable store component per second.12087Average time (in milliseconds) taken to update a FileTable item.12089Total number of FileTable delete item requests per second.12091Total number of FileTable update item requests per second.12093Average time (in milliseconds) taken to delete a FileTable item.12095Average time (in milliseconds) taken to rename a FileTable item (BASE).12097Counters to track SQL Batch Response times12099Number of SQL Batches having response time greater than or equal to 10ms but less than 20ms12101Number of SQL Batches having response time greater than or equal to 2ms but less than 5ms12103Number of SQL Batches having response time greater than or equal to 100,000ms12105Number of SQL Batches having response time greater than or equal to 50,000ms but less than 100,000ms12107Number of SQL Batches having response time greater than or equal to 5,000ms but less than 10,000ms12109Number of SQL Batches having response time greater than or equal to 500ms but less than 1,000ms12111Number of SQL Batches having response time greater than or equal to 0ms but less than 1ms12113Number of SQL Batches having response time greater than or equal to 1ms but less than 2ms12115Number of SQL Batches having response time greater than or equal to 50ms but less than 100ms12117Number of SQL Batches having response time greater than or equal to 5ms but less than 10ms12119Number of SQL Batches having response time greater than or equal to 20,000ms but less than 50,000ms12121Number of SQL Batches having response time greater than or equal to 100ms but less than 200ms12123Number of SQL Batches having response time greater than or equal to 2,000ms but less than 5,000ms12125Number of SQL Batches having response time greater than or equal to 10,000ms but less than 20,000ms12127Number of SQL Batches having response time greater than or equal to 200ms but less than 500ms12129Number of SQL Batches having response time greater than or equal to 20ms but less than 50ms12131Number of SQL Batches having response time greater than or equal to 1,000ms but less than 2,000ms12133Counters to track rate of partitions affected by soft throttling incidents12135Number of partitions affected by soft data read IO delay throttling12137Number of partitions affected by soft log write IO delay throttling12139Number of partitions affected by soft data space throttling12141Number of partitions affected by soft throttling due to busy workers threshold12143Number of partitions affected by soft log space throttling12145Counters to track rate of partitions affected by hard throttling incidents12147Number of partitions affected by hard log write IO delay throttling12149Number of partitions affected by hard log space throttling12151Number of partitions affected by hard data space throttling12153Number of partitions affected by hard data read IO delay throttling12155Number of partitions affected by hard throttling due to busy workers threshold12157Defines a HTTP storage object for SQL Server.12159The average number of microseconds it takes to do each read from the HTTP storage (BASE).12161Number of read and write operations per second on the HTTP storage.12163Average number of bytes transferred from the HTTP storage per write (BASE).12165Number of retry requests sent to the HTTP storage per second.12167Average number of bytes transferred from the HTTP storage per read.12169The average number of microseconds it takes to do each write to the HTTP storage (BASE).12171The average number of microseconds it takes for HTTP to complete the read to storage.12173Number of reads per second on the HTTP storage.12175The average number of microseconds it takes for HTTP to complete the write to storage.12177The average number of microseconds it takes to do each read from the HTTP storage.12179Average number of bytes transferred from the HTTP storage during read or write operations (BASE).12181Amount of data being transferred from the HTTP storage per second during read or write operations.12183The average number of microseconds it takes to do each transfer to the HTTP storage.12185Amount of data being transferred from the HTTP storage per second during read operations.12187The average number of microsecondsit takes to do each write to the HTTP storage.12189Amount of data being transferred from the HTTP storage per second during write operations.12191Number of failed write requests sent to the HTTP storage per second.12193Number of writer per second on the HTTP storage.12195The average number of microseconds it takes for HTTP to complete the write to storage (BASE).12197The average number of microseconds it takes for HTTP to complete the read to storage (BASE).12199Average number of bytes transferred from the HTTP storage per write."12201Average number of bytes transferred from the HTTP storage per read (BASE).12203The average number of microseconds it takes to do each transfer to the HTTP storage (BASE).12205The total number of outstanding I/Os towards a HTTP storage.12207Average number of bytes transferred from the HTTP storage during read or write operations.12209Defines a DB-scoped XEvent session object for SQL Server.12211Number of times per-db session limit was hit.12213Count of session start failures.12215Count of currently active sessions.12217Count of expired sessions.12219Count of dropped buffers.12221Number of times per-db node session limit was hit.12223Count of dropped events.12225This defines a Query Store object for SQL Server12227Number of physical read operations from Query Store.12229Number of logical write operations from Query Store.12231Number of physical read operations from Query Store.12233Execution time of Query Store operations expressed in hundredths of seconds.12235Describes statistics for columnstore indexes in SQL Server12237Number of delta rowgroups closed.12239Number of delta rowgroups compressed.12241Base for segment cache hit ratio calculations.12243Number of source rowgroups merged since the start of SQL Server.12245Number of delta rowgroups created.12247Total number of rowgroups compressed.12249Number of physical segment reads issued.12251Number of times tuple mover has cleaned up the delete buffer.12253Number of source rowgroups fit for MERGE since the start of SQL Server.12255Number of times the merge policy for columnstore was evaluated.12257Number of compressed target rowgroups created with MERGE since the start of SQL Server.12259Percentage of column segments that were found in the columnstore pool without having to incur a read from disk.12261Describes statistics for external script executions in SQL Server12263Number of external scripts executed with @input_data_1_partition_by_columns parameter12265Total time spent in executing external scripts12267Number of logins from satellite processes authenticated using implied authentication12269Number of external scripts executed using SQL Compute Context12271Number of external scripts executed12273Number of errors in executing external scripts12275Number of external scripts executed with @r_rowsPerRead parameter12277Number of external scripts executed with @parallel = 112279Describes statistics for advanced analytics12281Number of predictions performed using PREDICT function12283Describes statistics for advanced analytics12285Number of active Hadr threads used by AG13733The counters specific to the SMTP Server.13735The total number of bytes sent.13737The rate that bytes are sent.13739The total number of bytes received.13741The rate that bytes are received.13743The total number of bytes sent and received.13745The rate that bytes are sent and received.13747The total number of bytes sent in messages.13749The rate that bytes are sent in messages.13751The total number of bytes received in messages.13753The rate that bytes are received in messages.13755The total number of bytes sent and received in messages.13757The rate that bytes are sent and received in messages.13759The total number of inbound messages accepted.13761The rate that inbound messages are being received.13763The average number of recipients per inbound message received.13765Base Avg Recipients/msg Received (SHOULD BE HIDDEN)13767The percentage of recipients that will be delivered locally.13769Base % Recipients Local (SHOULD BE HIDDEN)13771The percentage of recipients that will be delivered remotely.13773Base % Recipients Remote (SHOULD BE HIDDEN)13775The total number of messages rejected because they were too big.13777The total number of messages refused due to no address objects.13779The total number of messages refused due to no mail objects.13781The total number of messages delivered to local mailboxes.13783The rate that messages are delivered to local mailboxes.13785The total number of local deliveries that were retried.13787The average number of retries per local delivery.13789Base Avg Retries/msg Delivered (SHOULD BE HIDDEN)13791The total number of messages retrieved from the mail pick-up directory.13793The rate that messages are being retrieved from the mail pick-up directory.13795The number of non-delivery reports that have been generated.13797The number of messages in the local queue.13799The number of messages in the local retry queue.13801Number of handles to open mail files.13803Number of handles to open queue files.13805The number of messages in the categorizer queue.13807The total number of outbound messages sent.13809The rate that outbound messages are being sent.13811The total number of outbound message sends that were retried.13813The average number of retries per outbound message sent.13815Base Avg Retries/msg Sent (SHOULD BE HIDDEN)13817The average number of recipients per outbound messages sent.13819Base Avg Recipients/msg Sent (SHOULD BE HIDDEN)13821The number of messages in the remote queue.13823The total number of DNS lookups.13825The rate of DNS lookups.13827The number of messages in the retry queue for remote delivery.13831The total number of inbound connections received.13833The total number of connections currently inbound.13835The total number of outbound connections attempted.13837The number of connections currently outbound.13839The number of outbound connection attempts refused by remote sites.13841The total number of connection errors.13843The number of connection errors per second.13845The total number of messages placed in a drop directory.13847The number of messages placed in a drop directory per second.13849The total number of routing table lookups.13851The number of routing table lookups per second.13853The total number of ETRN messages received by the server.13855The number of ETRN messages per second.13857The number of messages sent to badmail because they had no recipients.13859The number of messages sent to badmil becuase they had exceeded the maximum hop count.13861The number of messages sent to badmail for reasons not associated with a specific counter.13863The number of malformed pickup messages sent to badmail.13865The number of messages sent to badmail at the request of a server event sink.13867The number of Delivery Status Notifications sent to badmail becuase they could not be delivered.13869The number of messages that have been categorized but not routed.13871The number of messages that have been reported as currently undeliverable by routing.13873The total messages submitted to queuing for delivery.13875The total number of failed DSN generation attempts.13877The number of messages that are currently being processed by a server event sink for local delivery.13879The total number of messages submitted to the categorizer.13881The rate that messages are being submitted to the categorizer.13883The total number of messages submitted to categorizer that have finished categorization.13885The rate of categorizations completed.13887The number of categorizations in progress.13889The number of categorizations that completed without any errors.13891The number of categorizations that failed with a hard error (not retryable).13893The number of categorizations that failed with a retryable error.13895The number of categorizations that failed due to lack of available memory.13897The number of categorizations that failed due to a DS logon failure13899The number of categorizations that failed due to a DS connection failure13901The number of categorizations that failed with a generic retryable error13903The number of messages categorizer has submitted to queueing.13905The number of new messages created by the categorizer (bifurcation).13907The number of messages marked to be aborted by the categorizer.13909The number of mailmsg recipients submitted to categorizer.13911The number of mailmsg recipients submitted from categorizer to queueing.13913The number of recipients set to be NDRd by the categorizer.13915The number of unresolved recipients (local addresses not found).13917The number of recipients with addresses that match multiple DS objects.13919The number of recipients with illegal addresses detected by the categorizer.13921The number of recipients NDRd by the categorizer due to a forwarding loop detection.13923The number of recipients NDRd by the categorizer due to a generic recipient failure.13925The number of recipients the categorizer is currently processing.13927The number of senders not found in the DS.13929The number of senders with addresses that match multiple DS objects.13931The number of DS lookups for individual addresses13933The number of address lookups dispatched to the DS per second13935The number of address lookup completions processed13937The number of address lookup completions processed per second13939The number of address lookups that did not find any DS object13941The number of times a duplicate recipient address was detected by mailmsg/categorizer.13943The total number of LDAP connections opened13945The total number of failures encountered connection to LDAP servers13947The number of LDAP connections currently open13949The total number of successfull LDAP binds performed13951The total number of LDAP bind failures13953LDAP searches successfully dispatched13955LDAP searches successfully dispatched/sec13957LDAP paged searches successfully dispatched13959Number of failures to dispatch an async LDAP search13961Number of failures to dispatch an async paged LDAP search13963Number of LDAP search completions processed13965LDAP search completions processed/sec13967Number of paged LDAP completions processed13969Number of LDAP searches that completed with a failure13971Number of LDAP paged searches that completed with a failure13973Number of LDAP completions with a generic failure13975Number of LDAP searches abandoned13977Number of LDAP searches pending async completon13979This object represents global counters for the Exchange NTFS Store driver13981The current number of messages in the queue directory.13983The total number of messages allocated.13985The total number of messages deleted.13987The total number of messages enumerated during startup.13989The current number of open message bodies.13991The current number of open message streams.13993The Internet Information Services Global object includes counters that monitor Internet Information Services (the Web service and the FTP service) as a whole.13995Total requests allowed by bandwidth throttling settings (counted since service startup).13997Total requests temporarily blocked due to bandwidth throttling settings (counted since service startup).13999Total requests rejected due to bandwidth throttling settings (counted since service startup).14001Current requests temporarily blocked due to bandwidth throttling settings.14003Measured bandwidth of asynchronous I/O averaged over a minute.14005Current number of files whose content is in the cache for WWW and FTP services.14007Total number of files whose content was ever added to the cache for WWW and FTP services14009Total number of successful lookups in the file cache.14011Total number of unsuccessful lookups in the file cache.14013The ratio of File Cache Hits to total cache requests.14017File Cache Flushes since server startup.14019Current number of bytes used for file cache.14021Maximum number of bytes used for file cache.14023Active Flushed Entries are cached file handles that will be closed when all current transfers complete.14025Total Flushed Files is the number of file handles that have been removed from the cache since service start up.14027URI information blocks currently in the cache for WWW and FTP services.14029Total number of URI information blocks ever added to the cache for WWW and FTP services14031Total number of successful lookups in the URI cache.14033Total number of unsuccessful lookups in the URI cache.14035The ratio of URI Cache Hits to total cache requests.14039URI Cache Flushes since server startup.14041Total Flushed URIs is the number of URI information blocks that have been removed from the cache since service start up.14043BLOB information blocks currently in the cache for WWW and FTP services.14045Total number of BLOB information blocks ever added to the cache for WWW and FTP services14047Total number of successful lookups in the BLOB cache.14049Total number of unsuccessful lookups in the BLOB cache.14051The ratio of BLOB Cache Hits to total cache requests.14055BLOB Cache Flushes since server startup.14057Total Flushed BLOBs is the number of BLOB information blocks that have been removed from the cache since service start up.14935SQLAgent General Statistics about jobs14937Number of failed jobs.14939Number of successful jobs.14941Number of running jobs.14943Number of jobs queued.14945Number of jobs activated within the last minute.14947Base for successful jobs.14949Percentage of successful jobs from the total number of executed jobs.14951Statistics for job steps14953Number of queued steps.14955Number of active steps.14957The total number of times any Job Step execution is retried since the last SQL Server restart.14959SQLAgent statistics about alerts14961The number of Alerts that have activated since the last SQL Server restart.14963The number of Alerts that have activated within the last minute.14965SQLAgent general statistics14967The number of times the SQL Server has been successfully restarted by SQL Server Agent, since the last SQL Server Agent restart.14969SQLAgent General Statistics about system jobs14971Number of successful system jobs.14973Number of system jobs queued.14975Number of system jobs activated within the last minute.14977Number of failed system jobs.14979Number of running system jobs.14981Number of WMI High Performance provider returned by WMI Adapter14983Shows High Performance Classes14985Shows if High Performance Classes are valid14987iSCSI Connection Statistics14989Count of # of bytes received over this connection14991Count of # of bytes sent over this connection14993Count of # of  PDU sent over this connection14995Count of # of PDU received over this connection14997iSCSI Initiator Instance Statistics14999Count of Session connection timeout error15001Count of Session digest errors15003Number of Sessions failed belonging to this instance15005Count of Session format error15007iSCSI Initiator Login Statistics15009Count of Login Accept Responses15011Count of the number of times a login is aborted due to a target authentication failure15013Count of Login Authentication Failed Responses15015The object counts the number of times a login attempt from this local initiator has failed15017Count of the number of times login failed due to negotiation failure with target15019Count of Login other failed Responses15021Count of Login Redirect Responses15023Count of Logout command PDU with reason code 015025Count of Logout command PDUs with status code other than 015027iSCSI HBA main mode IPSEC Statistics15029The number of times that an acquire has failed.15031The number of entries in the acquire heap, which stores active acquires. This number increases under a heavy load and then gradually decreases over time, as the acquire heap is cleared.15033An acquire is a request by the IPSEC driver to have IKE perform a task. The active acquire statistic includes the outstanding request and the number of any queued requests. Typically, the number of active acquires is 1. Under a heavy load, the number of active acquires is 1 and the number of requests that are queued by IKE for processing.15035The number of IKE messages received that are queued for processing.15037The total number of identity authentication failures (Kerberos, certificate, and preshared key) that occurred during main mode negotiation.15039The number of quick mode state entries.15041The total number of requests submitted by IKE to obtain a unique Security Parameters Index (SPI) that failed.15043A cookie is a value contained in a received IKE message that is used by IKE to find the state of an active main mode. A cookie in a received IKE message that cannot be matched with an active main mode is invalid.15045The number of received IKE messages that are invalid, including IKE messages with invalid header fields, incorrect payload lengths, and incorrect values for the responder cookie (when it should be set to 0).15047The number of outbound quick mode security associations (SAs) submitted by IKE that failed15049The number of outbound quick mode security associations (SAs) added by IKE15051The number of inbound quick mode security associations (SAs) added by IKE15053The number of inbound quick mode security associations (SAs) added by IKE15055The total number of negotiation failures that occurred during main mode (also known as Phase I) or quick mode (also known as Phase II) negotiation.15057The total number of successful SAs created during main mode negotiations.15059The total number of successful SAs created during quick mode negotiations15061The number of times that the TCP stack has failed when receiving IKE messages.15063The number of entries in the IKE receive buffers for incoming IKE messages.15065The number of times that the TCP/IP stack has failed when sending IKE messages.15067The total number of negotiations that resulted in the use of plaintext (also known as soft SAs). This typically reflects the number of associations formed with computers that did not respond to main mode negotiation attempts. This can include both non-IPSEC-aware computers and IPSEC-aware computers that do not have IPSEC policy to negotiate security with this IPSEC peer.15069The total number of requests submitted by IKE to obtain a unique Security Parameters Index (SPI).15071This is an abstract base class for Hiperf provider15073Number of bytes received via ethernet port15075Number of bytes transmitted via ethernet port15077Number of PDU received via ethernet port15079Number of PDU transmitted via ethernet port15081iSCSI HBA quick mode IPSEC Statistics15083The number of active IPSEC SAs15085The number of active IPSEC tunnels.15087The number of bytes received using the AH protocol.15089The number of bytes sent using the AH protocol.15091The total number of packets for which the Security Parameters Index (SPI) was incorrect.15093The number of bytes received using the ESP protocol.15095The number of bytes sent using the ESP protocol.15097The total number of successful IPSEC SA negotiations15099The total number of key deletions for IPSEC SA15101The total number of packets for which data could not be verified.15103The total number of packets that failed decryption.15105The total number of packets that contained a valid Sequence Number field.15107The number of IPSEC key operations in progress15109The number of rekey operations for IPSEC SAs.15111The number of bytes received using the IPSEC protocol.15113The number of bytes sent using the IPSEC protocol.15115The number of bytes received using the IPSEC tunnel mode.15117The number of bytes sent using the IPSEC tunnel mode.15119iSCSI Request Processing Time15121Average time taken to process a request over this connection15123Maximum time taken to process a request over this connection15125iSCSI Session Statistics15127Number of bytes received over this session15129Number of bytes sent over this session15131Count of Number of ConnectionTimeout errors occured in this session15133Count of Number of Digest errors occured in this session15135Count of Number of Format errors occured in this session15137Number of PDU sent over this session15139Number of PDU received over this session15141Processor Performance Information15143Processor Frequency is the frequency of the current processor in megahertz. Some processors are capable of regulating their frequency outside of the control of Windows. Processor Frequency will not accurately reflect actual processor frequency on these systems. Use Processor Information\% Processor Performance instead.15145% of Maximum Frequency is the percentage of the current processor's maximum frequency. Some processors are capable of regulating their frequency outside of the control of Windows. % of Maximum Frequency will not accurately reflect actual processor frequency on these systems. Use Processor Information\% Processor Performance instead.15147Processor State Flags