.

KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY
Server : Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12
System : Windows NT SERVER-PC 10.0 build 26200 (Windows 11) AMD64
User : ServerPC ( 0)
PHP Version : 8.2.12
Disable Function : NONE
Directory : 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.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.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.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.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.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.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).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.367The number of searches for files currently active in the server.  Indicates current server activity.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.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.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.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.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.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.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.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.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.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.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.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).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.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.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.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.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.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 Marker8357.Net CLR Data8359Current number of connections, pooled or not.8361Current number of connections in all pools associated with the process.8363Current number of pools associated with the process.8365The highest number of connections in all pools since the process started.8367The total number of connection open attempts that have failed for any reason.8369The total number of command executes that have failed for any reason.8371Counters for System.Data.SqlClient8373The number of actual connections per second that are being made to servers8375The number of actual disconnects per second that are being made to servers8377The number of connections we get from the pool per second8379The number of connections we return to the pool per second8381The number of connections that are not using connection pooling8383The number of connections that are managed by the connection pooler8385The number of unique connection strings8387The number of unique connection strings waiting for pruning8389The number of active connection pools8391The number of inactive connection pools8393The number of connections currently in-use8395The number of connections currently available for use8397The number of connections currently waiting to be made ready for use8399The number of connections we reclaim from GCed external connections8401Microsoft Distributed Transaction Coordinator performance counters8403Number of currently active transactions8405Number of committed transactions8407Number of aborted transactions8409Number of in doubt transactions8411Maximum number of transactions ever concurrently active8413Number of transactions committed by the system administrator8415Number of transactions aborted by the system administrator8417Minimum time delta between transaction begin and commit8419Average time delta between transaction begin and commit8421Maximum time delta between transaction begin and commit8423Transactions performed per second8425Transactions committed per second8427Transactions aborted per second8429Windows Workflow Foundation Performance Counters8431Total number of workflows created.8433Rate of workflows created per second.8435Total number of workflows unloaded.8437Rate of workflows unloaded per second.8439Total number of workflows loaded.8441Rate of workflows loaded per second.8443Total number of workflows completed.8445Rate of workflows completed per second.8447Total number of workflows suspended.8449Rate of workflows suspended per second.8451Total number of workflows terminated.8453Rate of workflows terminated per second.8455Total number of workflows in memory.8457Total number of workflows aborted.8459Rate of workflows aborted per second.8461Total number of workflows persisted.8463Rate of workflows persisted per second.8465Total number of workflow instances actively executing.8467Rate of workflows becoming idle per second.8469Total number of workflows ready to execute.8471Total number of workflows waiting for a thread.8473Help not available.8475The cumulative total number of socket connections established for this process since the process was started.8477The 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.8479The 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.8481The cumulative total number of datagram packets received since the process was started.8483The cumulative total number of datagram packets sent since the process was started.8485Displays the current bulk transfer rate in bytes/sec.8487Displays the current isochronous transfer rate in bytes/sec.8489Displays the current interrupt transfer rate in bytes/sec.8491Displays the current control transfer rate in bytes/sec.8493Displays the rate of PCI interrupt generation by the USB controller. For controller instances only.8495Displays the current rate Work Signals generated per second by the usbport driver.  For controller instances only.8497Displays the percentage of BW reserved for interrupt transfers8499Displays the percentage of BW reserved for ISO transfers8501USB I/O Counters8503Displays the average size of all transfer URBs. For device instances only.8505Number of ISO packets that are NOT late, but complete with an error. For device instances only.8507Avg number of ms between the current frame and the start frame of an ISO transfer when scheduled.  For device instances only.8509Number of Transfer URBs completing with an error status. For device instances only.8511Non-zero value if the host controller is not running(idle).8513Non-Zero value if the host controller async schedule is not running(idle).8515Incremented each time the controller async cache is flushed.8517Non-Zero if the periodic schedule is not running(idle).8519Incremented each time the controller periodic cache is flushed.8521System.Runtime.Caching.MemoryCache Performance Counters8523The number of cache hits.8525The number of cache misses.8527The percentage of cache hits in the total number of cache requests.8529Cache Hit Ratio Base8531Total number of entries removed from the cache due to memory pressure or Trim invocations.8533The number of entries within the cache.8535The number of entries added to the cache or removed from the cache per second.8537Counters for CLR Garbage Collected heap.8539This 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.8541This 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.8543This 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.8545This 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.8547This 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.8549This 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.8551This 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.8553This 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.8555This counter displays the process ID of the CLR process instance being monitored. The value displayed will be 0 until after the first garbage collection.8557This 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.8559This 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.8561This 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.8563This 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.8565This 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.8567This 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.8569This 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.8571This 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.8573% 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.8575Not Displayed.8577This 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.8579This 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).8581This 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.)8583This 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.8585This 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.8587Statistics for CLR Class Loader.8589This counter displays the cumulative number of classes loaded in all Assemblies since the start of this application.8591Reserved for future use.8593Reserved for future use.8595This 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.8597This 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.8599This 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.)8601This 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.8603This 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.8605This counter displays the current number of classes loaded in all Assemblies.8607This 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.8609This 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.8611This 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.8613This 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.8615This 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.8617This 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.8619This 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.8621Stats for CLR Jit.8623This 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.8625This 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.8627This 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.8629This 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.8631This 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.8633This 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.8635Not Displayed.8637Stats for CLR interop.8639This 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.8641This 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.8643This 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.8645Reserved for future use.8647Reserved for future use.8649Stats for CLR Locks and Threads.8651This 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.8653Rate 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.8655This 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.8657This counter displays the total number of threads that waited to acquire some managed lock since the start of the application.8659This 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.8661This 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.8663This 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.8665This 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.8667This 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.8669This 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.8671Stats for CLR Security.8673This 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.8675Reserved for future use.8677This 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.8679This 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.8681Not Displayed.8683This 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.8685Stats for CLR Remoting.8687This 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.8689This 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.8691This 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.8693This 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.8695This 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.8697This 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.8699This 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.8701Runtime statistics on CLR exception handling.8703This 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.8705This 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.8707This 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.8709This 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.8711This 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.8713Counters for System.Data.OracleClient8715The number of actual connections per second that are being made to servers8717The number of actual disconnects per second that are being made to servers8719The number of connections we get from the pool per second8721The number of connections we return to the pool per second8723The number of connections that are not using connection pooling8725The number of connections that are managed by the connection pooler8727The number of unique connection strings8729The number of unique connection strings waiting for pruning8731The number of active connection pools8733The number of inactive connection pools8735The number of connections currently in-use8737The number of connections currently available for use8739The number of connections currently waiting to be made ready for use8741The number of connections we reclaim from GCed external connections8743SMSvcHost 4.0.0.0 performance counters8745The total number of failures at the protocol layer of net.tcp.8747The total number of failures at the protocol layer of net.pipe.8749The total number of failures dispatching messages received over net.tcp.8751The total number of failures dispatching messages received over net.pipe.8753The total number of connections dispatched over net.tcp.8755The total number of connections dispatched over net.pipe.8757The total number of TCP connections accepted over net.tcp.8759The total number of named pipe connections accepted over net.pipe.8761The number of uri registrations currently active for net.tcp.8763The number of uri registrations currently active for net.pipe.8765The total number of uris that were succesfully registered for net.tcp.8767The total number of uris that were succesfully registered for net.pipe.8769The total number of uris that were succesfully unregistered for net.tcp.8771The total number of uris that were succesfully unregistered for net.pipe.8773Process Level Statistics for User Input Delay8775Session Level Statistics for User Input Delay8777Maximum value for queuing delay across all user input waiting to be picked-up by the process during a target time interval8779Maximum value for queuing delay across all user input waiting to be picked-up by any process in the session during a target time interval8781The RAS Object Type handles individual ports of the RAS device on your system.8783The number of bytes transmitted total for this connection.8785The number of bytes received total for this connection.8787The number of data frames transmitted total for this connection.8789The number of data frames received total for this connection.8791The compression ratio for bytes being transmitted.8793The compression ratio for bytes being received.8795The total number of CRC Errors for this connection.  CRC Errors occur when the frame received contains erroneous data.8797The total number of Timeout Errors for this connection.  Timeout Errors occur when an expected is not received in time.8799The 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.8801The total number of Alignment Errors for this connection.  Alignment Errors occur when a byte received is different from the byte expected.8803The total number of Buffer Overrun Errors for this connection.  Buffer Overrun Errors when the software cannot handle the rate at which data is received.8805The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.8807The number of bytes transmitted per second.8809The number of bytes received per second.8811The number of frames transmitted per second.8813The number of frames received per second.8815The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.8817The RAS Object Type handles all combined ports of the RAS device on your system.8819The total number of Remote Access connections.8821Counters for the Windows Search Service Gatherer Project object8823The number of add notifications.8825The number of document additions per second.8827The number of delete notifications.8829The number of document deletes per second.8831The number of modify notifications.8833The number of modify notifications per second.8835The 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.8837The number of documents in progress.8839The number of documents on hold because a document with the same URL is currently in process.8841The number of documents delayed due to site hit frequency rules.8843The number of files (URLs) in the history list. This indicates the total size of your document corpus that was indexed.8845The number of documents processed since the history has been reset.8847The number of documents processed per second.8849The number of successfully filtered documents.8851The number of successfully filtered documents per second.8853The number of filtered documents which returned an error.8855The number of filtered documents which returned an error per second.8861The number of file protocol errors received while getting documents.8863The number of file protocol errors received per second.8869The number of documents accessed via file system.8871The number of documents accessed via file system per second.8877The number of office documents filtered.8879The number of office documents filtered per second.8881The number of text documents filtered.8883The number of text documents filtered per second.8885Number of crawls in progress.8887The Gatherer paused flag indicates if the Gatherer has been paused.8889The recovery in progress flag indicates if recovery is currently in progress. Indexing will not be resumed until this flag is off.8891The number of documents which were not filtered because no modification was detected since the last crawl.8893The Iterating history in progress flag indicates if the Gatherer is currently iterating over the URL history.8895Number of incremental crawls in progress.8897The number of documents currently being filtered.8899The 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.8901The total number of times a document access has been retried. Having this number high may indicate a problem with accessing the data.8903The number of retries per second.8911Documents incorrectly rejected by adaptive crawl8917Documents which have changed since the last crawl8919The number of Move/Rename notifications.8921The number of document Moves and Renames per second.8923Number of unique documents in the system. Documents are considered not unique if their contents is the same.8925Percentage of the history recovery completed8927Counters for the Windows Search Service Gathering service object8929Currently connected external notification sources.8931The total number of notifications received from all notification sources excluding file system.8933The rate of external notifications received per second.8935The number of currently connected administrative clients.8937The 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.8939Displays one heartbeat every 10 seconds.8941The total number of filtering threads in the system. This number is calculated based on your system resources.8943The number of threads waiting for documents.8945The number of document entries currently in memory. Zero means no indexing activity is going on.8947Indicates the level of the amount of system resources that the Gatherer service is allowed to use.8949The number of documents waiting for robot threads. If this number is not 0, all threads should be filtering.8951The number of filtering processes in the system.8953The maximum number of filtering processes that have existed in the system since startup.8955The 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.8957The number of documents delayed due to site hit frequency rules.8959The number of servers recently accessed by the system.8961The number of times a new server object had to be created.8963The number of filter objects in the system. Each filter object corresponds to a URL currently being filtered.8965The number of times a filter object was created. This corresponds to the total number of documents filtered in the system since startup.8967The number of documents filtered per second.8969The total number of timeouts detected by the system since startup.8971A server becomes unavailable when a number of requests to that server time out.8973A server becomes unavailable when a number of requests to that server time out.8975The 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.8977The number of threads waiting for plug-ins to complete an operation.8979The number of documents successfully filtered.8981The number of successfully filtered documents per second.8983The 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.8985Number of available cached word breakers instances8987Number of available cached stemmer instances. Too many may indicate a resource usage problem.8989The total number of notifications received from all notification sources including file system.8991The rate of external notifications received per second.8993System IO (disk) traffic rate in KB/s detected by back off logic8995The 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.8997The number of threads blocked due to back off event8999Indexer PlugIn statistics9001The level of the master index.9003Number of Master Merges to Date9005Master Merge Progress9007Shadow Merge Levels9009Shadow Merge Levels Threshold9011Number of Persistent Indexes9013Size of Index9015Number of Unique Keys9017Number of Documents Filtered9019Number of invalidator work items that were created9021Number of invalidator work items that were deleted9023Number of clean WidSets9025Number of dirty WidSets9027Indicator if a master merge is going on.9029Active Connections9031Number of Queries9033Number of Queries Failed9035Number of Queries Succeeded9037The number of L0 Indexes (Wordlists)9039The number of L0 merges (flushes) in progress at any one moment.9041The average value [documents/hour] computed for the speed of L0 merges (flushes) since the catalog has been loaded9043The number of L0 merges (flushes) since the catalog was loaded9045The last value [documents/hour] computed for the speed of L0 merges (flushes).9047The number of L1 Indexes9049The number of L1 merges in progress at any one moment.9051The average value [documents/hour] computed for the speed of L1 merges since the catalog has been loaded9053The number of L1 merges since the catalog was loaded9055The last value [documents/hour] computed for the speed of L1 merges.9057The number of L2 Indexes9059The number of L2 merges in progress at any one moment.9061The average value [documents/hour] computed for the speed of L2 merges since the catalog has been loaded9063The number of L2 merges since the catalog was loaded9065The last value [documents/hour] computed for the speed of L2 merges.9067The number of L3 Indexes9069The number of L3 merges in progress at any one moment.9071The average value [documents/hour] computed for the speed of L3 merges since the catalog has been loaded9073The number of L3 merges since the catalog was loaded9075The last value [documents/hour] computed for the speed of L3 merges.9077The number of L4 Indexes9079The number of L4 merges in progress at any one moment.9081The average value [documents/hour] computed for the speed of L4 merges since the catalog has been loaded9083The number of L4 merges since the catalog was loaded9085The last value [documents/hour] computed for the speed of L4 merges.9087The number of L5 Indexes9089The number of L5 merges in progress at any one moment.9091The average value [documents/hour] computed for the speed of L5 merges since the catalog has been loaded9093The number of L5 merges since the catalog was loaded9095The last value [documents/hour] computed for the speed of L5 merges.9097The number of L6 Indexes9099The number of L6 merges in progress at any one moment.9101The average value [documents/hour] computed for the speed of L6 merges since the catalog has been loaded9103The number of L6 merges since the catalog was loaded9105The last value [documents/hour] computed for the speed of L6 merges.9107The number of L7 Indexes9109The number of L7 merges in progress at any one moment.9111The average value [documents/hour] computed for the speed of L7 merges since the catalog has been loaded9113The number of L7 merges since the catalog was loaded9115The last value [documents/hour] computed for the speed of L7 merges.9117The number of L8 Indexes9119The number of L8 merges in progress at any one moment.9121The average value [documents/hour] computed for the speed of L8 merges since the catalog has been loaded9123The number of L8 merges since the catalog was loaded9125The last value [documents/hour] computed for the speed of L8 merges.9127BITS Per Job Network Utilization9129Estimate of Remote Server Speed (Bits/Sec)9131Estimate of the local netcard's speed (Bits/Sec)9133Estimate of most recent percent network interface utilization9135Estimate of the IGD's Internet connection speed (Bits/Sec)9137Estimate of most recent percent IGD Internet connection utilization9139Size of the next download block for BITS9141BITS download response interval (msec)9143Estimated bandwidth available to the remote system (Bits/sec)9145The Telphony System9147The number of telephone lines serviced by this computer.9149The number of telephone devices serviced by this computer.9151the number of telephone lines serviced by this computer that are currently active.9153The number of telephone devices that are currently being monitored.9155The rate of outgoing calls made by this computer.9157The rate of incoming calls answered by this computer.9159The number of applications that are currently using telephony services.9161Current outgoing calls being serviced by this computer.9163Current incoming calls being serviced by this computer.9165Database provides performance statistics for each process using the ESE high performance embedded database management system.9167Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.9169Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.9171Defragmentation 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]9173Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]9175Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]9177Heap Allocs/sec is the number of memory allocations from the MP Heaps per second.  [Dev Only]9179Heap Frees/sec is the number of memory frees to the MP Heaps per second.  [Dev Only]9181Heap Allocations is the current number of memory allocations in the MP Heaps.  [Dev Only]9183Heap Bytes Allocated is the size of all memory allocations in the MP Heaps discounting heap managemnt overhead.  [Dev Only]9185Page Bytes Reserved is the size of all explicitly reserved virtual address space.  [Dev Only]9187Page Bytes Committed is the size of all explicitly committed virtual memory backing store (page file and physical memory).  [Dev Only]9189FCB 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]9191FCB 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]9193FCB Async Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]9195FCB Sync Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second.  [Dev Only]9197FCB 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]9199FCB 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]9201FCB 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]9203FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache.  No file operations were required.  [Dev Only]9205No text9207FCB 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]9209FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache.  [Dev Only]9211FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache.  [Dev Only]9213FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated.  [Dev Only]9215FCB Cache Allocated/sec is the number of cached schema records (FCBs) currently allocated per second.  [Dev Only]9217FCB 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]9219FCB Attached RCEs is the number of revision control entries (RCEs)  attached to cached schema records (FCBs) [Dev Only]9221Sessions In Use is the number of database sessions currently open for use by client threads.9223Sessions % Used is the percentage of database sessions currently open for use by client threads.9225No text9227Resource Manager FCB Allocated indicates the amount of memory in Bytes of allocated FCBs [Dev Only]9229Resource Manager FCB Allocated Used indicates the amount of memory in Bytes of allocated and used FCBs [Dev Only]9231Resource Manager FCB Quota indicates the maximum amount of memory in Bytes for FCBs [Dev Only]9233Resource Manager FUCB Allocated indicates the amount of memory in Bytes of allocated FUCBs [Dev Only]9235Resource Manager FUCB Allocated Used indicates the amount of memory in Bytes of allocated and used FUCBs [Dev Only]9237Resource Manager FUCB Quota indicates the maximum amount of memory in Bytes for FUCBs [Dev Only]9239Resource Manager TDB Allocated indicates the amount of memory in Bytes of allocated TDBs [Dev Only]9241Resource Manager TDB Allocated Used indicates the amount of memory in Bytes of allocated and used TDBs [Dev Only]9243Resource Manager TDB Quota indicates the maximum amount of memory in Bytes for TDBs [Dev Only]9245Resource Manager IDB Allocated indicates the amount of memory in Bytes of allocated IDBs [Dev Only]9247Resource Manager IDB Allocated Used indicates the amount of memory in Bytes of allocated and used IDBs [Dev Only]9249Resource Manager IDB Quota indicates the maximum amount of memory in Bytes for IDBs [Dev Only]9251Table 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.9253No text9255Table 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.9257Table 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.9259Table 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]9261Table 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]9263Table Opens/sec is the number of database tables opened per second.9265Table Closes/sec is the number of database tables closed per second.9267Tables Open is the number of database tables opened.9269Log Bytes Write per second is the rate bytes are written to the log.9271Log 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.9273Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs.  [Dev Only]9275Log Buffer Bytes Free is the amount of free space available in the log buffers.  [Dev Only]9277Log Buffer Bytes Committed is total number of committedbytes of log buffer.  [Dev Only]9279Log 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.9281Log 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]9283Log 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]9285Log 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]9287User 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]9289User 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]9291User 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]9293User 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]9295User Wait Last Transaction Commits/sec is the count of signals to flush a specific sessions pending transactions.  [Dev Only]9297User 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]9299User 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]9301User 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]9303User 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]9305System 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]9307System 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]9309System Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of internal transactions committed to log buffer.  [Dev Only]9311System 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]9313System 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]9315System 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]9317System Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that access data stored in the database engine.  [Dev Only]9319Recovery 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]9321Recovery 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]9323Recovery 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]9325Recovery 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]9327Recovery 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]9329Database Page Allocation File Extension Stalls/sec is the rate of attempts to extend the database file that stall.  [Dev Only]9331Log Records/sec is the count of records written to the database log buffers per second.  [Dev Only]9333Log Buffer Capacity Writes/sec is the count of times the database log buffers must be written per second because they are full.  [Dev Only]9335Log 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]9337Log 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]9339Log 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]9341Log 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.9343Log Full Segment Writes/sec is the number of times full log segments are written to the log file(s) per second. [Dev Only]9345Log 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]9347Log 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]9349Log 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.9351Version Buckets Allocated is the total number of version buckets allocated.9353Total number of version buckets allocated for FlagDelete RCEs  [Dev Only]9355VER 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]9357Average length of bookmark in RCE  [Dev Only]9359Number 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]9361Number of times per second a version store clean task is dispatched asynchronously to be performed  [Dev Only]9363Number of times per second a version store clean task is performed synchronously  [Dev Only]9365Number of times per second a version store clean task was discarded due to load concerns  [Dev Only]9367Number of times per second a dispatched version store cleanup task fails  [Dev Only]9369Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]9371Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]9373Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]9375Record 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]9377Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]9379Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]9381Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]9383False 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]9385False 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]9387Record 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]9389Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]9391Record 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]9393Record 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]9395Record 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]9397Record 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]9399Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]9401Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]9403Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]9405Long-Value Maximum LID is the largest LID that has been used by the database engine.  [Dev Only]9407Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]9409Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]9411Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]9413Separated 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]9415Separated 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]9417Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]9419Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]9421Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]9423Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]9425B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]9427B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]9429B+ 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]9431B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]9433B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]9435B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]9437Right 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]9439B+ 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]9441B+ 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]9443B+ 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]9445B+ 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]9447B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]9449B+ 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]9451B+ 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]9453B+ 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]9455B+ 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]9457B+ 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]9459B+ 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]9461B+ 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]9463B+ 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]9465B+ 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]9467B+ 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]9469B+ 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]9471B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]9473B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]9475B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]9477B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]9479B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]9481B+ Tree Upserts/sec is the count of times a record is upserted in to a database B+ Tree per second.  [Dev Only]9483BBT Evicts/sec is the count of times a BBT evicts nodes from the root page down the tree per second.  [Dev Only]9485BBT Root Evicted Bytes/sec is the number of bytes evicted from the BBT root page down the tree per second.  [Dev Only]9487BBT Evict Retries/sec is the count of times per secound, a BBT evict operation had to be retried because it couldn't meet eviction quota.  [Dev Only]9489BBT Leaf Evict Stalls/sec is the count of times per secound, a BBT leaf evict operation failed to evict any nodes to a leaf page, because of no free space on the page.  [Dev Only]9491Pages Trimmed/sec is the number of database pages that are trimmed and the allocated space is released to the file system.  [Dev Only]9493Pages 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]9495Database 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.9497Database 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.9499No text9501Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.9503No text9505Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.9507Database Cache Requests/sec is the rate that pages are requested from the database cache.9509Database Cache % Pinned is the percentage of the database cache that pinned in the memory.  [Dev Only]9511No text9513Database Cache % Clean is the percentage of the database cache that does not contain modified data.  [Dev Only]9515No text9517Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]9519Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]9521Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]9523Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]9525Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]9527Database Opportune Write Issued (Total) is the count of IO operationshas been issued for opportune write. [Dev Only]9529Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]9531Database 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]9533Database 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]9535Database 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]9537Database 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]9539Database 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]9541Database Pages Non-Resident Reclaimed (Hard Faulted)/sec is the number of (probably) hard fault operations per second. [Dev Only]9543Database 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]9545Database Page Latches/sec is the rate that database pages are latched for access to their data.  [Dev Only]9547Database 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]9549Database 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]9551Database 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]9553No text9555Database 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]9557Database 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]9559Database 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]9561Database 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]9563Database 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]9565No text9567Database 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.9569Database 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.9571Database 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]9573Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]9575Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]9577Database 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]9579Database 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]9581Database 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]9583Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]9585Database 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]9587Database 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.9589Database 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.9591Database 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.9593Database 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.9595Database 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.9597Database 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.9599Database 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.9601Database 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.9603Database 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.9605Database 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]9607Database 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]9609Database 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]9611Database 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]9613Database 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.9615Database 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.9617Database 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]9619Database 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]9621Database 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]9623No text9625Database 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]9627No text9629Database 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]9631Database 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]9633Database 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]9635Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]9637Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]9639Database 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]9641Database 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]9643Database 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]9645No text9647Database 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]9649Database 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]9651Database 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]9653Database 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]9655Database 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]9657Database 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]9659Database 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]9661Database 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]9663Database 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]9665Database 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]9667Database 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]9669Database 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]9671Database 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]9673Provides 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]9675Provides 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]9677Provides 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]9679Provides the delta (in ms) of "Database Cache Lifetime" and "Database Cache Lifetime (smooth)".  [Dev Only]9681Provides 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]9683Provides 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]9685Database Cache Scan Pages Evaluated/sec is the rate at which database pages are considered for eviction from the database page cache.  [Dev Only]9687Database 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]9689Database 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]9691Provides the number of entries returned by LRU-k.  [Dev Only]9693Provides the number of buckets required to evaluate by LRU-k to do the  last scan.  [Dev Only]9695Provides the number of buckets that were empty to evaluate LRU-k during the last scan.  [Dev Only]9697Provides the raw ID range from the approximate index covered during last scan.  [Dev Only]9699Provides the scan range in seconds evaluated from the LRU-k.  [Dev Only]9701Provides the delta (in ms) between the first found resource during scavenge scan and the last evicted resource.  [Dev Only]9703Provides the number of currently super colded resources.  It is not hundred percent accurate.  [Dev Only]9705Provides the rate at which the engine is attempting to mark pages super  cold, for immediate eviction.  [Dev Only]9707Provides the rate at which the engine has successfully marked pages super  cold, for immediate eviction.  [Dev Only]9709Database Page History Records is the current number of database page access history records retained for supporting the LRU-K page replacment algorithm.  [Dev Only]9711Database Page History % Hit is the percentage of database page access history record lookups that were successful.  [Dev Only]9713No text9715Database Cache % Resident is the percentage of the database cache that are currently in the process's working set.  [Dev Only]9717No text9719Database Cache % Dehydrated is the percentage of pages in the database  cache that are currently compressed.9721No text9723Database 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]9725Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups.  [Dev Only]9727Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]9729Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation.  [Dev Only]9731Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]9733Pages Freed/sec is the number of pages per second that are freed from the database by the online defragmentation process [Dev Only]9735Data 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]9737Online 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]9739Online Defrag Log Bytes/sec is the rate at which online defragmentation is generating log bytes.  [Dev Only]9741Database Maintenance Duration is the number of hours that have passed since maintenance last completed for this database.9743Database Maintenance Pages Read is the number of pages read by database maintenance. [Dev Only]9745Database Maintenance Pages Read/sec is the rate at which pages are read by database maintenance. [Dev Only]9747Database Maintenance Pages Zeroed is the number of pages zeroed/scrubbed by database maintenance. [Dev Only]9749Database Maintenance Pages Zeroed/sec is the rate at which pages are zeroed/scrubbed by database maintenance. [Dev Only]9751Database Maintenance Zero Ref Count LVs is the number of zero ref counted LVs deleted by database maintenance. [Dev Only]9753Database Maintenance Pages with Flag Deleted LVs Reclaimed  is the number of LV pages with flag deleted LVs reclaimed  by database maintenance. [Dev Only]9755Database Maintenance IO Reads/sec is the approximate number of Database Maintenance read IO operations generated/sec. [Dev Only]9757Database Maintenance IO Reads Average Bytes is the approximate average size in bytes of Database Maintenance read IO. [Dev Only]9759No text9761Database 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]9763Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]9765Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]9767Database Tasks Pages Preread/sec is the rate at which database pages are read in anticipation of future use by background database tasks.  [Dev Only]9769Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]9771Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications.  [Dev Only]9773Database Tasks Log Records/sec is the rate at which background database tasks are generating log records.  [Dev Only]9775Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks.  [Dev Only]9777No text9779Database Tasks Log Bytes/sec is the rate at which background database tasks are generating log bytes.  [Dev Only]9781I/O Database Reads (Attached)/sec is the rate of database read operations completed.9783I/O Database Reads (Attached) Average Latency is the average length of time,  in milliseconds, per database read operation.9785No text9787I/O Database Reads (Attached) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]9789No text9791I/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]9793I/O Database Reads (Attached) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]9795I/O Database Reads (Recovery)/sec is the rate of database read operations completed.9797I/O Database Reads (Recovery) Average Latency is the average length of time,  in milliseconds, per database read operation.9799No text9801I/O Database Reads (Recovery) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]9803No text9805I/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]9807I/O Database Reads (Recovery) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]9809I/O Database Reads/sec is the rate of database read operations completed.9811I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.9813No text9815I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]9817No text9819I/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]9821I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]9823I/O Log Reads/sec is the rate of logfile read operations completed.9825I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation.9827No text9829I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation.  [Dev Only]9831No text9833I/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]9835I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion.  [Dev Only]9837I/O Snapshot Reads/sec is the rate of snapshot read operations completed.  [Dev Only]9839I/O Snapshot Reads Average Latency is the average length of time, in milliseconds, per snapshot read operation.  [Dev Only]9841No text9843I/O Snapshot Reads Average Bytes is the average number of bytes transferred per snapshot read operation.  [Dev Only]9845No text9847I/O Snapshot Reads In Heap is the number of snapshot read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]9849I/O Snapshot Reads Async Pending is the number of snapshot read operations asynchronously pending completion.  [Dev Only]9851I/O Database Writes (Attached)/sec is the rate of database write operations completed.9853I/O Database Writes (Attached) Average Latency is the average length of time,  in milliseconds, per database write operation.9855No text9857I/O Database Writes (Attached) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]9859No text9861I/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]9863I/O Database Writes (Attached) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]9865I/O Database Writes (Recovery)/sec is the rate of database write operations completed.9867I/O Database Writes (Recovery) Average Latency is the average length of time,  in milliseconds, per database write operation.9869No text9871I/O Database Writes (Recovery) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]9873No text9875I/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]9877I/O Database Writes (Recovery) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]9879I/O Database Writes/sec is the rate of database write operations completed.9881I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.9883No text9885I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]9887No text9889I/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]9891I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]9893I/O Flush Map Writes/sec is the rate of flush map write operations completed.9895I/O Flush Map Writes Average Latency is the average length of time,  in milliseconds, per flush map write operation.9897No text9899I/O Flush Map Writes Average Bytes is the average number of bytes transferred per flush map write operation.  [Dev Only]9901No text9903I/O Log Writes/sec is the rate of log file write operations completed.9905I/O Log Writes Average Latency is the average length of time, in milliseconds, per log file write operation.9907No text9909I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation.  [Dev Only]9911No text9913I/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]9915I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion.  [Dev Only]9917I/O Snapshot Writes/sec is the rate of snapshot write operations completed.  [Dev Only]9919I/O Snapshot Writes Average Latency is the average length of time, in milliseconds, per snapshot write operation.  [Dev Only]9921No text9923I/O Snapshot Writes Average Bytes is the average number of bytes transferred per snapshot write operation.  [Dev Only]9925No text9927I/O Snapshot Writes In Heap is the number of snapshot write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]9929I/O Snapshot Writes Async Pending is the number of snapshot write operations asynchronously pending completion.  [Dev Only]9931FlushFileBuffers ops/sec is the rate of FlushFileBuffers operations completed.  [Dev Only]9933FlushFileBuffers Average Latency is the average length of time, in milliseconds, per FlushFileBuffers operation.  [Dev Only]9935No text9937Threads 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]9939Threads 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]9941Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]9943Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]9945Encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]9947No text9949Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]9951Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]9953Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]9955No text9957Pages Reorganized (Other)/sec is the number of times per second a page was reorganized for some other / unknown reason.  [Dev Only]9959Pages 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]9961Pages 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]9963Pages Reorganized (Dehydrate Buffer)/sec is the number of times per second a page is reorganized to minimize our in-memory buffer usage.  [Dev Only]9965Program Marker is a generic marker that may be set by some clients to delimit program execution, usually for debugging or testing purposes. [Dev Only]9967Database 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.9969No text9971Database 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]9973Revert Snapshot Stalls/sec is the number of times per second that collecting pre-image for a page for revert snapshot was stalled because of running out of snapshot buffers potentially stalling updates to the database.  [Dev Only]9975Statistics for the ESE high performance embedded database management system by Table Class.9977Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]9979Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]9981Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]9983Record 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]9985Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]9987Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]9989Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]9991False 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]9993False 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]9995Record 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]9997Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]9999Record 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]10001Record 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]10003Record 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]10005Record 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]10007Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]10009Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]10011Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]10013Long-Value Maximum LID is the largest LID that has been used by the database engine for this table class.  [Dev Only]10015Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]10017Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]10019Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]10021Separated 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]10023Separated 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]10025Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]10027Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]10029Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]10031Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]10033B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]10035B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]10037B+ 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]10039B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]10041B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]10043B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]10045Right 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]10047B+ 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]10049B+ 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]10051B+ 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]10053B+ 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]10055B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]10057B+ 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]10059B+ 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]10061B+ 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]10063B+ 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]10065B+ 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]10067B+ 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]10069B+ 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]10071B+ 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]10073B+ 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]10075B+ 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]10077B+ 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]10079B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]10081B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]10083B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]10085B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]10087B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]10089B+ Tree Upserts/sec is the count of times a record is upserted in to a database B+ Tree per second.  [Dev Only]10091BBT Evicts/sec is the count of times a BBT evicts nodes from the root page down the tree per second.  [Dev Only]10093BBT Root Evicted Bytes/sec is the number of bytes evicted from the BBT root page down the tree per second.  [Dev Only]10095BBT Evict Retries/sec is the count of times per secound, a BBT evict operation had to be retried because it couldn't meet eviction quota.  [Dev Only]10097BBT Leaf Evict Stalls/sec is the count of times per secound, a BBT leaf evict operation failed to evict any nodes to a leaf page, because of no free space on the page.  [Dev Only]10099Database 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]10101Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]10103Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]10105Database 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]10107Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]10109Database 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]10111Database 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.10113Database 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.10115Database 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.10117Database 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.10119No text10121Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.10123No text10125Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.10127Database Cache Requests/sec is the rate that pages are requested from the database cache.10129Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]10131Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]10133Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]10135Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]10137Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]10139Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]10141Database 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]10143Database 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]10145Database 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]10147Database 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]10149Database 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]10151Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]10153Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]10155Database 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]10157Database 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]10159Database 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]10161Database 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]10163Database 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]10165Database 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]10167Database 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]10169Database 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]10171Database 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]10173Database 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]10175Database 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]10177Database 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]10179Database 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]10181Database 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]10183FCB 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]10185FCB 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]10187FCB Async Threshold Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]10189Table 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]10191Table 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]10193Database 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.10195No text10197Database 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]10199Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]10201Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]10203Encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]10205No text10207Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]10209Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]10211Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]10213No text10215Instances in this process10217Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.10219Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.10221Defragmentation 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]10223Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]10225Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]10227FCB 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]10229FCB 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]10231FCB Async Threshold Purge Failures/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  [Dev Only]10233FCB Sync Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second.  [Dev Only]10235FCB 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]10237FCB 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]10239FCB 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]10241FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache.  No file operations were required.  [Dev Only]10243No text10245FCB 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]10247FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache.  [Dev Only]10249FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache.  [Dev Only]10251FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated.  [Dev Only]10253FCB Cache Allocated/sec is the number of cached schema records (FCBs) currently allocated per second.  [Dev Only]10255FCB 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]10257FCB Cache Allocations Failed is the number of schema records (FCBs) attempts that fail to allocate. [Dev Only]10259FCB Cache Allocation Average Latency (ms) is the average latency in allocating cached schema records (FCBs).  [Dev Only]10261No text10263FCB Attached RCEs is the number of revision control entries (RCEs)  attached to cached schema records (FCBs) [Dev Only]10265Sessions In Use is the number of database sessions currently open for use by client threads.10267Sessions % Used is the percentage of database sessions currently open for use by client threads.10269No text10271Table 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.10273No text10275Table 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.10277Table 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.10279Table 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]10281Table 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]10283Table Opens/sec is the number of database tables opened per second.10285Table Closes/sec is the number of database tables closed per second.10287Tables Open is the number of database tables opened.10289Log Bytes Write per second is the rate bytes are written to the log.10291Log 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.10293Log Buffer Size is the amount of memory, in bytes, allocated for the database log buffers.  [Dev Only]10295Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs.  [Dev Only]10297Log Buffer Bytes Free is the amount of free space available in the log buffers.  [Dev Only]10299Log Buffer Bytes Committed is total number of committedbytes of log buffer.  [Dev Only]10301Log 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.10303Log File Size is the size, in bytes, of the database log files.  [Dev Only]10305Log 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]10307Log 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.10309Log 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]10311Log 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]10313Log 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.10315Log 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.10317No text10319Log 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.10321Log 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.10323Log Files Generated represents the total number of log files generated by an instance since that instance was last initialized.10325Log 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.10327Log File Current Generation gives the generation number of the current log file of an instance.10329User 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]10331User 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]10333User 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]10335User 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]10337User Wait Last Transaction Commits/sec is the count of signals to flush a specific sessions pending transactions.  [Dev Only]10339User 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]10341User 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]10343User 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]10345User 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]10347System 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]10349System 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]10351System Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of internal transactions committed to log buffer.  [Dev Only]10353System 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]10355System 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]10357System 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]10359System Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that access data stored in the database engine.  [Dev Only]10361Recovery 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]10363Recovery 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]10365Recovery 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]10367Recovery 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]10369Recovery 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]10371Database 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]10373Log Records/sec is the count of records written to the database log buffers per second.  [Dev Only]10375Log Buffer Capacity Writes/sec is the count of times the database log buffers must be written per second because they are full.  [Dev Only]10377Log 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]10379Log 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]10381Log 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]10383Log 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.10385Log Full Segment Writes/sec is the number of times full log segments are written to the log file(s) per second.  [Dev Only]10387Log 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]10389Log 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]10391Log 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.10393Total number of version buckets allocated10395Total number of version buckets allocated for FlagDelete RCEs  [Dev Only]10397VER 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]10399Average length of bookmark in RCE  [Dev Only]10401Number 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]10403Number of times per second a version store clean task is dispatched asynchronously to be performed  [Dev Only]10405Number of times per second a version store clean task is performed synchronously  [Dev Only]10407Number of times per second a version store clean task was discarded due to load concerns  [Dev Only]10409Number of times per second a dispatched version store cleanup task fails  [Dev Only]10411Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]10413Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]10415Record Replaces/sec is the rate at which records in database tables are being updated.  [Dev Only]10417Record 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]10419Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]10421Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]10423Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]10425False 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]10427False 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]10429Record 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]10431Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]10433Record 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]10435Record 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]10437Record 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]10439Record 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]10441Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]10443Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]10445Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]10447Long-Value Maximum LID is the largest LID that has been used by the database engine for this instance.  [Dev Only]10449Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]10451Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]10453Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]10455Separated 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]10457Separated 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]10459Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]10461Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]10463Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]10465Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]10467B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]10469B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]10471B+ 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]10473B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]10475B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]10477B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]10479Right 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]10481B+ 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]10483B+ 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]10485B+ 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]10487B+ 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]10489B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]10491B+ 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]10493B+ 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]10495B+ 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]10497B+ 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]10499B+ 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]10501B+ 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]10503B+ 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]10505B+ 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]10507B+ 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]10509B+ 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]10511B+ 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]10513B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]10515B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]10517B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]10519B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]10521B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]10523B+ Tree Upserts/sec is the count of times a record is upserted in to a database B+ Tree per second.  [Dev Only]10525BBT Evicts/sec is the count of times a BBT evicts nodes from the root page down the tree per second.  [Dev Only]10527BBT Root Evicted Bytes/sec is the number of bytes evicted from the BBT root page down the tree per second.  [Dev Only]10529BBT Evict Retries/sec is the count of times per secound, a BBT evict operation had to be retried because it couldn't meet eviction quota.  [Dev Only]10531BBT Leaf Evict Stalls/sec is the count of times per secound, a BBT leaf evict operation failed to evict any nodes to a leaf page, because of no free space on the page.  [Dev Only]10533Pages Trimmed/sec is the number of database pages that are trimmed and the allocated space is released to the file system.  [Dev Only]10535Pages 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]10537Database 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]10539Database Page Evictions (k=1)/sec is the rate that database file pages are evicted that were of limited usefulness (k=1 pool).  [Dev Only]10541Database Page Evictions (k=2)/sec is the rate that database file pages are evicted that were of high usefulness (k=2 pool).  [Dev Only]10543Database 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]10545Database Page Evictions (Scavenging.Shrink)/sec is the rate that cached pages are evicted during scavenging due to the database cache shrinking.  [Dev Only]10547Database 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]10549Database 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.10551Database 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.10553Database 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.10555No text10557Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.10559No text10561Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.10563Database Cache Requests/sec is the rate that pages are requested from the database cache.10565Instance 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]10567Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]10569Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]10571Database Pages Dirtied/sec is the rate that pages are dirtied in the database cache.  [Dev Only]10573Database Pages Dirtied (Repeatedly)/sec is the rate that pages are  repeatedly dirtied / redirtied in the database cache.  [Dev Only]10575Database Pages Written/sec is the rate that pages are written to the database file(s) from the database cache.  [Dev Only]10577Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]10579Database 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]10581Database 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]10583Database 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]10585Database 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]10587Database 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]10589Database Pages Dehydrated/sec is the rate that pages are compressed to memory usage in the buffer manager. [Dev Only]10591Database Pages Rehydrated/sec is the rate that pages are uncompressed for active usage or flushing to the database. [Dev Only]10593Database 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]10595Database 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]10597Database 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]10599Database 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]10601Database 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]10603Database 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]10605Database 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]10607Database 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]10609Database 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]10611Database 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]10613Database 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]10615Database 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]10617Database 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]10619Database 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]10621Flush Map % Dirty is the percentage of the flush map that has been modified and not persisted since the associated database was attached.  [Dev Only]10623No text10625Flush Map Pages Written Async/sec is the rate at which flush map pages are asynchronously written to the flush map file.  [Dev Only]10627Flush Map Pages Written Sync/sec is the rate at which flush map pages are synchronously written to the flush map file.  [Dev Only]10629Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups.10631Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]10633Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation.  [Dev Only]10635Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]10637Pages Freed/sec is the number of pages per second that are freed from the database by the online defragmentation process [Dev Only]10639Data 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]10641Online 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]10643Online Defrag Log Bytes/sec is the rate at which online defragmentation is generating log bytes.  [Dev Only]10645Database Maintenance Duration is the number of hours that have passed since maintenance last completed for this database.10647Database Maintenance Pages Read is the number of pages read by database maintenance. [Dev Only]10649Database Maintenance Pages Read/sec is the rate at which pages are read by database maintenance. [Dev Only]10651Database Maintenance Pages Zeroed is the number of pages zeroed/scrubbed by database maintenance. [Dev Only]10653Database Maintenance Pages Zeroed/sec is the rate at which pages are zeroed/scrubbed by database maintenance. [Dev Only]10655Database Maintenance Zero Ref Count LVs is the number of zero ref counted LVs deleted by database maintenance. [Dev Only]10657Database Maintenance Pages with Flag Deleted LVs Reclaimed  is the number of LV pages with flag deleted LVs reclaimed  by database maintenance. [Dev Only]10659Database Maintenance IO Reads/sec is the approximate number of Database Maintenance read IO operations generated/sec. [Dev Only]10661Database Maintenance IO Reads Average Bytes is the approximate average size in bytes of Database Maintenance read IO. [Dev Only]10663No text10665Database Maintenance Throttle Setting is the current Database Maintenance throttle setting. [Dev Only]10667Database 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]10669Database 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]10671Database 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]10673Database 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]10675Database 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]10677Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]10679Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]10681Database Tasks Pages Preread/sec is the rate at which database pages are read in anticipation of future use by background database tasks.  [Dev Only]10683Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]10685Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications.  [Dev Only]10687Database Tasks Log Records/sec is the rate at which background database tasks are generating log records.  [Dev Only]10689Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks.  [Dev Only]10691No text10693Database Tasks Log Bytes/sec is the rate at which background database tasks are generating log bytes.  [Dev Only]10695I/O Database Reads (Attached)/sec is the rate of database read operations completed.10697I/O Database Reads (Attached) Average Latency is the average length of time,  in milliseconds, per database read operation.10699No text10701I/O Database Reads (Attached) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]10703No text10705I/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]10707I/O Database Reads (Attached) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]10709I/O Database Reads (Recovery)/sec is the rate of database read operations completed.10711I/O Database Reads (Recovery) Average Latency is the average length of time,  in milliseconds, per database read operation.10713No text10715I/O Database Reads (Recovery) Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]10717No text10719I/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]10721I/O Database Reads (Recovery) Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]10723I/O Database Reads/sec is the rate of database read operations completed.10725I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.10727No text10729I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]10731No text10733I/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]10735I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]10737I/O Log Reads/sec is the rate of logfile read operations completed.10739I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation.10741No text10743I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation.  [Dev Only]10745No text10747I/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]10749I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion.  [Dev Only]10751I/O Snapshot Reads/sec is the rate of snapshot read operations completed.  [Dev Only]10753I/O Snapshot Reads Average Latency is the average length of time, in milliseconds, per snapshot read operation.  [Dev Only]10755No text10757I/O Snapshot Reads Average Bytes is the average number of bytes transferred per snapshot read operation.  [Dev Only]10759No text10761I/O Snapshot Reads In Heap is the number of snapshot read operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]10763I/O Snapshot Reads Async Pending is the number of snapshot read operations asynchronously pending completion.  [Dev Only]10765I/O Database Writes (Attached)/sec is the rate of database write operations completed.10767I/O Database Writes (Attached) Average Latency is the average length of time,  in milliseconds, per database write operation.10769No text10771I/O Database Writes (Attached) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]10773No text10775I/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]10777I/O Database Writes (Attached) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]10779I/O Database Writes (Recovery)/sec is the rate of database write operations completed.10781I/O Database Writes (Recovery) Average Latency is the average length of time,  in milliseconds, per database write operation.10783No text10785I/O Database Writes (Recovery) Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]10787No text10789I/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]10791I/O Database Writes (Recovery) Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]10793I/O Database Writes/sec is the rate of database write operations completed.10795I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.10797No text10799I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]10801No text10803I/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]10805I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]10807I/O Flush Map Writes/sec is the rate of flush map write operations completed.10809I/O Flush Map Writes Average Latency is the average length of time,  in milliseconds, per flush map write operation.10811No text10813I/O Flush Map Writes Average Bytes is the average number of bytes transferred per flush map write operation.  [Dev Only]10815No text10817I/O Log Writes/sec is the rate of log file write operations completed.10819I/O Log Writes Average Latency is the average length of time, in milliseconds, per log file write operation.10821No text10823I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation.  [Dev Only]10825No text10827I/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]10829I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion.  [Dev Only]10831I/O Snapshot Writes/sec is the rate of snapshot write operations completed.  [Dev Only]10833I/O Snapshot Writes Average Latency is the average length of time, in milliseconds, per snapshot write operation.  [Dev Only]10835No text10837I/O Snapshot Writes Average Bytes is the average number of bytes transferred per snapshot write operation.  [Dev Only]10839No text10841I/O Snapshot Writes In Heap is the number of snapshot write operations queued in the database engine's I/O heap and waiting to be issued.  [Dev Only]10843I/O Snapshot Writes Async Pending is the number of snapshot write operations asynchronously pending completion.  [Dev Only]10845FlushFileBuffers ops/sec is the rate of FlushFileBuffers operations completed.  [Dev Only]10847FlushFileBuffers Average Latency is the average length of time, in milliseconds, per FlushFileBuffers operation.  [Dev Only]10849No text10851Encryption Bytes/sec is the number of bytes per second that were encrypted.  [Dev Only]10853Encryption Ops/sec is the number of encryption operations per second that were performed.  [Dev Only]10855encryption average latency (us) is the average latency (in microseconds) per encryption operation.  [Dev Only]10857No text10859Decryption Bytes/sec is the number of bytes per second that were decrypted.  [Dev Only]10861Decryption Ops/sec is the number of decryption operations per second that were performed.  [Dev Only]10863Decryption average latency (us) is the average latency (in microseconds) per decryption operation.  [Dev Only]10865No text10867Compressed Bytes/sec is the number of bytes per second that were compressed during DML operations.  [Dev Only]10869Compression Ops/sec is the number of compression operations per second that were performed during DML operations.  [Dev Only]10871Average latency per compression operation in microseconds.  [Dev Only]10873No text10875Compression ratio calculated as: uncompressed size / compressed size.  [Dev Only]10877No text10879Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations.  [Dev Only]10881Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations.  [Dev Only]10883Average latency per decompression operation in microseconds.  [Dev Only]10885No text10887Xpress10 Software Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations using Xpress10 software implementation.  [Dev Only]10889Xpress10 Software Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations using Xpress10 software implementation.  [Dev Only]10891Xpress10 Software Average latency per decompression operation in microseconds.  [Dev Only]10893No text10895Xpress10 Corsica Compressed Bytes/sec is the number of bytes per second that were compressed during DML operations using Xpress10 on the Corsica hardware.  [Dev Only]10897Xpress10 Corsica Compression Ops/sec is the number of compression operations per second that were performed during DML operations using Xpress10 on the Corsica hardware.  [Dev Only]10899Xpress10 Corsica Average latency per compression operation in microseconds.  [Dev Only]10901No text10903Xpress10 Corsica Average latency in hardware per compression operation in microseconds.  [Dev Only]10905No text10907Xpress10 Corsica Compression ratio calculated as: original size / compressed size.  [Dev Only]10909No text10911Xpress10 Corsica Decompressed Bytes/sec is the number of bytes per second that were decompressed during DML operations using Xpress10 on the Corsica hardware.  [Dev Only]10913Xpress10 Corsica Decompression Ops/sec is the number of decompression operations per second that were performed during DML operations using Xpress10 on the Corsica hardware.  [Dev Only]10915Xpress10 Corsica Average latency per decompression operation in microseconds.  [Dev Only]10917No text10919Xpress10 Corsica Average latency in hardware per decompression operation in microseconds.  [Dev Only]10921No text10923Pages Reorganized (Other)/sec is the number of times per second a page was reorganized for some other / unknown reason.  [Dev Only]10925Pages 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]10927Pages 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]10929Pages Reorganized (Dehydrate Buffer)/sec is the number of times per second a page is reorganized to minimize our in-memory buffer usage.  [Dev Only]10931Database 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.10933No text10935Database 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]10937Provides an estimate of the oldest running transaction by elapsed time in milliseconds.10939New Pages/sec is the number of new pages used per second.  [Dev Only]10941Space Trees Deleted/sec is the number of space trees deleted per second.  [Dev Only]10943Space Trees Deleted Freed Pages/sec is the number of pages freed by space trees deletes per second.  [Dev Only]10945Space Trees Deleted Freed Extents/sec is the number of extents freed by space trees deletes per second.  [Dev Only]10947Revert Snapshot Stalls/sec is the number of times per second that collecting pre-image for a page for revert snapshot was stalled because of running out of snapshot buffers potentially stalling updates to the database.  [Dev Only]10949Space Trees Deleted Snapshotted Pages/sec is the number of pages freed by space trees deletes and captured by revert snapshot per second.  [Dev Only]10951Databases attached to this process10953Database 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.10955I/O Database Reads/sec is the rate of database read operations completed.10957I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.10959No text10961I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]10963No text10965I/O Database Writes/sec is the rate of database write operations completed.10967I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.10969No text10971I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation. [Dev Only]10973No text10975I/O Database Reads (Transactional) Total IO is the number of IOs accumulated   for the database read operation latency counters. [Dev Only]10977I/O Database Reads (Transactional) Mean Latency is the average length of time,  in microseconds, per database read operation. [Dev Only]10979I/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]10981I/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]10983I/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]10985I/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]10987I/O Database Reads (Maintenance) Total IO is the number of IOs accumulated   for the database read operation latency counters. [Dev Only]10989I/O Database Reads (Maintenance) Mean Latency is the average length of time,  in microseconds, per database read operation. [Dev Only]10991I/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]10993I/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]10995I/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]10997I/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]10999I/O Database Writes (Transactional) Total IO is the number of IOs accumulated   for the database write operation latency counters. [Dev Only]11001I/O Database Writes (Transactional) Mean Latency is the average length of time,  in microseconds, per database write operation. [Dev Only]11003I/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]11005I/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]11007I/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]11009I/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]11011I/O Database Writes (Maintenance) Total IO is the number of IOs accumulated   for the database write operation latency counters. [Dev Only]11013I/O Database Writes (Maintenance) Mean Latency is the average length of time,  in microseconds, per database write operation. [Dev Only]11015I/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]11017I/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]11019I/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]11021I/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]11023I/O Database Meted Queue Depth is queued and pending IO operations awaiting an open async IO slot. [Dev Only]11025I/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]11027I/O Database Async Read Pending is the number of async read IO operations outstanding to the OS. [Dev Only]11029Database Cache % Hit (Unique) is the percentage of unique  database file page requests that were fulfilled by the database cache.11031No text11033Database Cache Requests/sec (Unique) is the rate at which unique pages are requested from the database cache.11035Shrink Priming Current Position is the current position (in bytes) in the database file which is being primed for shrinkage. [Dev Only]11037Counters for classes in the System.Net namespace.11039The cumulative total number of socket connections established for this process since the process was started.11041The 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.11043The 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.11045The cumulative total number of datagram packets received since the process was started.11047The cumulative total number of datagram packets sent since the process was started.11049The number of HttpWebRequest objects created during the last sample interval (typically 1 sec).11051The 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.11053HttpWebRequests Average Lifetime Base11055The 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.11057The 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.11059HttpWebRequests Average Queue Time Base11061The 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.11063The 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()11065MSDTC Bridge 4.0.0.0 performance counters11067The number of WS-AT protocol messages that the WS-AT service failed to send per second.11069The number of Prepare retry messages that the WS-AT service has sent per second.11071The number of Commit retry messages that the WS-AT service has sent per second.11073The number of Prepared retry messages that the WS-AT service has sent per second.11075The number of Replay retry messages that the WS-AT service has sent per second.11077The number of Fault messages that the WS-AT service has received per second.11079The number of Fault messages that the WS-AT service has sent per second.11081Average time in milliseconds for the WS-AT service to receive a Prepare message response from a participant.11083Base counter for the 'Average participant prepare response time' counter.11085Average time in milliseconds for the WS-AT service to receive a Commit message response from a participant.11087Base counter for the 'Average participant commit response time' counter.11089Displays performance statistics about ReadyBoost Caches.11091The total (uncompressed) amount of data currently stored in ReadyBoost caches.11093Amount of space in bytes taken by data cached in ReadyBoost caches.11095(Cache space used) / (Bytes cached)11097Total size, in bytes, of all caches regardless of how much data they contain.11099Number of I/Os satisfied from ReadyBoost caches per second.11101Bytes of I/Os satisfied from ReadyBoost caches per second.11103Number of read I/Os ignored by ReadyBoost due to policy.11105Bytes of read I/Os ignored by ReadyBoost due to policy.11107Number of read I/Os that are received by ReadyBoost. This counter includes all reads whether or not they were satisfied by ReadyBoost caches.11109Bytes of read I/Os that are received by ReadyBoost. This counter includes all reads whether or not they were satisfied by ReadyBoost caches.11111Terminal Services per-session resource monitoring.19265Number of WMI High Performance provider returned by WMI Adapter19267Shows High Performance Classes19269Shows if High Performance Classes are valid19271MSiSCSI_ConnectionStatistics19273BytesReceived19275BytesSent19277PDUCommandsSent19279PDUResponsesReceived19281MSiSCSI_InitiatorInstanceStatistics19283SessionConnectionTimeoutErrorCount19285SessionDigestErrorCount19287SessionFailureCount19289SessionFormatErrorCount19291MSiSCSI_InitiatorLoginStatistics19293LoginAcceptRsps19295LoginAuthenticateFails19297LoginAuthFailRsps19299LoginFailures19301LoginNegotiateFails19303LoginOtherFailRsps19305LoginRedirectRsps19307LogoutNormals19309LogoutOtherCodes19311MSiSCSI_MMIPSECStats19313AcquireFailures19315AcquireHeapSize19317ActiveAcquire19319ActiveReceive19321AuthenticationFailures19323ConnectionListSize19325GetSPIFailures19327InvalidCookiesReceived19329InvalidPackets19331KeyAdditionFailures19333KeyAdditions19335KeyUpdateFailures19337KeyUpdates19339NegotiationFailures19341OakleyMainMode19343OakleyQuickMode19345ReceiveFailures19347ReceiveHeapSize19349SendFailures19351SoftAssociations19353TotalGetSPI19355MSiSCSI_NICPerformance19357BytesReceived19359BytesTransmitted19361PDUReceived19363PDUTransmitted19365MSiSCSI_QMIPSECStats19367ActiveSA19369ActiveTunnels19371AuthenticatedBytesReceived19373AuthenticatedBytesSent19375BadSPIPackets19377ConfidentialBytesReceived19379ConfidentialBytesSent19381KeyAdditions19383KeyDeletions19385PacketsNotAuthenticated19387PacketsNotDecrypted19389PacketsWithReplayDetection19391PendingKeyOperations19393ReKeys19395TransportBytesReceived19397TransportBytesSent19399TunnelBytesReceived19401TunnelBytesSent19403MSiSCSI_RequestTimeStatistics19405AverageProcessingTime19407MaximumProcessingTime19409MSiSCSI_SessionStatistics19411BytesReceived19413BytesSent19415ConnectionTimeoutErrors19417DigestErrors19419FormatErrors19421PDUCommandsSent19423PDUResponsesReceived19425ProcessorPerformance19427frequency19429percentage19431power
Anon7 - 2021