Mini Kabibi Habibi

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 Marker6775Terminal Services per-session resource monitoring.6777Microsoft Distributed Transaction Coordinator performance counters6779Number of currently active transactions6781Number of committed transactions6783Number of aborted transactions6785Number of in doubt transactions6787Maximum number of transactions ever concurrently active6789Number of transactions committed by the system administrator6791Number of transactions aborted by the system administrator6793Minimum time delta between transaction begin and commit6795Average time delta between transaction begin and commit6797Maximum time delta between transaction begin and commit6799Transactions performed per second6801Transactions committed per second6803Transactions aborted per second6805MSDTC Bridge 4.0.0.0 performance counters6807The number of WS-AT protocol messages that the WS-AT service failed to send per second.6809The number of Prepare retry messages that the WS-AT service has sent per second.6811The number of Commit retry messages that the WS-AT service has sent per second.6813The number of Prepared retry messages that the WS-AT service has sent per second.6815The number of Replay retry messages that the WS-AT service has sent per second.6817The number of Fault messages that the WS-AT service has received per second.6819The number of Fault messages that the WS-AT service has sent per second.6821Average time in milliseconds for the WS-AT service to receive a Prepare message response from a participant.6823Base counter for the 'Average participant prepare response time' counter.6825Average time in milliseconds for the WS-AT service to receive a Commit message response from a participant.6827Base counter for the 'Average participant commit response time' counter.6829Help not available.6831The cumulative total number of socket connections established for this process since the process was started.6833The 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.6835The 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.6837The cumulative total number of datagram packets received since the process was started.6839The cumulative total number of datagram packets sent since the process was started.6841.Net CLR Data6843Current number of connections, pooled or not.6845Current number of connections in all pools associated with the process.6847Current number of pools associated with the process.6849The highest number of connections in all pools since the process started.6851The total number of connection open attempts that have failed for any reason.6853The total number of command executes that have failed for any reason.6855Counters for System.Data.SqlClient6857The number of actual connections per second that are being made to servers6859The number of actual disconnects per second that are being made to servers6861The number of connections we get from the pool per second6863The number of connections we return to the pool per second6865The number of connections that are not using connection pooling6867The number of connections that are managed by the connection pooler6869The number of unique connection strings6871The number of unique connection strings waiting for pruning6873The number of active connection pools6875The number of inactive connection pools6877The number of connections currently in-use6879The number of connections currently available for use6881The number of connections currently waiting to be made ready for use6883The number of connections we reclaim from GCed external connections6885System.Runtime.Caching.MemoryCache Performance Counters6887The number of cache hits.6889The number of cache misses.6891The percentage of cache hits in the total number of cache requests.6893Cache Hit Ratio Base6895Total number of entries removed from the cache due to memory pressure or Trim invocations.6897The number of entries within the cache.6899The number of entries added to the cache or removed from the cache per second.6901Counters for classes in the System.Net namespace.6903The cumulative total number of socket connections established for this process since the process was started.6905The 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.6907The 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.6909The cumulative total number of datagram packets received since the process was started.6911The cumulative total number of datagram packets sent since the process was started.6913The number of HttpWebRequest objects created during the last sample interval (typically 1 sec).6915The 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.6917HttpWebRequests Average Lifetime Base6919The 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.6921The 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.6923HttpWebRequests Average Queue Time Base6925The 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.6927The 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()6929Database provides performance statistics for each process using the ESE high performance embedded database management system.6931Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.6933Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.6935Defragmentation 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]6937Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]6939Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]6941Heap Allocs/sec is the number of memory allocations from the MP Heaps per second.  [Dev Only]6943Heap Frees/sec is the number of memory frees to the MP Heaps per second.  [Dev Only]6945Heap Allocations is the current number of memory allocations in the MP Heaps.  [Dev Only]6947Heap Bytes Allocated is the size of all memory allocations in the MP Heaps discounting heap managemnt overhead.  [Dev Only]6949Page Bytes Reserved is the size of all explicitly reserved virtual address space.  [Dev Only]6951Page Bytes Committed is the size of all explicitly committed virtual memory backing store (page file and physical memory).  [Dev Only]6953FCB 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]6955FCB 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]6957FCB Async Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]6959FCB Sync Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second.  [Dev Only]6961FCB 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]6963FCB 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]6965FCB 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]6967FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache.  No file operations were required.  [Dev Only]6969No text6971FCB 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]6973FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache.  [Dev Only]6975FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache.  [Dev Only]6977FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated.  [Dev Only]6979FCB Cache Allocated/sec is the number of cached schema records (FCBs) currently allocated per second.  [Dev Only]6981FCB 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]6983FCB Attached RCEs is the number of revision control entries (RCEs)  attached to cached schema records (FCBs) [Dev Only]6985Sessions In Use is the number of database sessions currently open for use by client threads.6987Sessions % Used is the percentage of database sessions currently open for use by client threads.6989No text6991Resource Manager FCB Allocated indicates the amount of memory in Bytes of allocated FCBs [Dev Only]6993Resource Manager FCB Allocated Used indicates the amount of memory in Bytes of allocated and used FCBs [Dev Only]6995Resource Manager FCB Quota indicates the maximum amount of memory in Bytes for FCBs [Dev Only]6997Resource Manager FUCB Allocated indicates the amount of memory in Bytes of allocated FUCBs [Dev Only]6999Resource Manager FUCB Allocated Used indicates the amount of memory in Bytes of allocated and used FUCBs [Dev Only]7001Resource Manager FUCB Quota indicates the maximum amount of memory in Bytes for FUCBs [Dev Only]7003Resource Manager TDB Allocated indicates the amount of memory in Bytes of allocated TDBs [Dev Only]7005Resource Manager TDB Allocated Used indicates the amount of memory in Bytes of allocated and used TDBs [Dev Only]7007Resource Manager TDB Quota indicates the maximum amount of memory in Bytes for TDBs [Dev Only]7009Resource Manager IDB Allocated indicates the amount of memory in Bytes of allocated IDBs [Dev Only]7011Resource Manager IDB Allocated Used indicates the amount of memory in Bytes of allocated and used IDBs [Dev Only]7013Resource Manager IDB Quota indicates the maximum amount of memory in Bytes for IDBs [Dev Only]7015Table 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.7017No text7019Table 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.7021Table 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.7023Table 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]7025Table 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]7027Table Opens/sec is the number of database tables opened per second.7029Table Closes/sec is the number of database tables closed per second.7031Tables Open is the number of database tables opened.7033Log Bytes Write per second is the rate bytes are written to the log.7035Log 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.7037Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs.  [Dev Only]7039Log Buffer Bytes Free is the amount of free space available in the log buffers.  [Dev Only]7041Log Buffer Bytes Committed is total number of committedbytes of log buffer.  [Dev Only]7043Log 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.7045Log 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]7047Log 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]7049Log 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]7051User 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]7053User 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]7055User 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]7057User 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]7059User Wait Last Transaction Commits/sec is the count of signals to flush a specific sessions pending transactions.  [Dev Only]7061User 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]7063User 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]7065User 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]7067User 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]7069System 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]7071System 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]7073System Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of internal transactions committed to log buffer.  [Dev Only]7075System 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]7077System 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]7079System 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]7081System Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that access data stored in the database engine.  [Dev Only]7083Recovery 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]7085Recovery 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]7087Recovery 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]7089Recovery 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]7091Recovery 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]7093Database Page Allocation File Extension Stalls/sec is the rate of attempts to extend the database file that stall.  [Dev Only]7095Log Records/sec is the count of records written to the database log buffers per second.  [Dev Only]7097Log Buffer Capacity Writes/sec is the count of times the database log buffers must be written per second because they are full.  [Dev Only]7099Log 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]7101Log 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]7103Log 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]7105Log 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.7107Log Full Segment Writes/sec is the number of times full log segments are written to the log file(s) per second. [Dev Only]7109Log 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]7111Log 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]7113Log 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.7115Version Buckets Allocated is the total number of version buckets allocated.7117Total number of version buckets allocated for FlagDelete RCEs  [Dev Only]7119VER 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]7121Average length of bookmark in RCE  [Dev Only]7123Number 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]7125Number of times per second a version store clean task is dispatched asynchronously to be performed  [Dev Only]7127Number of times per second a version store clean task is performed synchronously  [Dev Only]7129Number of times per second a version store clean task was discarded due to load concerns  [Dev Only]7131Number of times per second a dispatched version store cleanup task fails  [Dev Only]7133Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]7135Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]7137Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]7139Record 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]7141Record Redundant Replaces/sec is the rate at which records in database tables are being updated with the exact same content of the original record.  [Dev Only]7143Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]7145Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]7147Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]7149False 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]7151False 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]7153Record 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]7155Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]7157Record 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]7159Record 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]7161Record 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]7163Record 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]7165Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]7167Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]7169Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]7171Long-Value Maximum LID is the largest LID that has been used by the database engine.  [Dev Only]7173Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]7175Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]7177Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]7179Separated 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]7181Separated 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]7183Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]7185Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]7187Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]7189Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]7191B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]7193B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]7195B+ 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]7197B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]7199B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]7201B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]7203Right 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]7205B+ 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]7207B+ 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]7209B+ 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]7211B+ 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]7213B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]7215B+ 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]7217B+ 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]7219B+ 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]7221B+ 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]7223B+ 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]7225B+ 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]7227B+ 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]7229B+ 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]7231B+ 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]7233B+ 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]7235B+ 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]7237B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]7239B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]7241B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]7243B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]7245B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]7247Pages Trimmed/sec is the number of database pages that are trimmed and the allocated space is released to the file system.  [Dev Only]7249Pages 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]7251Database 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.7253Database 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.7255No text7257Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.7259No text7261Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.7263Database Cache Requests/sec is the rate that pages are requested from the database cache.7265Database Cache % Pinned is the percentage of the database cache that pinned in the memory.  [Dev Only]7267No text7269Database Cache % Clean is the percentage of the database cache that does not contain modified data.  [Dev Only]7271No text7273Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]7275Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]7277Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]7279Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]7281Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]7283Database Opportune Write Issued (Total) is the count of IO operationshas been issued for opportune write. [Dev Only]7285Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]7287Database 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]7289Database 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]7291Database 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]7293Database 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]7295Database 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]7297Database Pages Non-Resident Reclaimed (Hard Faulted)/sec is the number of (probably) hard fault operations per second. [Dev Only]7299Database 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]7301Database Page Latches/sec is the rate that database pages are latched for access to their data.  [Dev Only]7303Database 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]7305Database 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]7307Database 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]7309No text7311Database 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]7313Database 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]7315Database 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]7317Database 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]7319Database 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]7321No text7323Database 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.7325Database 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.7327Database 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]7329Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]7331Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]7333Database 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]7335Database 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]7337Database 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]7339Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]7341Database 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]7343Database 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.7345Database 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.7347Database 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.7349Database 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.7351Database 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.7353Database 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.7355Database 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.7357Database 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.7359Database 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.7361Database 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]7363Database 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]7365Database 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]7367Database 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]7369Database 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.7371Database 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.7373Database 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]7375Database 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]7377Database 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]7379No text7381Database 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]7383No text7385Database 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]7387Database 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]7389Database 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]7391Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]7393Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]7395Database 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]7397Database 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]7399Database 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]7401No text7403Database 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]7405Database 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]7407Database 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]7409Database 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]7411Database 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]7413Database 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]7415Database 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]7417Database 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]7419Database 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]7421Database 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]7423Database 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]7425Database 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]7427Database 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]7429Provides 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]7431Provides 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]7433Provides 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]7435Provides the delta (in ms) of "Database Cache Lifetime" and "Database Cache Lifetime (smooth)".  [Dev Only]7437Provides 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]7439Provides 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]7441Database Cache Scan Pages Evaluated/sec is the rate at which database pages are considered for eviction from the database page cache.  [Dev Only]7443Database 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]7445Database 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]7447No text7449Provides the number of entries returned by LRU-k.  [Dev Only]7451Provides the number of buckets required to evaluate by LRU-k to do the  last scan.  [Dev Only]7453Provides the number of buckets that were empty to evaluate LRU-k during the last scan.  [Dev Only]7455Provides the raw ID range from the approximate index covered during last scan.  [Dev Only]7457Provides the scan range in seconds evaluated from the LRU-k.  [Dev Only]7459Provides the delta (in ms) between the first found resource during scavenge scan and the last evicted resource.  [Dev Only]7461Provides the number of currently super colded resources.  It is not hundred percent accurate.  [Dev Only]7463Provides the rate at which the engine is attempting to mark pages super  cold, for immediate eviction.  [Dev Only]7465Provides the rate at which the engine has successfully marked pages super  cold, for immediate eviction.  [Dev Only]7467Database Page History Records is the current number of database page access history records retained for supporting the LRU-K page replacment algorithm.  [Dev Only]7469Database Page History % Hit is the percentage of database page access history record lookups that were successful.  [Dev Only]7471No text7473Database Cache % Resident is the percentage of the database cache that are currently in the process's working set.  [Dev Only]7475No text7477Database Cache % Dehydrated is the percentage of pages in the database  cache that are currently compressed.7479No text7481Database 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]7483Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups.  [Dev Only]7485Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]7487Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation.  [Dev Only]7489Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]7491Pages Freed/sec is the number of pages per second that are freed from the database by the online defragmentation process [Dev Only]7493Data 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]7495Online 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]7497Online Defrag Log Bytes/sec is the rate at which online defragmentation is generating log bytes.  [Dev Only]7499Database Maintenance Duration is the number of hours that have passed since maintenance last completed for this database.7501Database Maintenance Pages Read is the number of pages read by database maintenance. [Dev Only]7503Database Maintenance Pages Read/sec is the rate at which pages are read by database maintenance. [Dev Only]7505Database Maintenance Pages Zeroed is the number of pages zeroed/scrubbed by database maintenance. [Dev Only]7507Database Maintenance Pages Zeroed/sec is the rate at which pages are zeroed/scrubbed by database maintenance. [Dev Only]7509Database Maintenance Zero Ref Count LVs is the number of zero ref counted LVs deleted by database maintenance. [Dev Only]7511Database Maintenance Pages with Flag Deleted LVs Reclaimed  is the number of LV pages with flag deleted LVs reclaimed  by database maintenance. [Dev Only]7513Database Maintenance IO Reads/sec is the approximate number of Database Maintenance read IO operations generated/sec. [Dev Only]7515Database Maintenance IO Reads Average Bytes is the approximate average size in bytes of Database Maintenance read IO. [Dev Only]7517No text7519Database 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]7521Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]7523Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]7525Database Tasks Pages Preread/sec is the rate at which database pages are read in anticipation of future use by background database tasks.  [Dev Only]7527Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]7529Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications.  [Dev Only]7531Database Tasks Log Records/sec is the rate at which background database tasks are generating log records.  [Dev Only]7533Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks.  [Dev Only]7535No text7537Database Tasks Log Bytes/sec is the rate at which background database tasks are generating log bytes.  [Dev Only]7539I/O Database Reads (Attached)/sec is the rate of database read operations completed.7541I/O Database Reads (Attached) Average Latency is the average length of time,  in milliseconds, per database read operation.7543No text7545I/O Database Reads (Attached) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]7547No text7549I/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]7551I/O Database Reads (Attached) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]7553I/O Database Reads (Recovery)/sec is the rate of database read operations completed.7555I/O Database Reads (Recovery) Average Latency is the average length of time,  in milliseconds, per database read operation.7557No text7559I/O Database Reads (Recovery) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]7561No text7563I/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]7565I/O Database Reads (Recovery) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]7567I/O Database Reads/sec is the rate of database read operations completed.7569I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.7571No text7573I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]7575No text7577I/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]7579I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]7581I/O Log Reads/sec is the rate of logfile read operations completed.7583I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation.7585No text7587I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation.  [Dev Only]7589No text7591I/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]7593I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion.  [Dev Only]7595I/O Database Writes (Attached)/sec is the rate of database write operations completed.7597I/O Database Writes (Attached) Average Latency is the average length of time,  in milliseconds, per database write operation.7599No text7601I/O Database Writes (Attached) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]7603No text7605I/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]7607I/O Database Writes (Attached) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]7609I/O Database Writes (Recovery)/sec is the rate of database write operations completed.7611I/O Database Writes (Recovery) Average Latency is the average length of time,  in milliseconds, per database write operation.7613No text7615I/O Database Writes (Recovery) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]7617No text7619I/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]7621I/O Database Writes (Recovery) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]7623I/O Database Writes/sec is the rate of database write operations completed.7625I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.7627No text7629I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]7631No text7633I/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]7635I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]7637I/O Flush Map Writes/sec is the rate of flush map write operations completed.7639I/O Flush Map Writes Average Latency is the average length of time,  in milliseconds, per flush map write operation.7641No text7643I/O Flush Map Writes Average Bytes is the average number of bytes transferred per flush map write operation.  [Dev Only]7645No text7647I/O Log Writes/sec is the rate of log file write operations completed.7649I/O Log Writes Average Latency is the average length of time, in milliseconds, per log file write operation.7651No text7653I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation.  [Dev Only]7655No text7657I/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]7659I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion.  [Dev Only]7661FlushFileBuffers ops/sec is the rate of FlushFileBuffers operations completed.  [Dev Only]7663FlushFileBuffers Average Latency is the average length of time, in milliseconds, per FlushFileBuffers operation.  [Dev Only]7665No text7667Threads 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]7669Threads 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]7671Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]7673Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]7675Encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]7677No text7679Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]7681Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]7683Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]7685No text7687Pages Reorganized (Other)/sec is the number of times per second a page was reorganized for some other / unknown reason.  [Dev Only]7689Pages 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]7691Pages 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]7693Pages Reorganized (Dehydrate Buffer)/sec is the number of times per second a page is reorganized to minimize our in-memory buffer usage.  [Dev Only]7695Program Marker is a generic marker that may be set by some clients to delimit program execution, usually for debugging or testing purposes. [Dev Only]7697Database 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.7699No text7701Database 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]7703Statistics for the ESE high performance embedded database management system by Table Class.7705Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]7707Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]7709Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]7711Record 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]7713Record Redundant Replaces/sec is the rate at which records in database tables are being updated with the exact same content of the original record.  [Dev Only]7715Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]7717Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]7719Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]7721False 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]7723False 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]7725Record 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]7727Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]7729Record 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]7731Record 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]7733Record 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]7735Record 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]7737Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]7739Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]7741Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]7743Long-Value Maximum LID is the largest LID that has been used by the database engine for this table class.  [Dev Only]7745Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]7747Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]7749Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]7751Separated 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]7753Separated 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]7755Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]7757Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]7759Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]7761Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]7763B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]7765B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]7767B+ 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]7769B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]7771B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]7773B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]7775Right 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]7777B+ 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]7779B+ 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]7781B+ 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]7783B+ 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]7785B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]7787B+ 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]7789B+ 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]7791B+ 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]7793B+ 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]7795B+ 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]7797B+ 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]7799B+ 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]7801B+ 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]7803B+ 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]7805B+ 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]7807B+ 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]7809B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]7811B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]7813B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]7815B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]7817B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]7819Database 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]7821Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]7823Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]7825Database 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]7827Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]7829Database 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]7831Database 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.7833Database 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.7835Database 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.7837Database 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.7839No text7841Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.7843No text7845Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.7847Database Cache Requests/sec is the rate that pages are requested from the database cache.7849Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]7851Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]7853Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]7855Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]7857Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]7859Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]7861Database 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]7863Database 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]7865Database 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]7867Database 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]7869Database 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]7871Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]7873Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]7875Database 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]7877Database 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]7879Database 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]7881Database 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]7883Database 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]7885Database 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]7887Database 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]7889Database 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]7891Database 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]7893Database 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]7895Database 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]7897Database 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]7899Database 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]7901Database 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]7903FCB 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]7905FCB 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]7907FCB Async Threshold Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]7909Table 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]7911Table 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]7913Database 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.7915No text7917Database 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]7919Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]7921Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]7923Encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]7925No text7927Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]7929Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]7931Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]7933No text7935Instances in this process7937Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.7939Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.7941Defragmentation 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]7943Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]7945Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]7947FCB 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]7949FCB 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]7951FCB Async Threshold Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]7953FCB Sync Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second.  [Dev Only]7955FCB 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]7957FCB 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]7959FCB 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]7961FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache.  No file operations were required.  [Dev Only]7963No text7965FCB 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]7967FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache.  [Dev Only]7969FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache.  [Dev Only]7971FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated.  [Dev Only]7973FCB Cache Allocated/sec is the number of cached schema records (FCBs) currently allocated per second.  [Dev Only]7975FCB 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]7977FCB Cache Allocations Failed is the number of schema records (FCBs) attempts that fail to allocate. [Dev Only]7979FCB Cache Allocation Average Latency (ms) is the average latency in allocating cached schema records (FCBs).  [Dev Only]7981No text7983FCB Attached RCEs is the number of revision control entries (RCEs)  attached to cached schema records (FCBs) [Dev Only]7985Sessions In Use is the number of database sessions currently open for use by client threads.7987Sessions % Used is the percentage of database sessions currently open for use by client threads.7989No text7991Table 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.7993No text7995Table 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.7997Table 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.7999Table 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]8001Table 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]8003Table Opens/sec is the number of database tables opened per second.8005Table Closes/sec is the number of database tables closed per second.8007Tables Open is the number of database tables opened.8009Log Bytes Write per second is the rate bytes are written to the log.8011Log 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.8013Log Buffer Size is the amount of memory, in bytes, allocated for the database log buffers.  [Dev Only]8015Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs.  [Dev Only]8017Log Buffer Bytes Free is the amount of free space available in the log buffers.  [Dev Only]8019Log Buffer Bytes Committed is total number of committedbytes of log buffer.  [Dev Only]8021Log 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.8023Log File Size is the size, in bytes, of the database log files.  [Dev Only]8025Log 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]8027Log 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.8029Log 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]8031Log 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]8033Log 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.8035Log 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.8037No text8039Log 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.8041Log 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.8043Log Files Generated represents the total number of log files generated by an instance since that instance was last initialized.8045Log 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.8047Log File Current Generation gives the generation number of the current log file of an instance.8049User 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]8051User 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]8053User 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]8055User 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]8057User Wait Last Transaction Commits/sec is the count of signals to flush a specific sessions pending transactions.  [Dev Only]8059User 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]8061User 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]8063User 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]8065User 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]8067System 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]8069System 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]8071System Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of internal transactions committed to log buffer.  [Dev Only]8073System 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]8075System 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]8077System 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]8079System Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that access data stored in the database engine.  [Dev Only]8081Recovery 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]8083Recovery 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]8085Recovery 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]8087Recovery 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]8089Recovery 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]8091Database 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]8093Log Records/sec is the count of records written to the database log buffers per second.  [Dev Only]8095Log Buffer Capacity Writes/sec is the count of times the database log buffers must be written per second because they are full.  [Dev Only]8097Log 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]8099Log 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]8101Log 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]8103Log 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.8105Log Full Segment Writes/sec is the number of times full log segments are written to the log file(s) per second.  [Dev Only]8107Log 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]8109Log 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]8111Log 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.8113Total number of version buckets allocated8115Total number of version buckets allocated for FlagDelete RCEs  [Dev Only]8117VER 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]8119Average length of bookmark in RCE  [Dev Only]8121Number 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]8123Number of times per second a version store clean task is dispatched asynchronously to be performed  [Dev Only]8125Number of times per second a version store clean task is performed synchronously  [Dev Only]8127Number of times per second a version store clean task was discarded due to load concerns  [Dev Only]8129Number of times per second a dispatched version store cleanup task fails  [Dev Only]8131Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]8133Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]8135Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]8137Record 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]8139Record Redundant Replaces/sec is the rate at which records in database tables are being updated with the exact same content of the original record.  [Dev Only]8141Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]8143Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]8145Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]8147False 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]8149False 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]8151Record 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]8153Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]8155Record 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]8157Record 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]8159Record 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]8161Record 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]8163Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]8165Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]8167Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]8169Long-Value Maximum LID is the largest LID that has been used by the database engine for this instance.  [Dev Only]8171Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]8173Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]8175Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]8177Separated 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]8179Separated 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]8181Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]8183Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]8185Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]8187Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]8189B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]8191B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]8193B+ 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]8195B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]8197B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]8199B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]8201Right 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]8203B+ 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]8205B+ 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]8207B+ 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]8209B+ 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]8211B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]8213B+ 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]8215B+ 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]8217B+ 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]8219B+ 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]8221B+ 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]8223B+ 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]8225B+ 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]8227B+ 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]8229B+ 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]8231B+ 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]8233B+ 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]8235B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]8237B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]8239B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]8241B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]8243B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]8245Pages Trimmed/sec is the number of database pages that are trimmed and the allocated space is released to the file system.  [Dev Only]8247Pages 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]8249Database 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]8251Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]8253Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]8255Database 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]8257Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]8259Database 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]8261Database 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.8263Database 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.8265Database 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.8267No text8269Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.8271No text8273Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.8275Database Cache Requests/sec is the rate that pages are requested from the database cache.8277Instance 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]8279Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]8281Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]8283Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]8285Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]8287Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]8289Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]8291Database 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]8293Database 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]8295Database 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]8297Database 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]8299Database 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]8301Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]8303Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]8305Database 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]8307Database 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]8309Database 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]8311Database 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]8313Database 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]8315Database 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]8317Database 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]8319Database 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]8321Database 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]8323Database 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]8325Database 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]8327Database 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]8329Database 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]8331Database 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]8333Flush Map % Dirty is the percentage of the flush map that has been modified and not persisted since the associated database was attached.  [Dev Only]8335No text8337Flush Map Pages Written Async/sec is the rate at which flush map pages are asynchronously written to the flush map file.  [Dev Only]8339Flush Map Pages Written Sync/sec is the rate at which flush map pages are synchronously written to the flush map file.  [Dev Only]8341Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups.8343Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]8345Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation.  [Dev Only]8347Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]8349Pages Freed/sec is the number of pages per second that are freed from the database by the online defragmentation process [Dev Only]8351Data 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]8353Online 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]8355Online Defrag Log Bytes/sec is the rate at which online defragmentation is generating log bytes.  [Dev Only]8357Database Maintenance Duration is the number of hours that have passed since maintenance last completed for this database.8359Database Maintenance Pages Read is the number of pages read by database maintenance. [Dev Only]8361Database Maintenance Pages Read/sec is the rate at which pages are read by database maintenance. [Dev Only]8363Database Maintenance Pages Zeroed is the number of pages zeroed/scrubbed by database maintenance. [Dev Only]8365Database Maintenance Pages Zeroed/sec is the rate at which pages are zeroed/scrubbed by database maintenance. [Dev Only]8367Database Maintenance Zero Ref Count LVs is the number of zero ref counted LVs deleted by database maintenance. [Dev Only]8369Database Maintenance Pages with Flag Deleted LVs Reclaimed  is the number of LV pages with flag deleted LVs reclaimed  by database maintenance. [Dev Only]8371Database Maintenance IO Reads/sec is the approximate number of Database Maintenance read IO operations generated/sec. [Dev Only]8373Database Maintenance IO Reads Average Bytes is the approximate average size in bytes of Database Maintenance read IO. [Dev Only]8375No text8377Database Maintenance Throttle Setting is the current Database Maintenance throttle setting. [Dev Only]8379Database 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]8381Database 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]8383Database 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]8385Database 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]8387Database 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]8389Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]8391Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]8393Database Tasks Pages Preread/sec is the rate at which database pages are read in anticipation of future use by background database tasks.  [Dev Only]8395Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]8397Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications.  [Dev Only]8399Database Tasks Log Records/sec is the rate at which background database tasks are generating log records.  [Dev Only]8401Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks.  [Dev Only]8403No text8405Database Tasks Log Bytes/sec is the rate at which background database tasks are generating log bytes.  [Dev Only]8407I/O Database Reads (Attached)/sec is the rate of database read operations completed.8409I/O Database Reads (Attached) Average Latency is the average length of time,  in milliseconds, per database read operation.8411No text8413I/O Database Reads (Attached) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]8415No text8417I/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]8419I/O Database Reads (Attached) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]8421I/O Database Reads (Recovery)/sec is the rate of database read operations completed.8423I/O Database Reads (Recovery) Average Latency is the average length of time,  in milliseconds, per database read operation.8425No text8427I/O Database Reads (Recovery) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]8429No text8431I/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]8433I/O Database Reads (Recovery) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]8435I/O Database Reads/sec is the rate of database read operations completed.8437I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.8439No text8441I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]8443No text8445I/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]8447I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]8449I/O Log Reads/sec is the rate of logfile read operations completed.8451I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation.8453No text8455I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation.  [Dev Only]8457No text8459I/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]8461I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion.  [Dev Only]8463I/O Database Writes (Attached)/sec is the rate of database write operations completed.8465I/O Database Writes (Attached) Average Latency is the average length of time,  in milliseconds, per database write operation.8467No text8469I/O Database Writes (Attached) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]8471No text8473I/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]8475I/O Database Writes (Attached) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]8477I/O Database Writes (Recovery)/sec is the rate of database write operations completed.8479I/O Database Writes (Recovery) Average Latency is the average length of time,  in milliseconds, per database write operation.8481No text8483I/O Database Writes (Recovery) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]8485No text8487I/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]8489I/O Database Writes (Recovery) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]8491I/O Database Writes/sec is the rate of database write operations completed.8493I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.8495No text8497I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]8499No text8501I/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]8503I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]8505I/O Flush Map Writes/sec is the rate of flush map write operations completed.8507I/O Flush Map Writes Average Latency is the average length of time,  in milliseconds, per flush map write operation.8509No text8511I/O Flush Map Writes Average Bytes is the average number of bytes transferred per flush map write operation.  [Dev Only]8513No text8515I/O Log Writes/sec is the rate of log file write operations completed.8517I/O Log Writes Average Latency is the average length of time, in milliseconds, per log file write operation.8519No text8521I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation.  [Dev Only]8523No text8525I/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]8527I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion.  [Dev Only]8529FlushFileBuffers ops/sec is the rate of FlushFileBuffers operations completed.  [Dev Only]8531FlushFileBuffers Average Latency is the average length of time, in milliseconds, per FlushFileBuffers operation.  [Dev Only]8533No text8535Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]8537Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]8539encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]8541No text8543Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]8545Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]8547Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]8549No text8551Compressed Bytes/sec is the number of bytes per second that were compressed during DML operations.  [Dev Only]8553Compression Ops/sec is the number of compression operations per second that were performed during DML operations.  [Dev Only]8555Average latency per compression operation in microseconds.  [Dev Only]8557No text8559Compression ratio calculated as: uncompressed size / compressed size.  [Dev Only]8561No text8563Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations.  [Dev Only]8565Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations.  [Dev Only]8567Average latency per decompression operation in microseconds.  [Dev Only]8569No text8571Cpu Xpress9 Compressed Bytes/sec is the number of bytes per second that were compressed during DML operations using Xpress9 on the system cpu.  [Dev Only]8573Cpu Xpress9 Compression Ops/sec is the number of compression operations per second that were performed during DML operations using Xpress9 on the system cpu.  [Dev Only]8575Cpu Xpress9 Average latency per compression operation in microseconds.  [Dev Only]8577No text8579Cpu Xpress9 Compression ratio calculated as: uncompressed size / compressed size.  [Dev Only]8581No text8583Cpu 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]8585Cpu 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]8587Cpu Xpress9 Average latency per decompression operation in microseconds.  [Dev Only]8589No text8591Fpga Xpress9 Compressed Bytes/sec is the number of bytes per second that were compressed during DML operations using Xpress9 on the Fpga.  [Dev Only]8593Fpga Xpress9 Compression Ops/sec is the number of compression operations per second that were performed during DML operations using Xpress9 on the Fpga.  [Dev Only]8595Fpga Xpress9 Average latency per compression operation in microseconds.  [Dev Only]8597No text8599Fpga Xpress9 Compression ratio calculated as: uncompressed size / compressed size.  [Dev Only]8601No text8603Fpga Xpress9 Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations using Xpress9 on the Fpga.  [Dev Only]8605Fpga Xpress9 Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations using Xpress9 on the Fpga.  [Dev Only]8607Fpga Xpress9 Average latency per decompression operation in microseconds.  [Dev Only]8609No text8611Pages Reorganized (Other)/sec is the number of times per second a page was reorganized for some other / unknown reason.  [Dev Only]8613Pages 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]8615Pages 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]8617Pages Reorganized (Dehydrate Buffer)/sec is the number of times per second a page is reorganized to minimize our in-memory buffer usage.  [Dev Only]8619Database 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.8621No text8623Database 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]8625Provides an estimate of the oldest running transaction by elapsed time in milliseconds.8627Databases attached to this process8629Database 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.8631I/O Database Reads/sec is the rate of database read operations completed.8633I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.8635No text8637I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]8639No text8641I/O Database Writes/sec is the rate of database write operations completed.8643I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.8645No text8647I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation. [Dev Only]8649No text8651I/O Database Reads (Transactional) Total IO is the number of IOs accumulated   for the database read operation latency counters. [Dev Only]8653I/O Database Reads (Transactional) Mean Latency is the average length of time,  in microseconds, per database read operation. [Dev Only]8655I/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]8657I/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]8659I/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]8661I/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]8663I/O Database Reads (Maintenance) Total IO is the number of IOs accumulated   for the database read operation latency counters. [Dev Only]8665I/O Database Reads (Maintenance) Mean Latency is the average length of time,  in microseconds, per database read operation. [Dev Only]8667I/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]8669I/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]8671I/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]8673I/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]8675I/O Database Writes (Transactional) Total IO is the number of IOs accumulated   for the database write operation latency counters. [Dev Only]8677I/O Database Writes (Transactional) Mean Latency is the average length of time,  in microseconds, per database write operation. [Dev Only]8679I/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]8681I/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]8683I/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]8685I/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]8687I/O Database Writes (Maintenance) Total IO is the number of IOs accumulated   for the database write operation latency counters. [Dev Only]8689I/O Database Writes (Maintenance) Mean Latency is the average length of time,  in microseconds, per database write operation. [Dev Only]8691I/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]8693I/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]8695I/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]8697I/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]8699I/O Database Meted Queue Depth is queued and pending IO operations awaiting an open async IO slot. [Dev Only]8701I/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]8703I/O Database Async Read Pending is the number of async read IO operations outstanding to the OS. [Dev Only]8705Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.8707No text8709Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.8711SMSvcHost 4.0.0.0 performance counters8713The total number of failures at the protocol layer of net.tcp.8715The total number of failures at the protocol layer of net.pipe.8717The total number of failures dispatching messages received over net.tcp.8719The total number of failures dispatching messages received over net.pipe.8721The total number of connections dispatched over net.tcp.8723The total number of connections dispatched over net.pipe.8725The total number of TCP connections accepted over net.tcp.8727The total number of named pipe connections accepted over net.pipe.8729The number of uri registrations currently active for net.tcp.8731The number of uri registrations currently active for net.pipe.8733The total number of uris that were succesfully registered for net.tcp.8735The total number of uris that were succesfully registered for net.pipe.8737The total number of uris that were succesfully unregistered for net.tcp.8739The total number of uris that were succesfully unregistered for net.pipe.8741Counters for CLR Garbage Collected heap.8743This 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.8745This 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.8747This 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.8749This 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.8751This 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.8753This 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.8755This 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.8757This 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.8759This counter displays the process ID of the CLR process instance being monitored. The value displayed will be 0 until after the first garbage collection.8761This 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.8763This 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.8765This 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.8767This 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.8769This 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.8771This 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.8773This 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.8775This 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.8777% 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.8779Not Displayed.8781This 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.8783This 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).8785This 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.)8787This 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.8789This 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.8791Statistics for CLR Class Loader.8793This counter displays the cumulative number of classes loaded in all Assemblies since the start of this application.8795Reserved for future use.8797Reserved for future use.8799This 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.8801This 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.8803This 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.)8805This 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.8807This 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.8809This counter displays the current number of classes loaded in all Assemblies.8811This 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.8813This 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.8815This 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.8817This 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.8819This 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.8821This 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.8823This 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.8825Stats for CLR Jit.8827This 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.8829This 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.8831This 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.8833This 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.8835This 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.8837This 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.8839Not Displayed.8841Stats for CLR interop.8843This 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.8845This 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.8847This 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.8849Reserved for future use.8851Reserved for future use.8853Stats for CLR Locks and Threads.8855This 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.8857Rate 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.8859This 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.8861This counter displays the total number of threads that waited to acquire some managed lock since the start of the application.8863This 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.8865This 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.8867This 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.8869This 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.8871This 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.8873This 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.8875Stats for CLR Security.8877This 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.8879Reserved for future use.8881This 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.8883This 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.8885Not Displayed.8887This 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.8889Stats for CLR Remoting.8891This 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.8893This 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.8895This 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.8897This 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.8899This 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.8901This 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.8903This 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.8905Runtime statistics on CLR exception handling.8907This 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.8909This 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.8911This 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.8913This 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.8915This 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.8917Counters for System.Data.OracleClient8919The number of actual connections per second that are being made to servers8921The number of actual disconnects per second that are being made to servers8923The number of connections we get from the pool per second8925The number of connections we return to the pool per second8927The number of connections that are not using connection pooling8929The number of connections that are managed by the connection pooler8931The number of unique connection strings8933The number of unique connection strings waiting for pruning8935The number of active connection pools8937The number of inactive connection pools8939The number of connections currently in-use8941The number of connections currently available for use8943The number of connections currently waiting to be made ready for use8945The number of connections we reclaim from GCed external connections8947The Telphony System8949The number of telephone lines serviced by this computer.8951The number of telephone devices serviced by this computer.8953the number of telephone lines serviced by this computer that are currently active.8955The number of telephone devices that are currently being monitored.8957The rate of outgoing calls made by this computer.8959The rate of incoming calls answered by this computer.8961The number of applications that are currently using telephony services.8963Current outgoing calls being serviced by this computer.8965Current incoming calls being serviced by this computer.8967BITS Per Job Network Utilization8969Estimate of Remote Server Speed (Bits/Sec)8971Estimate of the local netcard's speed (Bits/Sec)8973Estimate of most recent percent network interface utilization8975Estimate of the IGD's Internet connection speed (Bits/Sec)8977Estimate of most recent percent IGD Internet connection utilization8979Size of the next download block for BITS8981BITS download response interval (msec)8983Estimated bandwidth available to the remote system (Bits/sec)8985Displays performance statistics about ReadyBoost Caches.8987The total (uncompressed) amount of data currently stored in ReadyBoost caches.8989Amount of space in bytes taken by data cached in ReadyBoost caches.8991(Cache space used) / (Bytes cached)8993Total size, in bytes, of all caches regardless of how much data they contain.8995Number of I/Os satisfied from ReadyBoost caches per second.8997Bytes of I/Os satisfied from ReadyBoost caches per second.8999Number of read I/Os ignored by ReadyBoost due to policy.9001Bytes of read I/Os ignored by ReadyBoost due to policy.9003Number of read I/Os that are received by ReadyBoost. This counter includes all reads whether or not they were satisfied by ReadyBoost caches.9005Bytes of read I/Os that are received by ReadyBoost. This counter includes all reads whether or not they were satisfied by ReadyBoost caches.9007Displays the current bulk transfer rate in bytes/sec.9009Displays the current isochronous transfer rate in bytes/sec.9011Displays the current interrupt transfer rate in bytes/sec.9013Displays the current control transfer rate in bytes/sec.9015Displays the rate of PCI interrupt generation by the USB controller. For controller instances only.9017Displays the current rate Work Signals generated per second by the usbport driver.  For controller instances only.9019Displays the percentage of BW reserved for interrupt transfers9021Displays the percentage of BW reserved for ISO transfers9023USB I/O Counters9025Displays the average size of all transfer URBs. For device instances only.9027Number of ISO packets that are NOT late, but complete with an error. For device instances only.9029Avg number of ms between the current frame and the start frame of an ISO transfer when scheduled.  For device instances only.9031Number of Transfer URBs completing with an error status. For device instances only.9033Non-zero value if the host controller is not running(idle).9035Non-Zero value if the host controller async schedule is not running(idle).9037Incremented each time the controller async cache is flushed.9039Non-Zero if the periodic schedule is not running(idle).9041Incremented each time the controller periodic cache is flushed.9043Process Level Statistics for User Input Delay9045Session Level Statistics for User Input Delay9047Maximum value for queuing delay across all user input waiting to be picked-up by the process during a target time interval9049Maximum value for queuing delay across all user input waiting to be picked-up by any process in the session during a target time interval9051The RAS Object Type handles individual ports of the RAS device on your system.9053The number of bytes transmitted total for this connection.9055The number of bytes received total for this connection.9057The number of data frames transmitted total for this connection.9059The number of data frames received total for this connection.9061The compression ratio for bytes being transmitted.9063The compression ratio for bytes being received.9065The total number of CRC Errors for this connection.  CRC Errors occur when the frame received contains erroneous data.9067The total number of Timeout Errors for this connection.  Timeout Errors occur when an expected is not received in time.9069The 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.9071The total number of Alignment Errors for this connection.  Alignment Errors occur when a byte received is different from the byte expected.9073The total number of Buffer Overrun Errors for this connection.  Buffer Overrun Errors when the software cannot handle the rate at which data is received.9075The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.9077The number of bytes transmitted per second.9079The number of bytes received per second.9081The number of frames transmitted per second.9083The number of frames received per second.9085The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.9087The RAS Object Type handles all combined ports of the RAS device on your system.9089The total number of Remote Access connections.9091Windows Workflow Foundation Performance Counters9093Total number of workflows created.9095Rate of workflows created per second.9097Total number of workflows unloaded.9099Rate of workflows unloaded per second.9101Total number of workflows loaded.9103Rate of workflows loaded per second.9105Total number of workflows completed.9107Rate of workflows completed per second.9109Total number of workflows suspended.9111Rate of workflows suspended per second.9113Total number of workflows terminated.9115Rate of workflows terminated per second.9117Total number of workflows in memory.9119Total number of workflows aborted.9121Rate of workflows aborted per second.9123Total number of workflows persisted.9125Rate of workflows persisted per second.9127Total number of workflow instances actively executing.9129Rate of workflows becoming idle per second.9131Total number of workflows ready to execute.9133Total number of workflows waiting for a thread.9135Counters for the Windows Search Service Gatherer Project object9137The number of add notifications.9139The number of document additions per second.9141The number of delete notifications.9143The number of document deletes per second.9145The number of modify notifications.9147The number of modify notifications per second.9149The 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.9151The number of documents in progress.9153The number of documents on hold because a document with the same URL is currently in process.9155The number of documents delayed due to site hit frequency rules.9157The number of files (URLs) in the history list. This indicates the total size of your document corpus that was indexed.9159The number of documents processed since the history has been reset.9161The number of documents processed per second.9163The number of successfully filtered documents.9165The number of successfully filtered documents per second.9167The number of filtered documents which returned an error.9169The number of filtered documents which returned an error per second.9175The number of file protocol errors received while getting documents.9177The number of file protocol errors received per second.9183The number of documents accessed via file system.9185The number of documents accessed via file system per second.9191The number of office documents filtered.9193The number of office documents filtered per second.9195The number of text documents filtered.9197The number of text documents filtered per second.9199Number of crawls in progress.9201The Gatherer paused flag indicates if the Gatherer has been paused.9203The recovery in progress flag indicates if recovery is currently in progress. Indexing will not be resumed until this flag is off.9205The number of documents which were not filtered because no modification was detected since the last crawl.9207The Iterating history in progress flag indicates if the Gatherer is currently iterating over the URL history.9209Number of incremental crawls in progress.9211The number of documents currently being filtered.9213The 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.9215The total number of times a document access has been retried. Having this number high may indicate a problem with accessing the data.9217The number of retries per second.9225Documents incorrectly rejected by adaptive crawl9231Documents which have changed since the last crawl9233The number of Move/Rename notifications.9235The number of document Moves and Renames per second.9237Number of unique documents in the system. Documents are considered not unique if their contents is the same.9239Percentage of the history recovery completed9241Counters for the Windows Search Service Gathering service object9243Currently connected external notification sources.9245The total number of notifications received from all notification sources excluding file system.9247The rate of external notifications received per second.9249The number of currently connected administrative clients.9251The 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.9253Displays one heartbeat every 10 seconds.9255The total number of filtering threads in the system. This number is calculated based on your system resources.9257The number of threads waiting for documents.9259The number of document entries currently in memory. Zero means no indexing activity is going on.9261Indicates the level of the amount of system resources that the Gatherer service is allowed to use.9263The number of documents waiting for robot threads. If this number is not 0, all threads should be filtering.9265The number of filtering processes in the system.9267The maximum number of filtering processes that have existed in the system since startup.9269The 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.9271The number of documents delayed due to site hit frequency rules.9273The number of servers recently accessed by the system.9275The number of times a new server object had to be created.9277The number of filter objects in the system. Each filter object corresponds to a URL currently being filtered.9279The number of times a filter object was created. This corresponds to the total number of documents filtered in the system since startup.9281The number of documents filtered per second.9283The total number of timeouts detected by the system since startup.9285A server becomes unavailable when a number of requests to that server time out.9287A server becomes unavailable when a number of requests to that server time out.9289The 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.9291The number of threads waiting for plug-ins to complete an operation.9293The number of documents successfully filtered.9295The number of successfully filtered documents per second.9297The 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.9299Number of available cached word breakers instances9301Number of available cached stemmer instances. Too many may indicate a resource usage problem.9303The total number of notifications received from all notification sources including file system.9305The rate of external notifications received per second.9307System IO (disk) traffic rate in KB/s detected by back off logic9309The 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.9311The number of threads blocked due to back off event9313Indexer PlugIn statistics9315The level of the master index.9317Number of Master Merges to Date9319Master Merge Progress9321Shadow Merge Levels9323Shadow Merge Levels Threshold9325Number of Persistent Indexes9327Size of Index9329Number of Unique Keys9331Number of Documents Filtered9333Number of invalidator work items that were created9335Number of invalidator work items that were deleted9337Number of clean WidSets9339Number of dirty WidSets9341Indicator if a master merge is going on.9343Active Connections9345Number of Queries9347Number of Queries Failed9349Number of Queries Succeeded9351The number of L0 Indexes (Wordlists)9353The number of L0 merges (flushes) in progress at any one moment.9355The average value [documents/hour] computed for the speed of L0 merges (flushes) since the catalog has been loaded9357The number of L0 merges (flushes) since the catalog was loaded9359The last value [documents/hour] computed for the speed of L0 merges (flushes).9361The number of L1 Indexes9363The number of L1 merges in progress at any one moment.9365The average value [documents/hour] computed for the speed of L1 merges since the catalog has been loaded9367The number of L1 merges since the catalog was loaded9369The last value [documents/hour] computed for the speed of L1 merges.9371The number of L2 Indexes9373The number of L2 merges in progress at any one moment.9375The average value [documents/hour] computed for the speed of L2 merges since the catalog has been loaded9377The number of L2 merges since the catalog was loaded9379The last value [documents/hour] computed for the speed of L2 merges.9381The number of L3 Indexes9383The number of L3 merges in progress at any one moment.9385The average value [documents/hour] computed for the speed of L3 merges since the catalog has been loaded9387The number of L3 merges since the catalog was loaded9389The last value [documents/hour] computed for the speed of L3 merges.9391The number of L4 Indexes9393The number of L4 merges in progress at any one moment.9395The average value [documents/hour] computed for the speed of L4 merges since the catalog has been loaded9397The number of L4 merges since the catalog was loaded9399The last value [documents/hour] computed for the speed of L4 merges.9401The number of L5 Indexes9403The number of L5 merges in progress at any one moment.9405The average value [documents/hour] computed for the speed of L5 merges since the catalog has been loaded9407The number of L5 merges since the catalog was loaded9409The last value [documents/hour] computed for the speed of L5 merges.9411The number of L6 Indexes9413The number of L6 merges in progress at any one moment.9415The average value [documents/hour] computed for the speed of L6 merges since the catalog has been loaded9417The number of L6 merges since the catalog was loaded9419The last value [documents/hour] computed for the speed of L6 merges.9421The number of L7 Indexes9423The number of L7 merges in progress at any one moment.9425The average value [documents/hour] computed for the speed of L7 merges since the catalog has been loaded9427The number of L7 merges since the catalog was loaded9429The last value [documents/hour] computed for the speed of L7 merges.9431The number of L8 Indexes9433The number of L8 merges in progress at any one moment.9435The average value [documents/hour] computed for the speed of L8 merges since the catalog has been loaded9437The number of L8 merges since the catalog was loaded9439The last value [documents/hour] computed for the speed of L8 merges.9719ServiceModelOperation 3.0.0.0 performance counters9721The number of calls to this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.Calls.aspx9723The number of calls to this operation per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsPerSecond.aspx9725The number of calls to this operation that are in progress. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsOutstanding.aspx9727The number of calls with unhandled exceptions in this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFailed.aspx9729The number of calls with unhandled exceptions in this operation per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFailedPerSecond.aspx9731The number of calls to this operation that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFaulted.aspx9733The number of calls to this operation that returned faults per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFaultedPerSecond.aspx9735The average duration of calls to this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallDuration.aspx9737Base counter for the 'Calls Duration' counter.9739The number of transactions that flowed to this operation. This counter is incremented any time a transaction ID is present in the message sent to the operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.TxFlowed.aspx9741The number of transactions that flowed to this operation per second. This counter is incremented any time a transaction ID is present in the message sent to the operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.TxFlowedPerSecond.aspx9743The number of calls to this operation that failed validation or authentication. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityValidationAuthenticationFailures.aspx9745The number of calls to this operation that failed validation or authentication per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityValidationAuthenticationFailuresPerSecond.aspx9747The number of calls to this operation that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityCallsNotAuthorized.aspx9749The number of calls to this operation that failed authorization per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityCallsNotAuthorizedPerSecond.aspx9751ServiceModelService 3.0.0.0 performance counters9753The number of calls to this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.Calls.aspx9755The number of calls to this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsPerSecond.aspx9757The number of calls to this service that are in progress. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsOutstanding.aspx9759The number of calls with unhandled exceptions in this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFailed.aspx9761The number of calls with unhandled exceptions in this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFailedPerSecond.aspx9763The number of calls to this service that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFaulted.aspx9765The number of calls to this service that returned faults per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFaultedPerSecond.aspx9767The average duration of calls to this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallDuration.aspx9769Base counter for the 'Calls Duration' counter.9771The number of transactions that flowed to operations in this service. This counter is incremented any time a transaction ID is present in the message that is sent to the service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxFlowed.aspx9773The number of transactions that flowed to operations in this service per second. This counter is incremented any time a transaction ID is present in the message that is sent to the service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxFlowedPerSecond.aspx9775The number of transacted operations with the outcome committed in this service. Work done under such operations is fully committed. Resources are updated in accordance with the work done in the operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxCommitted.aspx9777The number of transacted operations with the outcome committed in this service per second. Work done under such operations is fully committed. Resources are updated in accordance with the work done in the operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxCommittedPerSecond.aspx9779The number of transacted operations with the outcome aborted in this service. Work done under such operations is rolled back. Resources are reverted to their previous state. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxAborted.aspx9781The number of transacted operations with the outcome aborted in this service per second. Work done under such operations is rolled back. Resources are reverted to their previous state. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxAbortedPerSecond.aspx9783The number of transacted operations with an outcome in doubt in this service. Work done with an outcome in doubt is in an indeterminate state. Resources are held pending outcome. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxInDoubt.aspx9785The number of transacted operations with an outcome in doubt in this service per second. Work done with an outcome in doubt is in an indeterminate state. Resources are held pending outcome. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxInDoubtPerSecond.aspx9787The number of calls to this service that failed validation or authentication. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityValidationAuthenticationFailures.aspx9789The number of calls to this service that failed validation or authentication per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityValidationAuthenticationFailuresPerSecond.aspx9791The number of calls to this service that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityCallsNotAuthorized.aspx9793The number of calls to this service that failed authorization per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityCallsNotAuthorizedPerSecond.aspx9795The total number of instances of the service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.Instances.aspx9797The creation rate of service instances per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.InstancesPerSecond.aspx9799The number of reliable messaging sessions that were faulted in this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.RMSessionsFaulted.aspx9801The number of reliable messaging sessions that were faulted in this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.RMSessionsFaultedPerSecond.aspx9803The number of reliable messaging messages that were dropped in this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.RMMessagesDropped.aspx9805The number of reliable messaging messages that were dropped in this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.RMMessagesDroppedPerSecond.aspx9807The number of messages to this service that were marked poisoned by the queued transport. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqPoisonMessages.aspx9809The number of messages to this service that were marked poisoned by the queued transport per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqPoisonMessagesPerSecond.aspx9811The number of messages to this servcie that were rejected by the queued transport. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqRejectedMessages.aspx9813The number of messages to this service that were rejected by the queued transport per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqRejectedMessagesPerSecond.aspx9815The number of messages to this service that were dropped by the queued transport. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqDroppedMessages.aspx9817The number of messages to this service that were dropped by the queued transport per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqDroppedMessagesPerSecond.aspx9819SMSvcHost 3.0.0.0 performance counters9821The total number of failures at the protocol layer of net.tcp.9823The total number of failures at the protocol layer of net.pipe.9825The total number of failures dispatching messages received over net.tcp.9827The total number of failures dispatching messages received over net.pipe.9829The total number of connections dispatched over net.tcp.9831The total number of connections dispatched over net.pipe.9833The total number of TCP connections accepted over net.tcp.9835The total number of named pipe connections accepted over net.pipe.9837The number of uri registrations currently active for net.tcp.9839The number of uri registrations currently active for net.pipe.9841The total number of uris that were succesfully registered for net.tcp.9843The total number of uris that were succesfully registered for net.pipe.9845The total number of uris that were succesfully unregistered for net.tcp.9847The total number of uris that were succesfully unregistered for net.pipe.9849Windows Workflow Foundation Performance Counters9851Total number of workflows created.9853Rate of workflows created per second.9855Total number of workflows unloaded.9857Rate of workflows unloaded per second.9859Total number of workflows loaded.9861Rate of workflows loaded per second.9863Total number of workflows completed.9865Rate of workflows completed per second.9867Total number of workflows suspended.9869Rate of workflows suspended per second.9871Total number of workflows terminated.9873Rate of workflows terminated per second.9875Total number of workflows in memory.9877Total number of workflows aborted.9879Rate of workflows aborted per second.9881Total number of workflows persisted.9883Rate of workflows persisted per second.9885Total number of workflow instances actively executing.9887Rate of workflows becoming idle per second.9889Total number of workflows ready to execute.9891Total number of workflows waiting for a thread.9893MSDTC Bridge 3.0.0.0 performance counters9895The number of WS-AT protocol messages that the WS-AT service failed to send per second.9897The number of Prepare retry messages that the WS-AT service has sent per second.9899The number of Commit retry messages that the WS-AT service has sent per second.9901The number of Prepared retry messages that the WS-AT service has sent per second.9903The number of Replay retry messages that the WS-AT service has sent per second.9905The number of Fault messages that the WS-AT service has received per second.9907The number of Fault messages that the WS-AT service has sent per second.9909Average time in milliseconds for the WS-AT service to receive a Prepare message response from a participant.9911Base counter for the 'Average participant prepare response time' counter.9913Average time in milliseconds for the WS-AT service to receive a Commit message response from a participant.9915Base counter for the 'Average participant commit response time' counter.9917ServiceModelEndpoint 3.0.0.0 performance counters9919The number of calls to this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.Calls.aspx9921The number of calls to this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsPerSecond.aspx9923The number of calls to this endpoint that are in progress. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsOutstanding.aspx9925The number of calls with unhandled exceptions at this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFailed.aspx9927The number of calls with unhandled exceptions at this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFailedPerSecond.aspx9929The number of calls to this endpoint that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFaulted.aspx9931The number of calls to this endpoint that returned faults per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFaultedPerSecond.aspx9933The average duration of calls to this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallDuration.aspx9935Base counter for the 'Calls Duration' counter.9937The number of transactions that flowed to operations at this endpoint. This counter is incremented any time a transaction ID is present in the message that is sent to the endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.TxFlowed.aspx9939The number of transactions that flowed to operations at this endpoint per second. This counter is incremented any time a transaction ID is present in the message that is sent to the endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.TxFlowedPerSecond.aspx9941The number of calls to this endpoint that failed validation or authentication. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityValidationAuthenticationFailures.aspx9943The number of calls to this endpoint that failed validation or authentication per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityValidationAuthenticationFailuresPerSecond.aspx9945The number of calls to this endpoint that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityCallsNotAuthorized.aspx9947The number of calls to this endpoint that failed authorization per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityCallsNotAuthorizedPerSecond.aspx9949The number of reliable messaging sessions that faulted at this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.RMSessionsFaulted.aspx9951The number of reliable messaging sessions that faulted at this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.RMSessionsFaultedPerSecond.aspx9953The number of reliable messaging messages that were dropped at this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.RMMessagesDropped.aspx9955The number of reliable messaging messages that were dropped at this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.RMMessagesDroppedPerSecond.aspx10395Number of WMI High Performance provider returned by WMI Adapter10397Shows High Performance Classes10399Shows if High Performance Classes are valid10401iSCSI Connection Statistics10403Count of # of bytes received over this connection10405Count of # of bytes sent over this connection10407Count of # of  PDU sent over this connection10409Count of # of PDU received over this connection10411iSCSI Initiator Instance Statistics10413Count of Session connection timeout error10415Count of Session digest errors10417Number of Sessions failed belonging to this instance10419Count of Session format error10421iSCSI Initiator Login Statistics10423Count of Login Accept Responses10425Count of the number of times a login is aborted due to a target authentication failure10427Count of Login Authentication Failed Responses10429The object counts the number of times a login attempt from this local initiator has failed10431Count of the number of times login failed due to negotiation failure with target10433Count of Login other failed Responses10435Count of Login Redirect Responses10437Count of Logout command PDU with reason code 010439Count of Logout command PDUs with status code other than 010441iSCSI HBA main mode IPSEC Statistics10443The number of times that an acquire has failed.10445The 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.10447An 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.10449The number of IKE messages received that are queued for processing.10451The total number of identity authentication failures (Kerberos, certificate, and preshared key) that occurred during main mode negotiation.10453The number of quick mode state entries.10455The total number of requests submitted by IKE to obtain a unique Security Parameters Index (SPI) that failed.10457A 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.10459The 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).10461The number of outbound quick mode security associations (SAs) submitted by IKE that failed10463The number of outbound quick mode security associations (SAs) added by IKE10465The number of inbound quick mode security associations (SAs) added by IKE10467The number of inbound quick mode security associations (SAs) added by IKE10469The total number of negotiation failures that occurred during main mode (also known as Phase I) or quick mode (also known as Phase II) negotiation.10471The total number of successful SAs created during main mode negotiations.10473The total number of successful SAs created during quick mode negotiations10475The number of times that the TCP stack has failed when receiving IKE messages.10477The number of entries in the IKE receive buffers for incoming IKE messages.10479The number of times that the TCP/IP stack has failed when sending IKE messages.10481The 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.10483The total number of requests submitted by IKE to obtain a unique Security Parameters Index (SPI).10485This is an abstract base class for Hiperf provider10487Number of bytes received via ethernet port10489Number of bytes transmitted via ethernet port10491Number of PDU received via ethernet port10493Number of PDU transmitted via ethernet port10495iSCSI HBA quick mode IPSEC Statistics10497The number of active IPSEC SAs10499The number of active IPSEC tunnels.10501The number of bytes received using the AH protocol.10503The number of bytes sent using the AH protocol.10505The total number of packets for which the Security Parameters Index (SPI) was incorrect.10507The number of bytes received using the ESP protocol.10509The number of bytes sent using the ESP protocol.10511The total number of successful IPSEC SA negotiations10513The total number of key deletions for IPSEC SA10515The total number of packets for which data could not be verified.10517The total number of packets that failed decryption.10519The total number of packets that contained a valid Sequence Number field.10521The number of IPSEC key operations in progress10523The number of rekey operations for IPSEC SAs.10525The number of bytes received using the IPSEC protocol.10527The number of bytes sent using the IPSEC protocol.10529The number of bytes received using the IPSEC tunnel mode.10531The number of bytes sent using the IPSEC tunnel mode.10533iSCSI Request Processing Time10535Average time taken to process a request over this connection10537Maximum time taken to process a request over this connection10539iSCSI Session Statistics10541Number of bytes received over this session10543Number of bytes sent over this session10545Count of Number of ConnectionTimeout errors occured in this session10547Count of Number of Digest errors occured in this session10549Count of Number of Format errors occured in this session10551Number of PDU sent over this session10553Number of PDU received over this session10555Processor Performance Information10557Processor 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.10559% 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.10561Processor State Flags