1. ========================= SEAF 1.0.1.0 - C_XX
2. 
3. Commencé à: 15:21:01 le 06/08/2014
4. 
5. Valeur(s) recherchée(s):
6. bing
7. 
8. Légende: TC => Date de création, TM => Date de modification, DA => Dernier accès
9. 
10. (!) --- Recherche registre
11. 
12. ====== Fichier(s) ======
13. 
14. 
15. "C:\Windows\winsxs\amd64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.16428_none_11b913172f0cb26f\bing.ico" [ ARCHIVE | 5 Ko ]
16. TC: 10/06/2014,04:31:09 | TM: 10/06/2014,04:31:09 | DA: 10/06/2014,04:31:09
17. 
18. 
19. =========================
20. 
21. 
22. "C:\Windows\winsxs\amd64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.17041_none_11e6f4b92ee9bf19\bing.ico" [ ARCHIVE | 5 Ko ]
23. TC: 10/06/2014,04:31:09 | TM: 10/06/2014,04:31:09 | DA: 10/06/2014,04:31:09
24. 
25. 
26. =========================
27. 
28. 
29. "C:\Windows\winsxs\amd64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.17126_none_11d9b2512ef42881\bing.ico" [ ARCHIVE | 5 Ko ]
30. TC: 10/06/2014,04:31:09 | TM: 10/06/2014,04:31:09 | DA: 10/06/2014,04:31:09
31. 
32. 
33. =========================
34. 
35. 
36. "C:\Windows\winsxs\amd64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.17207_none_11cccb092efe2b65\bing.ico" [ ARCHIVE | 5 Ko ]
37. TC: 10/06/2014,04:31:09 | TM: 10/06/2014,04:31:09 | DA: 10/06/2014,04:31:09
38. 
39. 
40. =========================
41. 
42. 
43. 
44. ====== Entrée(s) du registre ======
45. 
46. 
47. [HKLM\Software\Microsoft\Internet Explorer\Extension Compatibility\{8DCB7100-DF86-4384-8842-8FA844297B3F}]
48. "DllName"="BingExt.dll" (REG_SZ)
49. 
50. [HKLM\Software\Microsoft\Internet Explorer\Extension Compatibility\{D2CE3E00-F94A-4740-988E-03DC2F38C34F}]
51. "DllName"="BingExt.dll" (REG_SZ)
52. 
53. [HKLM\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
54. ""="Bing" (REG_SZ)
55. 
56. [HKLM\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
57. "URL"="http://www.bing.com/search?q={searchTerms}&FORM=IE8SRC" (REG_SZ)
58. 
59. [HKLM\Software\Microsoft\Speech\PhoneConverters\Tokens\Chinese]
60. "PhoneMap"="- 0001 ! 0002 & 0003 , 0004 . 0005 ? 0006 _ 0007 + 0008 * 0009 1 000A 2 000B 3 000C 4 000D 5 000E a 000F ai 0010 an 0011 ang 0012 ao 0013 ba 0014 bai 0015 ban 0016 bang 0017 bao 0018 bei 0019 ben 001A beng 001B bi 001C bian 001D biao 001E bie 001F bin 0020 bing 0021 bo 0022 bu 0023 ca 0024 cai 0025 can 0026 cang 0027 cao 0028 ce 0029 cen 002A ceng 002B cha 002C chai 002D chan 002E chang 002F chao 0030 che 0031 chen 0032 cheng 0033 chi 0034 chong 0035 chou 0036 chu 0037 chuai 0038 chuan 0039 chuang 003A chui 003B chun 003C chuo 003D ci 003E cong 003F cou 0040 cu 0041 cuan 0042 cui 0043 cun 0044 cuo 0045 da 0046 dai 0047 dan 0048 dang 0049 dao 004A de 004B dei 004C den 004D deng 004E di 004F dia 0050 dian 0051 diao 0052 die 0053 ding 0054 diu 0055 dong 0056 dou 0057 du 0058 duan 0059 dui 005A dun 005B duo 005C e 005D ei 005E en 005F er 0060 fa 0061 fan 0062 fang 0063 fei 0064 fen 0065 feng 0066 fo 0067 fou 0068 fu 0069 ga 006A gai 006B gan 006C gang 006D gao 006E ge 006F gei 0070 gen 0071 geng 0072 gong 0073 gou 0074 gu 0075 gua 0076 guai 0077 guan 0078 guang 0079 gui 007A gun 007B guo 007C ha 007D hai 007E han 007F hang 0080 hao 0081 he 0082 hei 0083 hen 0084 heng 0085 hong 0086 hou 0087 hu 0088 hua 0089 huai 008A huan 008B huang 008C hui 008D hun 008E huo 008F ji 0090 jia 0091 jian 0092 jiang 0093 jiao 0094 jie 0095 jin 0096 jing 0097 jiong 0098 jiu 0099 ju 009A juan 009B jue 009C jun 009D ka 009E kai 009F kan 00A0 kang 00A1 kao 00A2 ke 00A3 kei 00A4 ken 00A5 keng 00A6 kong 00A7 kou 00A8 ku 00A9 kua 00AA kuai 00AB kuan 00AC kuang 00AD kui 00AE kun 00AF kuo 00B0 la 00B1 lai 00B2 lan 00B3 lang 00B4 lao 00B5 le 00B6 lei 00B7 leng 00B8 li 00B9 lia 00BA lian 00BB liang 00BC liao 00BD lie 00BE lin 00BF ling 00C0 liu 00C1 lo 00C2 long 00C3 lou 00C4 lu 00C5 luan 00C6 lue 00C7 lun 00C8 luo 00C9 lv 00CA ma 00CB mai 00CC man 00CD mang 00CE mao 00CF me 00D0 mei 00D1 men 00D2 meng 00D3 mi 00D4 mian 00D5 miao 00D6 mie 00D7 min 00D8 ming 00D9 miu 00DA mo 00DB mou 00DC mu 00DD na 00DE nai 00DF nan 00E0 nang 00E1 nao 00E2 ne 00E3 nei 00E4 nen 00E5 neng 00E6 ni 00E7 nian 00E8 niang 00E9 niao 00EA nie 00EB nin 00EC ning 00ED niu 00EE nong 00EF nou 00F0 nu 00F1 nuan 00F2 nue 00F3 nuo 00F4 nv 00F5 o 00F6 ou 00F7 pa 00F8 pai 00F9 pan 00FA pang 00FB pao 00FC pei 00FD pen 00FE peng 00FF pi 0100 pian 0101 piao 0102 pie 0103 pin 0104 ping 0105 po 0106 pou 0107 pu 0108 qi 0109 qia 010A qian 010B qiang 010C qiao 010D qie 010E qin 010F qing 0110 qiong 0111 qiu 0112 qu 0113 quan 0114 que 0115 qun 0116 ran 0117 rang 0118 rao 0119 re 011A ren 011B reng 011C ri 011D rong 011E rou 011F ru 0120 ruan 0121 rui 0122 run 0123 ruo 0124 sa 0125 sai 0126 san 0127 sang 0128 sao 0129 se 012A sen 012B seng 012C sha 012D shai 012E shan 012F shang 0130 shao 0131 she 0132 shei 0133 shen 0134 sheng 0135 shi 0136 shou 0137 shu 0138 shua 0139 shuai 013A shuan 013B shuang 013C shui 013D shun 013E shuo 013F si 0140 song 0141 sou 0142 su 0143 suan 0144 sui 0145 sun 0146 suo 0147 ta 0148 tai 0149 tan 014A tang 014B tao 014C te 014D tei 014E teng 014F ti 0150 tian 0151 tiao 0152 tie 0153 ting 0154 tong 0155 tou 0156 tu 0157 tuan 0158 tui 0159 tun 015A tuo 015B wa 015C wai 015D wan 015E wang 015F wei 0160 wen 0161 weng 0162 wo 0163 wu 0164 xi 0165 xia 0166 xian 0167 xiang 0168 xiao 0169 xie 016A xin 016B xing 016C xiong 016D xiu 016E xu 016F xuan 0170 xue 0171 xun 0172 ya 0173 yan 0174 yang 0175 yao 0176 ye 0177 yi 0178 yin 0179 ying 017A yo 017B yong 017C you 017D yu 017E yuan 017F yue 0180 yun 0181 za 0182 zai 0183 zan 0184 zang 0185 zao 0186 ze 0187 zei 0188 zen 0189 zeng 018A zha 018B zhai 018C zhan 018D zhang 018E zhao 018F zhe 0190 zhei 0191 zhen 0192 zheng 0193 zhi 0194 zhong 0195 zhou 0196 zhu 0197 zhua 0198 zhuai 0199 zhuan 019A zhuang 019B zhui 019C zhun 019D zhuo 019E zi 019F zong 01A0 zou 01A1 zu 01A2 zuan 01A3 zui 01A4 zun 01A5 zuo 01A6" (REG_SZ)
61. 
62. [HKLM\Software\Microsoft\Windows NT\CurrentVersion\Perflib\009]
63. "Help"="3
64. The System performance object consists of counters that apply to more than one instance of a component processors on the computer.
65. 5
66. The 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.
67. 7
68. % 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.
69. 9
70. % Total DPC Time is the average percentage of time that all processors spend receiving and servicing deferred procedure calls (DPCs).  (DPCs are interrupts that run at a lower priority than the standard interrupts). It is the sum of Processor: % DPC Time for all processors on the computer, divided by the number of processors.  System: % Total DPC Time is a component of System: % Total Privileged Time because DPCs are executed in privileged mode.  DPCs are counted separately and are not a component of the interrupt count.  This counter displays the average busy time as a percentage of the sample time.
71. 11
72. File 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.
73. 13
74. File 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.
75. 15
76. File 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.
77. 17
78. File 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.
79. 19
80. File 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.
81. 21
82. File 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.
83. 23
84. % Total Interrupt Time is the average percentage of time that all processors spend receiving and servicing hardware interrupts during sample intervals, where the value is an indirect indicator of the activity of devices that generate interrupts. It is the sum of Processor: % Interrupt Time for of all processors on the computer, divided by the number of processors.  DPCs are counted separately and are not a component of the interrupt count.  This value is an indirect indicator of the activity of devices that generate interrupts, such as the system timer, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices.
85. 25
86. Available 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. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.
87. 27
88. Committed 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.
89. 29
90. Page 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.
91. 31
92. Commit 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.
93. 33
94. Write 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.
95. 35
96. Transition 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.
97. 37
98. Cache 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.
99. 39
100. Demand 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.
101. 41
102. Pages/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.
103. 43
104. Page 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.
105. 45
106. Processor 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.
107. 47
108. Thread 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.
109. 49
110. Pages 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.
111. 51
112. Page 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.
113. 53
114. The Browser performance object consists of counters that measure the rates of announcements, enumerations, and other Browser transmissions.
115. 55
116. Announcements Server/sec is the rate at which the servers in this domain have announced themselves to this server.
117. 57
118. Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) 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\\Pool Paged Bytes\\_Total. This counter displays the last observed value only; it is not an average.
119. 59
120. Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) 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\\Pool Nonpaged Bytes\\_Total.  This counter displays the last observed value only; it is not an average.
121. 61
122. Pool Paged Allocs is the number of calls to allocate space in the paged pool. The paged pool is an area of system memory (physical memory used by the operating system) 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.
123. 63
124. Pool Paged Resident Bytes is the current size, in bytes, of the paged pool. The paged pool is an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used. Space used by the paged and nonpaged pools are taken from physical memory, so a pool that is too large denies memory space to processes. This counter displays the last observed value only; it is not an average.
125. 65
126. Pool 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.
127. 67
128. Bytes 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.
129. 69
130. System Code Total Bytes is the size, in bytes, of the pageable operating system code currently in virtual memory. It is a measure of the amount of physical memory being used by the operating system that can be written to disk when not in use. 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.
131. 71
132. System Code Resident Bytes is the size, in bytes of the operating system code currently in physical memory that can be written to disk when not in use. This value is a component of Memory\\System Code Total Bytes, which also includes operating system code on disk. 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.
133. 73
134. System 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 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.
135. 75
136. System 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.
137. 77
138. System Cache Resident Bytes is the size, in bytes, of the pageable operating system code in the file system cache. This value includes only current physical pages and does not include any virtual memory pages not currently resident. It does equal the System Cache value shown in Task Manager. As a result, this value may be smaller than the actual amount of virtual memory in use by the file system cache. This value is a component of Memory\\System Code Resident Bytes which represents all pageable operating system code that is currently in physical memory. This counter displays the last observed value only; it is not an average.
139. 79
140. Announcements Domain/sec is the rate at which a domain has announced itself to the network.
141. 81
142. Election Packets/sec is the rate at which browser election packets have been received by this workstation.
143. 83
144. Mailslot Writes/sec is the rate at which mailslot messages have been successfully received.
145. 85
146. Server List Requests/sec is the rate at which requests to retrieve a list of browser servers have been processed by this workstation.
147. 87
148. The Cache performance object  consists of counters that monitor the file system cache, an area of physical memory that stores recently used data as long as possible to permit access to the data without having to read from the disk.  Because applications typically use the cache, the cache is monitored as an indicator of application I/O operations.  When memory is plentiful, the cache can grow, but when memory is scarce, the cache can become too small to be effective.
149. 89
150. Data Maps/sec is the frequency that a file system such as NTFS, maps a page of a file into the file system cache to read the page.
151. 91
152. Sync Data Maps/sec counts the frequency that a file system, such as NTFS, maps a page of a file into the file system cache to read the page, and wishes to wait for the page to be retrieved if it is not in main memory.
153. 93
154. Async Data Maps/sec is the frequency that an application using a file system, such as NTFS, to map a page of a file into the file system cache to read the page, and does not wait for the page to be retrieved if it is not in main memory.
155. 95
156. Data Map Hits is the percentage of data maps in the file system cache that could be resolved without having to retrieve a page from the disk, because the page was already in physical memory.
157. 97
158. Data Map Pins/sec is the frequency of data maps in the file system cache that resulted in pinning a page in main memory, an action usually preparatory to writing to the file on disk.   While pinned, a page's physical address in main memory and virtual address in the file system cache will not be altered.
159. 99
160. Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk.  Pages read in this fashion are pinned in memory at the completion of the read.  While pinned, a page's physical address in the file system cache will not be altered.
161. 101
162. Sync Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk.  Pages read in this fashion are pinned in memory at the completion of the read.  The file system will not regain control until the page is pinned in the file system cache, in particular if the disk must be accessed to retrieve the page.  While pinned, a page's physical address in the file system cache will not be altered.
163. 103
164. Async Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk.  Pages read in this fashion are pinned in memory at the completion of the read.  The file system will regain control immediately even if the disk must be accessed to retrieve the page.  While pinned, a page's physical address will not be altered.
165. 105
166. Pin Read Hits is the percentage of pin read requests that hit the file system cache, i.e., did not require a disk read in order to provide access to the page in the file system cache.  While pinned, a page's physical address in the file system cache will not be altered.  The LAN Redirector uses this method for retrieving data from the cache, as does the LAN Server for small transfers.  This is usually the method used by the disk file systems as well.
167. 107
168. Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer.  The LAN Redirector uses this method for retrieving information from the file system cache, as does the LAN Server for small transfers.  This is a method used by the disk file systems as well.
169. 109
170. Sync Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer.  The file system will not regain control until the copy operation is complete, even if the disk must be accessed to retrieve the page.
171. 111
172. Async Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer.  The application will regain control immediately even if the disk must be accessed to retrieve the page.
173. 113
174. Copy Read Hits is the percentage of cache copy read requests that hit the cache, that is, they did not require a disk read in order to provide access to the page in the cache.  A copy read is a file read operation that is satisfied by a memory copy from a page in the cache to the application's buffer.  The LAN Redirector uses this method for retrieving information from the cache, as does the LAN Server for small transfers.  This is a method used by the disk file systems as well.
175. 115
176. MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the data.  The MDL contains the physical address of each page involved in the transfer, and thus can employ a hardware Direct Memory Access (DMA) device to effect the copy.  The LAN Server uses this method for large transfers out of the server.
177. 117
178. Sync MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages.  The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages.  If the accessed page(s) are not in main memory, the caller will wait for the pages to fault in from the disk.
179. 119
180. Async MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages.  The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages.  If the accessed page(s) are not in main memory, the calling application program will not wait for the pages to fault in from disk.
181. 121
182. MDL Read Hits is the percentage of Memory Descriptor List (MDL) Read requests to the file system cache that hit the cache, i.e., did not require disk accesses in order to provide memory access to the page(s) in the cache.
183. 123
184. Read Aheads/sec is the frequency of reads from the file system cache in which the Cache detects sequential access to a file.  The read aheads permit the data to be transferred in larger blocks than those being requested by the application, reducing the overhead per access.
185. 125
186. 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.
187. 127
188. Sync Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache.  Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache.  Even if the data is not in the cache, one invocation of the file system is avoided.  If the data is not in the cache, the request (application program call) will wait until the data has been retrieved from disk.
189. 129
190. Async Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache.  Normally, file I/O requests will invoke the appropriate file system to retrieve data from a file, but this path permits data to be retrieved from the cache directly (without file system involvement) if the data is in the cache.  Even if the data is not in the cache, one invocation of the file system is avoided.  If the data is not in the cache, the request (application program call) will not wait until the data has been retrieved from disk, but will get control immediately.
191. 131
192. Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request.
193. 133
194. Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass the file system to get to data in the file system cache that could not be honored without invoking the file system.
195. 135
196. Lazy Write Flushes/sec is the rate at which the Lazy Writer thread has written to disk.  Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding.  More than one page can be transferred by each write operation.
197. 137
198. Lazy Write Pages/sec is the rate at which the Lazy Writer thread has written to disk.  Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding.  More than one page can be transferred on a single disk write operation.
199. 139
200. Data Flushes/sec is the rate at which the file system cache has flushed its contents to disk as the result of a request to flush or to satisfy a write-through file write request.  More than one page can be transferred on each flush operation.
201. 141
202. Data Flush Pages/sec is the number of pages the file system cache has flushed to disk as a result of a request to flush or to satisfy a write-through file write request.  More than one page can be transferred on each flush operation.
203. 143
204. % 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.
205. 145
206. % 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.
207. 147
208. Context 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.
209. 149
210. Interrupts/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.
211. 151
212. System 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.
213. 153
214. Level 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.
215. 155
216. Level 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.
217. 157
218. % 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.
219. 159
220. % 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.
221. 161
222. Enumerations Server/sec is the rate at which server browse requests have been processed by this workstation.
223. 163
224. Enumerations Domain/sec is the rate at which domain browse requests have been processed by this workstation.
225. 165
226. Enumerations Other/sec is the rate at which browse requests processed by this workstation are not domain or server browse requests.
227. 167
228. Missed Server Announcements is the number of server announcements that have been missed due to configuration or allocation limits.
229. 169
230. Missed Mailslot Datagrams is the number of Mailslot Datagrams that have been discarded due to configuration or allocation limits.
231. 171
232. Missed 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.
233. 173
234. Virtual 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.
235. 175
236. Virtual 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.
237. 177
238. Page Faults/sec is the rate at which page faults by the threads executing in this process are occurring.  A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This may not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.
239. 179
240. Working 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.
241. 181
242. Working 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.
243. 183
244. Page 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.
245. 185
246. Page 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.
247. 187
248. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes.
249. 189
250. % 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.
251. 191
252. % 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.
253. 193
254. % User Time is the percentage of elapsed time that this thread has spent executing code in user mode.  Applications, environment subsystems, and integral subsystems execute in user mode.  Code executing in user mode cannot damage the integrity of the Windows NT Executive, Kernel, and device drivers.  Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes.  These subsystem processes provide additional protection.  Therefore, some work done by Windows NT on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.
255. 195
256. % 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.
257. 197
258. Context Switches/sec is the rate of switches from one thread to another.  Thread switches can occur either inside of a single process or across processes.  A thread switch can be caused either by one thread asking another for information, or by a thread being preempted by another, higher priority thread becoming ready to run.  Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes.  These subsystem processes provide additional protection.  Therefore, some work done by Windows NT on behalf of an application  appear in other subsystem processes in addition to the privileged time in the application.  Switching to the subsystem process causes one Context Switch in the application thread.  Switching back causes another Context Switch in the subsystem thread.
259. 199
260. Current 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.
261. 201
262. % Disk Time is the percentage of elapsed time that the selected disk drive was busy servicing read or write requests.
263. 203
264. % Disk Read Time is the percentage of elapsed time that the selected disk drive was busy servicing read requests.
265. 205
266. % Disk Write Time is the percentage of elapsed time that the selected disk drive was busy servicing write requests.
267. 207
268. Avg. Disk sec/Transfer is the time, in seconds, of the average disk transfer.
269. 209
270. Avg. Disk sec/Read is the average time, in seconds, of a read of data from the disk.
271. 211
272. Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk.
273. 213
274. Disk Transfers/sec is the rate of read and write operations on the disk.
275. 215
276. Disk Reads/sec is the rate of read operations on the disk.
277. 217
278. Disk Writes/sec is the rate of write operations on the disk.
279. 219
280. Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations.
281. 221
282. Disk Read Bytes/sec is the rate at which bytes are transferred from the disk during read operations.
283. 223
284. Disk Write Bytes/sec is rate at which bytes are transferred to the disk during write operations.
285. 225
286. Avg. Disk Bytes/Transfer is the average number of bytes transferred to or from the disk during write or read operations.
287. 227
288. Avg. Disk Bytes/Read is the average number of bytes transferred from the disk during read operations.
289. 229
290. Avg. Disk Bytes/Write is the average number of bytes transferred to the disk during write operations.
291. 231
292. The 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.
293. 233
294. The 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.
295. 235
296. The 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.
297. 237
298. The 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.
299. 239
300. The 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.
301. 241
302. % 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%.
303. 243
304. % 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.
305. 245
306. % 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.
307. 247
308. Total 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.
309. 249
310. Processes 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.
311. 251
312. Threads 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.
313. 253
314. Events 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.
315. 255
316. Semaphores 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.
317. 257
318. Mutexes 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.
319. 259
320. Sections 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.
321. 261
322. The 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.
323. 263
324. The Redirector performance object consists of counter that monitor network connections originating at the local computer.
325. 265
326. Bytes 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).
327. 267
328. Packets 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).
329. 269
330. Read 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).
331. 271
332. Read 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.
333. 273
334. Read 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).
335. 275
336. Read 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).
337. 277
338. Bytes 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).
339. 279
340. Packets 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.
341. 281
342. Write 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).
343. 283
344. Write 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.
345. 285
346. Write 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.
347. 287
348. Write 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).
349. 289
350. File 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.
351. 291
352. Read 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.
353. 293
354. Read 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.
355. 295
356. Reads 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.
357. 297
358. Read 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.
359. 299
360. File 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.
361. 301
362. Write 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.
363. 303
364. Write 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.
365. 305
366. Writes 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.
367. 307
368. Write 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.
369. 309
370. Reads 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.
371. 311
372. Writes 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.
373. 313
374. Network 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 Manager Block) protocol error is a Network Error. An entry is written to the System Event Log and provide details.
375. 315
376. Server 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.
377. 317
378. Server 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.
379. 319
380. Connects 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.
381. 321
382. Connects LAN Manager 2.0 counts connections to LAN Manager 2.0 servers, including LMX servers.
383. 323
384. Connects LAN Manager 2.1 counts connections to LAN Manager 2.1 servers, including LMX servers.
385. 325
386. Connects Windows NT counts the connections to Windows 2000 or earlier computers.
387. 327
388. Server Disconnects counts the number of times a Server has disconnected your Redirector.  See also Server Reconnects.
389. 329
390. Server 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.
391. 331
392. The Server performance object consists of counters that measure communication between the  local computer and the network.
393. 333
394. The number of bytes the server has received from the network.  Indicates how busy the server is.
395. 335
396. The number of bytes the server has sent on the network.  Indicates how busy the server is.
397. 337
398. Thread 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).
399. 339
400. % DPC Time is the percentage of time that the processor spent receiving and servicing deferred procedure calls (DPCs) during the sample interval. DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a component of % Privileged Time because DPCs are executed in privileged mode. They are counted separately and are not a component of the interrupt counters. This counter displays the average busy time as a percentage of the sample time.
401. 341
402. The 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.
403. 343
404. The 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.
405. 345
406. The number of sessions that have terminated normally.  Useful in interpreting the Sessions Times Out and Sessions Errored Out statistics--allows percentage calculations.
407. 347
408. The number of sessions that have been forced to logoff.  Can indicate how many sessions were forced to logoff due to logon time constraints.
409. 349
410. The number of failed logon attempts to the server.  Can indicate whether password guessing programs are being used to crack the security on the server.
411. 351
412. The 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.
413. 353
414. The number of times accesses to files opened successfully were denied.  Can indicate attempts to access files without proper access authorization.
415. 355
416. The number of times an internal Server Error was detected.  Unexpected errors usually indicate a problem with the Server.
417. 357
418. The 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.
419. 359
420. The 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.
421. 361
422. The 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.
423. 363
424. The number of files currently opened in the server.  Indicates current server activity.
425. 365
426. The number of sessions currently active in the server.  Indicates current server activity.
427. 367
428. The number of searches for files currently active in the server.  Indicates current server activity.
429. 369
430. The number of bytes of non-pageable computer memory the server is using.  This value is useful for determining the values of the MaxNonpagedMemoryUsage value entry in the Windows NT Registry.
431. 371
432. The number of times allocations from nonpaged pool have failed.  Indicates that the computer's physical memory is too small.
433. 373
434. The 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.
435. 375
436. The number of bytes of pageable computer memory the server is currently using.  Can help in determining good values for the MaxPagedMemoryUsage parameter.
437. 377
438. The number of times allocations from paged pool have failed.  Indicates that the computer's physical memory or paging file are too small.
439. 379
440. The maximum number of bytes of paged pool the server has had allocated.  Indicates the proper sizes of the Page File(s) and physical memory.
441. 381
442. Server Announce Allocations Failed/sec is the rate at which server (or domain) announcements have failed due to lack of memory.
443. 383
444. Mailslot Allocations Failed is the number of times the datagram receiver has failed to allocate a buffer to hold a user mailslot write.
445. 385
446. Mailslot Receives Failed indicates the number of mailslot messages that could not be received due to transport failures.
447. 387
448. Mailslot Writes Failed is the total number of mailslot messages that have been successfully received, but that could not be written to the mailslot.
449. 389
450. Bytes 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.
451. 391
452. File Data Operations/sec is the rate at which the Redirector is processing data operations. One operation should include many bytes, since each operation has overhead. The efficiency of this path can be determined by dividing the Bytes/sec by this counter to obtain the average number of bytes transferred per operation.
453. 393
454. Current 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.
455. 395
456. The number of bytes the server has sent to and received from the network.  This value provides an overall indication of how busy the server is.
457. 397
458. % Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. suspends normal thread execution during interrupts. This counter displays the average busy time as a percentage of the sample time.
459. 399
460. The NWLink NetBIOS performance object consists of counters that monitor IPX transport rates and connections.
461. 401
462. Packets/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.
463. 405
464. Context 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.
465. 407
466. File 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.
467. 409
468. % Free Space is the percentage of total usable space on the selected logical disk drive that was free.
469. 411
470. Free Megabytes displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.
471. 413
472. Connections Open is the number of connections currently open for this protocol.  This counter shows the current count only and does not accumulate over time.
473. 415
474. Connections 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.
475. 417
476. Connections 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.
477. 419
478. Disconnects Local is the number of session disconnections that were initiated by the local computer.  This number is an accumulator and shows a running total.
479. 421
480. Disconnects Remote is the number of session disconnections that were initiated by the remote computer.  This number is an accumulator and shows a running total.
481. 423
482. Failures Link is the number of connections that were dropped due to a link failure.  This number is an accumulator and shows a running total.
483. 425
484. Failures Adapter is the number of connections that were dropped due to an adapter failure.  This number is an accumulator and shows a running total.
485. 427
486. Connection 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.
487. 429
488. Connections Canceled is the number of connections that were canceled.  This number is an accumulator and shows a running total.
489. 431
490. Failures 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.
491. 433
492. Failures 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.
493. 435
494. Failures 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.
495. 437
496. Failures No Listen is the number of connections that were rejected because the remote computer was not listening for connection requests.
497. 439
498. Datagrams/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.
499. 441
500. Datagram 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.
501. 443
502. Datagrams 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.
503. 445
504. Datagram 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.
505. 447
506. Datagrams 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.
507. 449
508. Datagram 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.
509. 451
510. Packets/sec is the rate at which packets are processed by the computer.  This count is the sum of Packets Sent and Packets Received per second.  This counter includes all packets processed: control as well as data packets.
511. 453
512. Packets 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.
513. 455
514. Packets Received/sec is the rate at which packets are received by the computer.  This counter counts all packets processed: control as well as data packets.
515. 457
516. Frames/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.
517. 459
518. Frame 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.
519. 461
520. Frames Sent/sec is the rate at which data frames are sent by the computer.  This counter only counts the frames (packets) that carry data.
521. 463
522. Frame 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.
523. 465
524. Frames Received/sec is the rate at which data frames are received by the computer.  This counter only counts the frames (packets) that carry data.
525. 467
526. Frame 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.
527. 469
528. Frames 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.
529. 471
530. Frame 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.
531. 473
532. Frames Rejected/sec is the rate at which data frames are rejected.  This counter only counts the frames (packets) that carry data.
533. 475
534. Frame 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.
535. 477
536. Expirations Response is the count of T1 timer expirations.
537. 479
538. Expirations Ack is the count of T2 timer expirations.
539. 481
540. Window Send Maximum is the maximum number of bytes of data that will be sent before waiting for an acknowledgment from the remote computer.
541. 483
542. Window Send Average is the running average number of data bytes that were sent before waiting for an acknowledgment from the remote computer.
543. 485
544. Piggyback 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.
545. 487
546. Piggyback 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.
547. 489
548. The NWLink IPX performance object consists of counters that measure datagram transmission to and from computers using the IPX protocol.
549. 491
550. The NWLink SPX performance object consist of counters that measure data transmission and session connections for computers using the SPX protocol.
551. 493
552. The NetBEUI performance object consists of counters that measure data transmission for network activity which conforms to the NetBIOS End User Interface standard.
553. 495
554. The NetBEUI Resource performance object consists of counters that track the use of buffers by the NetBEUI protocol.
555. 497
556. Used 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.
557. 499
558. Used 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.
559. 501
560. Times 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.
561. 503
562. The 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.
563. 505
564. Bytes Received/sec is the rate at which bytes are received by the local computer over an NBT connection to some remote computer.  All the bytes received by the local computer over the particular NBT connection are counted.
565. 507
566. Bytes 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.
567. 509
568. Bytes 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.
569. 511
570. The Network Interface performance object consists of counters that measure the rates at which bytes and packets are sent and received over a TCP/IP network connection.  It includes counters that monitor connection errors.
571. 513
572. Bytes 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.
573. 515
574. Packets/sec is the rate at which packets are sent and received on the network interface.
575. 517
576. Packets Received/sec is the rate at which packets are received on the network interface.
577. 519
578. Packets Sent/sec is the rate at which packets are sent on the network interface.
579. 521
580. Current 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.
581. 523
582. Bytes Received/sec is the rate at which bytes are received over each network adapter, including framing characters. Network Interface\Bytes Received/sec is a subset of Network Interface\Bytes Total/sec.
583. 525
584. Packets Received Unicast/sec is the rate at which (subnet) unicast packets are delivered to a higher-layer protocol.
585. 527
586. Packets Received Non-Unicast/sec is the rate at which non-unicast (subnet broadcast or subnet multicast) packets are delivered to a higher-layer protocol.
587. 529
588. Packets 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.
589. 531
590. Packets Received Errors is the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
591. 533
592. Packets Received Unknown is the number of packets received through the interface that were discarded because of an unknown or unsupported protocol.
593. 535
594. Bytes Sent/sec is the rate at which bytes are sent over each network adapter, including framing characters. Network Interface\Bytes Sent/sec is a subset of Network Interface\Bytes Total/sec.
595. 537
596. Packets 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.
597. 539
598. Packets 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.
599. 541
600. Packets 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.
601. 543
602. Packets Outbound Errors is the number of outbound packets that could not be transmitted because of errors.
603. 545
604. Output 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.
605. 547
606. The 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.
607. 549
608. Datagrams/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.
609. 551
610. Datagrams Received/sec is the rate, in incidents per second, at which IP datagrams are received from the interfaces, including those in error. Datagrams Received/sec is a subset of Datagrams/sec.
611. 553
612. Datagrams 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.
613. 555
614. Datagrams 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.
615. 557
616. Datagrams 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.
617. 559
618. Datagrams Received Unknown Protocol is the number of locally-addressed datagrams that were successfully received but were discarded because of an unknown or unsupported protocol.
619. 561
620. Datagrams 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.
621. 563
622. Datagrams 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).
623. 565
624. Datagrams Sent/sec is the rate, in incidents per second, at which IP datagrams were supplied for transmission by local IP user-protocols (including ICMP). This counter does not include any datagrams counted in Datagrams Forwarded/sec. Datagrams Sent/sec is a subset of Datagrams/sec.
625. 567
626. Datagrams 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.
627. 569
628. Datagrams 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.
629. 571
630. Fragments Received/sec is the rate, in incidents per second, at which IP fragments that need to be reassembled at this entity are received.
631. 573
632. Fragments Re-assembled/sec is the rate, in incidents per second, at which IP fragments were successfully reassembled.
633. 575
634. Fragment 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.
635. 577
636. Fragmented Datagrams/sec is the rate, in incidents per second, at which datagrams are successfully fragmented.
637. 579
638. Fragmentation 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).
639. 581
640. Fragments Created/sec is the rate, in incidents per second, at which IP datagram fragments were generated as a result of fragmentation.
641. 583
642. The 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.
643. 585
644. Messages/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.
645. 587
646. Messages Received/sec is the rate, in incidents per second at which ICMP messages were received. The rate includes messages received in error.
647. 589
648. Messages Received Errors is the number of ICMP messages that the entity received but had errors, such as bad ICMP checksums, bad length, etc.
649. 591
650. Received Destination Unreachable is the number of ICMP Destination Unreachable messages received.
651. 593
652. Received Time Exceeded is the number of ICMP Time Exceeded messages received.
653. 595
654. Received Parameter Problem is the number of ICMP Parameter Problem messages received.
655. 597
656. Received Source Quench is the number of ICMP Source Quench messages received.
657. 599
658. Received Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were received.
659. 601
660. Received Echo/sec is the rate, in incidents per second, at which ICMP Echo messages were received.
661. 603
662. Received Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were received.
663. 605
664. Received Timestamp/sec is the rate, in incidents per second at which ICMP Timestamp Request messages were received.
665. 607
666. Received Timestamp Reply/sec is the rate of ICMP Timestamp Reply messages received.
667. 609
668. Received Address Mask is the number of ICMP Address Mask Request messages received.
669. 611
670. Received Address Mask Reply is the number of ICMP Address Mask Reply messages received.
671. 613
672. Messages Sent/sec is the rate, in incidents per second, at which the server attempted to send. The rate includes those messages sent in error.
673. 615
674. Messages 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.
675. 617
676. Sent Destination Unreachable is the number of ICMP Destination Unreachable messages sent.
677. 619
678. Sent Time Exceeded is the number of ICMP Time Exceeded messages sent.
679. 621
680. Sent Parameter Problem is the number of ICMP Parameter Problem messages sent.
681. 623
682. Sent Source Quench is the number of ICMP Source Quench messages sent.
683. 625
684. Sent Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were sent.
685. 627
686. Sent Echo/sec is the rate of ICMP Echo messages sent.
687. 629
688. Sent Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were sent.
689. 631
690. Sent Timestamp/sec is the rate, in incidents per second, at which ICMP Timestamp Request messages were sent.
691. 633
692. Sent Timestamp Reply/sec is the rate, in incidents per second,  at which ICMP Timestamp Reply messages were sent.
693. 635
694. Sent Address Mask is the number of ICMP Address Mask Request messages sent.
695. 637
696. Sent Address Mask Reply is the number of ICMP Address Mask Reply messages sent.
697. 639
698. The 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.
699. 641
700. Segments/sec is the rate at which TCP segments are sent or received using the TCP protocol.
701. 643
702. Connections Established is the number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
703. 645
704. Connections 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.
705. 647
706. Connections 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.
707. 649
708. Connection 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.
709. 651
710. Connections 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.
711. 653
712. Segments Received/sec is the rate at which segments are received, including those received in error.  This count includes segments received on currently established connections.
713. 655
714. Segments Sent/sec is the rate at which segments are sent, including those on current connections, but excluding those containing only retransmitted bytes.
715. 657
716. Segments Retransmitted/sec is the rate at which segments are retransmitted, that is, segments transmitted containing one or more previously transmitted bytes.
717. 659
718. The 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.
719. 661
720. Datagrams/sec is the rate at which UDP datagrams are sent or received by the entity.
721. 663
722. Datagrams Received/sec is the rate at which UDP datagrams are delivered to UDP users.
723. 665
724. Datagrams No Port/sec is the rate of received UDP datagrams for which there was no application at the destination port.
725. 667
726. Datagrams 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.
727. 669
728. Datagrams Sent/sec is the rate at which UDP datagrams are sent from the entity.
729. 671
730. Disk Storage device statistics from the foreign computer
731. 673
732. The number of allocation failures reported by the disk storage device
733. 675
734. System 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.
735. 677
736. The current number of system handles in use.
737. 679
738. Free 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.
739. 681
740. The 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.
741. 683
742. The current base priority of this process. Threads within a process can raise and lower their own base priority relative to the process' base priority.
743. 685
744. The total elapsed time, in seconds, that this process has been running.
745. 687
746. Alignment Fixups/sec is the rate, in incidents per seconds, at alignment faults were fixed by the system.
747. 689
748. Exception Dispatches/sec is the rate, in incidents per second, at which exceptions were dispatched by the system.
749. 691
750. Floating 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.
751. 693
752. Logon/sec is the rate of all server logons.
753. 695
754. The 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.
755. 697
756. The 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.
757. 699
758. The total elapsed time (in seconds) this thread has been running.
759. 701
760. The 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.
761. 703
762. The amount of the Page File instance in use in percent.  See also Process\\Page File Bytes.
763. 705
764. The peak usage of the Page File instance in percent.  See also Process\\Page File Bytes Peak.
765. 707
766. Starting virtual address for this thread.
767. 709
768. Current User Program Counter for this thread.
769. 711
770. Mapped 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.
771. 713
772. Mapped 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.
773. 715
774. Mapped 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.
775. 717
776. Mapped 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.
777. 719
778. Mapped 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.
779. 721
780. Mapped 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.
781. 723
782. Mapped 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.
783. 725
784. Mapped 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.
785. 727
786. Reserved 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.
787. 729
788. Reserved 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.
789. 731
790. Reserved 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.
791. 733
792. Reserved 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.
793. 735
794. Reserved 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.
795. 737
796. Reserved 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.
797. 739
798. Reserved 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.
799. 741
800. The Image performance object consists of counters that monitor the virtual address usage of images executed by processes on the computer.
801. 743
802. Reserved 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.
803. 745
804. Unassigned 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.
805. 747
806. Unassigned 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.
807. 749
808. Unassigned 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.
809. 751
810. Unassigned 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.
811. 753
812. Unassigned 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.
813. 755
814. Unassigned 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.
815. 757
816. Unassigned 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.
817. 759
818. Unassigned 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.
819. 761
820. Image 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.
821. 763
822. Image 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.
823. 765
824. Image 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.
825. 767
826. Image 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.
827. 769
828. Image 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.
829. 771
830. Image 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.
831. 773
832. Image 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.
833. 775
834. Image 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.
835. 777
836. Bytes Image Reserved is the sum of all virtual memory reserved by images within this process.
837. 779
838. Bytes Image Free is the amount of virtual address space that is not in use or reserved by images within this process.
839. 781
840. Bytes Reserved is the total amount of virtual memory reserved for future use by this process.
841. 783
842. Bytes Free is the total unused virtual address space of this process.
843. 785
844. ID 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.
845. 787
846. The Process Address Space performance object consists of counters that monitor memory allocation and use  for a selected process.
847. 789
848. Image 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.
849. 791
850. Image 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.
851. 793
852. Image 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.
853. 795
854. Image 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.
855. 797
856. Image 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.
857. 799
858. Image 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.
859. 801
860. Image 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.
861. 803
862. Image 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.
863. 805
864. ID 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.
865. 807
866. Mailslot Opens Failed/sec indicates the rate at which mailslot messages to be delivered to mailslots that are not present are received by this workstation.
867. 809
868. Duplicate Master Announcements indicates the number of times that the master browser has detected another master browser on the same domain.
869. 811
870. Illegal Datagrams/sec is the rate at which incorrectly formatted datagrams have been received by the workstation.
871. 813
872. Announcements Total/sec is the sum of Announcements Server/sec and Announcements Domain/sec.
873. 815
874. Enumerations 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.
875. 817
876. The 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.
877. 819
878. Cache Bytes is the sum of the Memory\\System Cache Resident Bytes, Memory\\System Driver Resident Bytes, Memory\\System Code Resident Bytes, and Memory\\Pool Paged Resident Bytes counters.  This counter displays the last observed value only; it is not an average.
879. 821
880. Cache Bytes Peak is the maximum number of bytes used by the file system 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.
881. 823
882. Pages 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.
883. 825
884. Transition 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.
885. 873
886. The number of bytes transmitted total for this connection.
887. 875
888. The number of bytes received total for this connection.
889. 877
890. The number of data frames transmitted total for this connection.
891. 879
892. The number of data frames received total for this connection.
893. 881
894. The compression ratio for bytes being transmitted.
895. 883
896. The compression ratio for bytes being received.
897. 885
898. The total number of CRC Errors for this connection.  CRC Errors occur when the frame received contains erroneous data.
899. 887
900. The total number of Timeout Errors for this connection.  Timeout Errors occur when an expected is not received in time.
901. 889
902. The 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.
903. 891
904. The total number of Alignment Errors for this connection.  Alignment Errors occur when a byte received is different from the byte expected.
905. 893
906. The total number of Buffer Overrun Errors for this connection.  Buffer Overrun Errors when the software cannot handle the rate at which data is received.
907. 895
908. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.
909. 897
910. The number of bytes transmitted per second.
911. 899
912. The number of bytes received per second.
913. 901
914. The number of frames transmitted per second.
915. 903
916. The number of frames received per second.
917. 905
918. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.
919. 909
920. The total number of Remote Access connections.
921. 921
922. The WINS Server performance object consists of counters that monitor communications using the WINS Server service.
923. 923
924. Unique Registrations/sec is the rate at which unique registration are received by the WINS server.
925. 925
926. Group Registrations/sec is the rate at which group registration are received by the WINS server.
927. 927
928. Total 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.
929. 929
930. Unique Renewals/sec is the rate at which unique renewals are received by the WINS server.
931. 931
932. Group Renewals/sec is the rate at which group renewals are received by the WINS server.
933. 933
934. Total 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.
935. 935
936. Total Number of Releases/sec is the rate at which releases are received by the WINS server.
937. 937
938. Total Number of Queries/sec is the rate at which queries are received by the WINS server.
939. 939
940. Unique Conflicts/sec is the rate at which unique registrations/renewals received by the WINS server resulted in conflicts with records in the database.
941. 941
942. Group Conflicts/sec is the rate at which group registration received by the WINS server resulted in conflicts with records in the database.
943. 943
944. Total 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.
945. 945
946. Total Number of Successful Releases/sec
947. 947
948. Total Number of Failed Releases/sec
949. 949
950. Total Number of Successful Queries/sec
951. 951
952. Total Number of Failed Queries/sec
953. 953
954. The 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.
955. 1001
956. Services for Macintosh AFP File Server.
957. 1003
958. The maximum amount of paged memory resources used by the MacFile Server.
959. 1005
960. The current amount of paged memory resources used by the MacFile Server.
961. 1007
962. The maximum amount of nonpaged memory resources use by the MacFile Server.
963. 1009
964. The current amount of nonpaged memory resources used by the MacFile Server.
965. 1011
966. The number of sessions currently connected to the MacFile server.  Indicates current server activity.
967. 1013
968. The maximum number of sessions connected at one time to the MacFile server.  Indicates usage level of server.
969. 1015
970. The number of internal files currently open in the MacFile server.  This count does not include files opened on behalf of Macintosh clients.
971. 1017
972. The 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.
973. 1019
974. The 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.
975. 1021
976. The number of bytes read from disk per second.
977. 1023
978. The number of bytes written to disk per second.
979. 1025
980. The number of bytes received from the network per second.  Indicates how busy the server is.
981. 1027
982. The number of bytes sent on the network per second.  Indicates how busy the server is.
983. 1029
984. The number of outstanding work items waiting to be processed.
985. 1031
986. The maximum number of outstanding work items waiting at one time.
987. 1033
988. The current number of threads used by MacFile server.  Indicates how busy the server is.
989. 1035
990. The maximum number of threads used by MacFile server.  Indicates peak usage level of server.
991. 1051
992. AppleTalk Protocol
993. 1053
994. Number of packets received per second by Appletalk on this port.
995. 1055
996. Number of packets sent per second by Appletalk on this port.
997. 1057
998. Number of bytes received per second by Appletalk on this port.
999. 1059
1000. Number of bytes sent per second by Appletalk on this port.
1001. 1061
1002. Average time in milliseconds to process a DDP packet on this port.
1003. 1063
1004. Number of DDP packets per second received by Appletalk on this port.
1005. 1065
1006. Average time in milliseconds to process an AARP packet on this port.
1007. 1067
1008. Number of AARP packets per second received by Appletalk on this port.
1009. 1069
1010. Average time in milliseconds to process an ATP packet on this port.
1011. 1071
1012. Number of ATP packets per second received by Appletalk on this port.
1013. 1073
1014. Average time in milliseconds to process an NBP packet on this port.
1015. 1075
1016. Number of NBP packets per second received by Appletalk on this port.
1017. 1077
1018. Average time in milliseconds to process a ZIP packet on this port.
1019. 1079
1020. Number of ZIP packets per second received by Appletalk on this port.
1021. 1081
1022. Average time in milliseconds to process an RTMP packet on this port.
1023. 1083
1024. Number of RTMP packets per second received by Appletalk on this port.
1025. 1085
1026. Number of ATP requests retransmitted on this port.
1027. 1087
1028. Number of ATP release timers that have expired on this port.
1029. 1089
1030. Number of ATP Exactly-once transaction responses per second on this port.
1031. 1091
1032. Number of ATP At-least-once transaction responses per second on this port.
1033. 1093
1034. Number of ATP transaction release packets per second received on this port.
1035. 1095
1036. The current amount of nonpaged memory resources used by AppleTalk.
1037. 1097
1038. Number of packets routed in on this port.
1039. 1099
1040. Number of packets dropped due to resource limitations on this port.
1041. 1101
1042. Number of ATP requests retransmitted to this port.
1043. 1103
1044. Number of packets routed out on this port.
1045. 1111
1046. Provides Network Statistics for the local network segment via the Network Monitor Service.
1047. 1113
1048. The total number of frames received per second on this network segment.
1049. 1115
1050. The number of bytes received per second on this network segment.
1051. 1117
1052. The number of Broadcast frames received per second on this network segment.
1053. 1119
1054. The number of Multicast frames received per second on this network segment.
1055. 1121
1056. Percentage of network bandwidth in use on this network segment.
1057. 1125
1058. Percentage of network bandwidth which is made up of broadcast traffic on this network segment.
1059. 1127
1060. Percentage of network bandwidth which is made up of multicast traffic on this network segment.
1061. 1151
1062. The Telephony System
1063. 1153
1064. The number of telephone lines serviced by this computer.
1065. 1155
1066. The number of telephone devices serviced by this computer.
1067. 1157
1068. The number of telephone lines serviced by this computer that are currently active.
1069. 1159
1070. The number of telephone devices that are currently being monitored.
1071. 1161
1072. The rate of outgoing calls made by this computer.
1073. 1163
1074. The rate of incoming calls answered by this computer.
1075. 1165
1076. The number of applications that are currently using telephony services.
1077. 1167
1078. Current outgoing calls being serviced by this computer.
1079. 1169
1080. Current incoming calls being serviced by this computer.
1081. 1233
1082. Packet 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.
1083. 1235
1084. Packet 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.
1085. 1237
1086. Packet 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.
1087. 1239
1088. Packet 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.
1089. 1241
1090. Packet Burst IO/sec is the sum of Packet Burst Read NCPs/sec and Packet Burst Write NCPs/sec.
1091. 1261
1092. Logon Total includes all interactive logons, network logons, service logons, successful logon, and failed logons since the machine is last rebooted.
1093. 1263
1094. The number of durable handles, it indicates how many durable handles keep alive ever when SMB2 sessions are disconnected.
1095. 1265
1096. The number of reconnected durable handles, the ratio of "reconnected durable handles"/"total durable handles" indicates how much performance gain from reconnect durable handles.
1097. 1267
1098. The 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.
1099. 1269
1100. The 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.
1101. 1271
1102. The number of SMB BranchCache hash requests that were received by the server.
1103. 1273
1104. The number of SMB BranchCache hash responses that have been sent from the server.
1105. 1275
1106. The amount of SMB BranchCache hash data sent from the server. This includes bytes transferred for both hash header requests and full hash data requests.
1107. 1277
1108. The number of resilient handles, it indicates how many resilient handles keep alive ever when SMB2 sessions are disconnected.
1109. 1279
1110. The number of reconnected resilient handles, the ratio of "reconnected resilient handles"/"total resilient handles" indicates how much performance gain from reconnect resilient handles.
1111. 1301
1112. The Server Work Queues performance object consists of counters that monitor the length of the queues and objects in the queues.
1113. 1303
1114. Queue Length is the current length of the server work queue for this CPU.  A sustained queue length greater than four might indicate processor congestion.  This is an instantaneous count, not an average over time.
1115. 1305
1116. Active 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.
1117. 1307
1118. Available 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.
1119. 1309
1120. Every 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 Blocking Queue instance.
1121. 1311
1122. Every 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 instance.
1123. 1313
1124. Every 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 instance.
1125. 1315
1126. Current 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.
1127. 1317
1128. The rate at which the Server is receiving bytes from the network clients on this CPU.  This value is a measure of how busy the Server is.
1129. 1319
1130. The rate at which the Server is sending bytes to the network clients on this CPU.  This value is a measure of how busy the Server is.
1131. 1321
1132. The 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.
1133. 1323
1134. Read Operations/sec is the rate the server is performing file read operations for the clients on this CPU.  This value is a measure of how busy the Server is.  This value will always be 0 in the Blocking Queue instance.
1135. 1325
1136. Read 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.
1137. 1327
1138. Write Operations/sec is the rate the server is performing file write operations for the clients on this CPU.  This value is a measure of how busy the Server is.  This value will always be 0 in the Blocking Queue instance.
1139. 1329
1140. Write 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.
1141. 1331
1142. Total Bytes/sec is the rate the Server is reading and writing data to and from the files for the clients on this CPU.  This value is a measure of how busy the Server is.
1143. 1333
1144. Total 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.
1145. 1335
1146. DPCs 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.
1147. 1337
1148. DPC 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.
1149. 1343
1150. Total 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.
1151. 1345
1152. Total 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.
1153. 1351
1154. % 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.
1155. 1361
1156. Counters that indicate the status of local and system Very Large memory allocations.
1157. 1363
1158. VLM % Virtual Size In Use
1159. 1365
1160. Current size of the process VLM Virtual memory space in bytes.
1161. 1367
1162. The 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.
1163. 1369
1164. The 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.
1165. 1371
1166. The current size of committed VLM memory space for the current process in bytes.
1167. 1373
1168. The peak size of the committed VLM memory space in bytes for the current process since the process started.
1169. 1375
1170. The current size of all committed VLM memory space in bytes for the system.
1171. 1377
1172. The peak size of all committed VLM memory space in bytes since the system was started.
1173. 1379
1174. The current size of all committed shared VLM memory space in bytes for the system.
1175. 1381
1176. Available 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. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.
1177. 1383
1178. Available 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. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.
1179. 1401
1180. Avg. Disk Queue Length is the average number of both read and write requests that were queued for the selected disk during the sample interval.
1181. 1403
1182. Avg. Disk Read Queue Length is the average number of read requests that were queued for the selected disk during the sample interval.
1183. 1405
1184. Avg. Disk Write Queue Length is the average number of write requests that were queued for the selected disk during the sample interval.
1185. 1407
1186. % 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.
1187. 1409
1188. The 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.
1189. 1411
1190. The 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.
1191. 1413
1192. The 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.
1193. 1415
1194. The 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.
1195. 1417
1196. The 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.
1197. 1419
1198. The 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.
1199. 1421
1200. The 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.
1201. 1423
1202. The 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.
1203. 1425
1204. The 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.
1205. 1427
1206. The 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.
1207. 1451
1208. Displays performance statistics about a Print Queue.
1209. 1453
1210. Total number of jobs printed on a print queue since the last restart.
1211. 1455
1212. Number of bytes per second printed on a print queue.
1213. 1457
1214. Total number of pages printed through GDI on a print queue since the last restart.
1215. 1459
1216. Current number of jobs in a print queue.
1217. 1461
1218. Current number of references (open handles) to this printer.
1219. 1463
1220. Peak number of references (open handles) to this printer.
1221. 1465
1222. Current number of spooling jobs in a print queue.
1223. 1467
1224. Maximum number of spooling jobs in a print queue since last restart.
1225. 1469
1226. Total number of out of paper errors in a print queue since the last restart.
1227. 1471
1228. Total number of printer not ready errors in a print queue since the last restart.
1229. 1473
1230. Total number of job errors in a print queue since last restart.
1231. 1475
1232. Total number of calls from browse clients to this print server to request network browse lists since last restart.
1233. 1477
1234. Total number of calls from other print servers to add shared network printers to this server since last restart.
1235. 1479
1236. Working 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.
1237. 1481
1238. Working 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.
1239. 1483
1240. % Idle Time reports the percentage of time during the sample interval that the disk was idle.
1241. 1485
1242. Split 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.
1243. 1501
1244. Reports the accounting and processor usage data collected by each active named Job object.
1245. 1503
1246. Current % Processor Time shows the percentage of the sample interval that the processes in the Job object spent executing code.
1247. 1505
1248. Current % User mode Time shows the percentage of the sample interval that the processes in the Job object spent executing code in user mode.
1249. 1507
1250. Current % 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.
1251. 1509
1252. This 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.
1253. 1511
1254. This 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.
1255. 1513
1256. This 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.
1257. 1515
1258. Pages/Sec shows the page fault rate of all the processes in the Job object.
1259. 1517
1260. Process Count - Total shows the number of processes, both active and terminated, that are or have been associated with the Job object.
1261. 1519
1262. Process Count - Active shows the number of processes that are currently associated with the Job object.
1263. 1521
1264. Process Count - Terminated shows the number of processes that have been terminated because of a limit violation.
1265. 1523
1266. Total 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.
1267. 1525
1268. Total 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.
1269. 1527
1270. Total 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.
1271. 1537
1272. Received Packet Too Big is the number of received packets thatare larger than anticipated.
1273. 1539
1274. Received Membership Query is the number of packets received thatquery their membership to a group.
1275. 1541
1276. Received Membership Report is the number of packets received thatreport their membership to a group.
1277. 1543
1278. Received Membership Reduction is the number of packets received thatcancelled their membership to a group.
1279. 1545
1280. Received Router Solicit is the number of packets received thatsolicit the router.
1281. 1547
1282. Received Router Advert is the number of packets received thatadvert the router.
1283. 1549
1284. % Job object Details shows detailed performance information about the active processes that make up a Job object.
1285. 1551
1286. Received Neighbor Solicit is the number of packets received thatsolicit a neighbor.
1287. 1553
1288. Received Neighbor Advert is the number of packets received thatadvert a neighbor.
1289. 1555
1290. Sent Packet Too Big is the number of sent packets thatare larger than anticipated.
1291. 1557
1292. Sent Membership Query is the number of packets sent thatquery their membership to a group.
1293. 1559
1294. Sent Membership Report is the number of packets sent thatreport their membership to a group.
1295. 1561
1296. Sent Membership Reduction is the number of packets sent thatcancelled their membership to a group.
1297. 1563
1298. Sent Router Solicit is the number of packets sent thatsolicit the router.
1299. 1565
1300. Sent Router Advert is the number of packets sent thatadvert the router.
1301. 1567
1302. Sent Neighbor Solicit is the number of packets sent thatsolicit a neighbor.
1303. 1569
1304. Sent Neighbor Advert is the number of packets sent thatadvert a neighbor.
1305. 1571
1306. These counters track authentication performance on a per second basis.
1307. 1573
1308. This counter tracks the number of NTLM authentications processed per second for the AD on this DC or for local accounts on this member server.
1309. 1575
1310. This counter tracks the number of times that clients use a ticket to authenticate to this computer per second.
1311. 1577
1312. This counter tracks the number of Authentiation 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.
1313. 1579
1314. This 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.
1315. 1581
1316. This 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.
1317. 1583
1318. This 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.
1319. 1585
1320. This 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.
1321. 1587
1322. This 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.
1323. 1589
1324. This 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.
1325. 1591
1326. This 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.
1327. 1593
1328. This counter tracks the number of Digest authentications that are being processed per second.
1329. 1595
1330. This 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.
1331. 1597
1332. Offloaded Connections is the number of TCP connections (over both IPv4 and IPv6) that are currently handled by the TCP chimney offload capable network adapter.
1333. 1671
1334. These counters track the number of security resources and handles used per process.
1335. 1673
1336. This 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.
1337. 1675
1338. This 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.
1339. 1677
1340. Free & 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. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.
1341. 1679
1342. Modified 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. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.
1343. 1681
1344. Standby 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. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.
1345. 1683
1346. Standby 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. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.
1347. 1685
1348. Standby 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. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.
1349. 1747
1350. % Idle Time is the percentage of time the processor is idle during the sample interval
1351. 1749
1352. % 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.
1353. 1751
1354. % 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.
1355. 1753
1356. % 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.
1357. 1755
1358. C1 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.
1359. 1757
1360. C2 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.
1361. 1759
1362. C3 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.
1363. 1761
1364. Heap performance counters for must used heaps
1365. 1763
1366. Memory actively used by this heap (FreeBytes + AllocatedBytes)
1367. 1765
1368. Total virtual address space reserved for this heap (includes uncommitted ranges)
1369. 1767
1370. ReservedBytes minus last uncommitted range in each segment
1371. 1769
1372. Memory on freelists in this heap (does not include uncommitted ranges or blocks in heap cache)
1373. 1771
1374. Number of blocks on the list of free blocks >1k in size
1375. 1773
1376. 1/Average time per allocation (excluding allocs from heap cache)
1377. 1775
1378. 1/Average time per free (excluding frees to heap cache)
1379. 1777
1380. Number of uncommitted ranges in the reserved virtual address
1381. 1779
1382. Difference between number of allocations and frees (for leak detection)
1383. 1781
1384. Allocations/sec from heap cache
1385. 1783
1386. Frees/sec from heap cache
1387. 1785
1388. Allocations/sec of size <1k bytes (including heap cache)
1389. 1787
1390. Frees/sec of size <1k bytes (including heap cache)
1391. 1789
1392. Allocations/sec of size 1-8k bytes
1393. 1791
1394. Frees/sec of size 1-8k bytes
1395. 1793
1396. Allocations/sec of size over 8k bytes
1397. 1795
1398. Frees/sec of size over 8k bytes
1399. 1797
1400. Allocations/sec (including from heap cache)
1401. 1799
1402. Frees/sec (including to heap cache)
1403. 1801
1404. Total number of blocks in the heap cache
1405. 1803
1406. Largest number of blocks of any one size in the heap cache
1407. 1805
1408. (FreeBytes / CommittedBytes) *100
1409. 1807
1410. (VirtualBytes / ReservedBytes) * 100
1411. 1809
1412. Collisions/sec on the heap lock
1413. 1811
1414. Total number of dirty pages on the system cache
1415. 1813
1416. Threshold for number of dirty pages on system cache
1417. 1847
1418. End Marker
1419. 2157
1420. BITS Per Job Network Utilization
1421. 2159
1422. Estimate of Remote Server Speed (Bits/Sec)
1423. 2161
1424. Estimate of the local netcard's speed (Bits/Sec)
1425. 2163
1426. Estimate of most recent percent network interface utilization
1427. 2165
1428. Estimate of the IGD's Internet connection speed (Bits/Sec)
1429. 2167
1430. Estimate of most recent percent IGD Internet connection utilization
1431. 2169
1432. Size of the next download block for BITS
1433. 2171
1434. BITS download response interval (msec)
1435. 2173
1436. Estimated bandwidth available to the remote system (Bits/sec)
1437. 2187
1438. The Telphony System
1439. 2189
1440. The number of telephone lines serviced by this computer.
1441. 2191
1442. The number of telephone devices serviced by this computer.
1443. 2193
1444. the number of telephone lines serviced by this computer that are currently active.
1445. 2195
1446. The number of telephone devices that are currently being monitored.
1447. 2197
1448. The rate of outgoing calls made by this computer.
1449. 2199
1450. The rate of incoming calls answered by this computer.
1451. 2201
1452. The number of applications that are currently using telephony services.
1453. 2203
1454. Current outgoing calls being serviced by this computer.
1455. 2205
1456. Current incoming calls being serviced by this computer.
1457. 2207
1458. The RAS Object Type handles individual ports of the RAS device on your system.
1459. 2209
1460. The number of bytes transmitted total for this connection.
1461. 2211
1462. The number of bytes received total for this connection.
1463. 2213
1464. The number of data frames transmitted total for this connection.
1465. 2215
1466. The number of data frames received total for this connection.
1467. 2217
1468. The compression ratio for bytes being transmitted.
1469. 2219
1470. The compression ratio for bytes being received.
1471. 2221
1472. The total number of CRC Errors for this connection.  CRC Errors occur when the frame received contains erroneous data.
1473. 2223
1474. The total number of Timeout Errors for this connection.  Timeout Errors occur when an expected is not received in time.
1475. 2225
1476. The 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.
1477. 2227
1478. The total number of Alignment Errors for this connection.  Alignment Errors occur when a byte received is different from the byte expected.
1479. 2229
1480. The total number of Buffer Overrun Errors for this connection.  Buffer Overrun Errors when the software cannot handle the rate at which data is received.
1481. 2231
1482. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.
1483. 2233
1484. The number of bytes transmitted per second.
1485. 2235
1486. The number of bytes received per second.
1487. 2237
1488. The number of frames transmitted per second.
1489. 2239
1490. The number of frames received per second.
1491. 2241
1492. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.
1493. 2243
1494. The RAS Object Type handles all combined ports of the RAS device on your system.
1495. 2245
1496. The total number of Remote Access connections.
1497. 3207
1498. Database provides performance statistics for each process using the ESE high performance embedded database management system.
1499. 3209
1500. Pages Converted/sec is the count of times per second a database page is converted from an older database format
1501. 3211
1502. Pages Converted is the count of database pages that have been converted from an older format
1503. 3213
1504. Records Converted/sec is the count of times per second a database record is converted from an older database format
1505. 3215
1506. Records Converted is the count of database records that have been converted from an older format
1507. 3217
1508. Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.
1509. 3219
1510. Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.
1511. 3221
1512. Defragmentation Tasks Discarded is the count of background database defragmentation tasks that could not be registered. [Dev Only]
1513. 3223
1514. Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]
1515. 3225
1516. Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]
1517. 3227
1518. Heap Allocs/sec is the number of memory allocations from the MP Heaps per second.  [Dev Only]
1519. 3229
1520. Heap Frees/sec is the number of memory frees to the MP Heaps per second.  [Dev Only]
1521. 3231
1522. Heap Allocations is the current number of memory allocations in the MP Heaps.  [Dev Only]
1523. 3233
1524. Heap Bytes Allocated is the size of all memory allocations in the MP Heaps discounting heap managemnt overhead.  [Dev Only]
1525. 3235
1526. Page Bytes Reserved is the size of all explicitly reserved virtual address space.  [Dev Only]
1527. 3237
1528. Page Bytes Committed is the size of all explicitly committed virtual memory backing store (page file and physical memory).  [Dev Only]
1529. 3239
1530. FCB Asynchronous 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]
1531. 3241
1532. FCB Asynchronous 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]
1533. 3243
1534. FCB Asynchronous Threshold-Scan/sec is the number of cached schema records (FCBs) scanned during asynchronous schema record cleanup.  Cleanup was triggered by a large number of schema records above the preferred limit.  These records are aggressively scanned to age out older schema definitions.  [Dev Only]
1535. 3245
1536. FCB Asynchronous Threshold-Purge/sec is the number of cached schema records (FCBs) purged during asynchronous schema record cleanup.  Cleanup was triggered by a large number of schema records above the preferred limit.  These records are aggressively purged to age out older schema definitions.  [Dev Only]
1537. 3247
1538. FCB Asynchronous Purge Conflicts/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  The purge operation failed because exclusive ownership of the schema record could not be obtained.  [Dev Only]
1539. 3249
1540. FCB Synchronous Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second.  [Dev Only]
1541. 3251
1542. FCB Synchronous 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]
1543. 3253
1544. FCB 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]
1545. 3255
1546. FCB 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]
1547. 3257
1548. FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache.  No file operations were required.  [Dev Only]
1549. 3259
1550. No text
1551. 3261
1552. FCB 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]
1553. 3263
1554. FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache.  [Dev Only]
1555. 3265
1556. FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache.  [Dev Only]
1557. 3267
1558. FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated and in use.  [Dev Only]
1559. 3269
1560. FCB 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]
1561. 3271
1562. Sessions In Use is the number of database sessions currently open for use by client threads.
1563. 3273
1564. Sessions % Used is the percentage of database sessions currently open for use by client threads.
1565. 3275
1566. No text
1567. 3277
1568. Table 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.
1569. 3279
1570. No text
1571. 3281
1572. Table 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.
1573. 3283
1574. Table 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.
1575. 3285
1576. Table Opens/sec is the number of database tables opened per second.
1577. 3287
1578. Log Bytes Write per second is the rate bytes are written to the log.
1579. 3289
1580. Log 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.
1581. 3291
1582. Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs.  [Dev Only]
1583. 3293
1584. Log Buffer Bytes Free is the amount of free space available in the log buffers.  [Dev Only]
1585. 3295
1586. Log 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.
1587. 3297
1588. Log 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]
1589. 3299
1590. Log 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]
1591. 3301
1592. User 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]
1593. 3303
1594. User Read/Write Transaction Commits to Level 0/sec is the count of fully committed transactions started by the calling process that modify data stored in the database engine.  [Dev Only]
1595. 3305
1596. User 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]
1597. 3307
1598. User 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]
1599. 3309
1600. User 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]
1601. 3311
1602. User 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]
1603. 3313
1604. System 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]
1605. 3315
1606. System Read/Write Transaction Commits to Level 0/sec is the count of fully committed transactions started internally that modify data stored in the database engine.  [Dev Only]
1607. 3317
1608. System 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]
1609. 3319
1610. System 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]
1611. 3321
1612. System 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]
1613. 3323
1614. System Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that access data stored in the database engine.  [Dev Only]
1615. 3325
1616. Database Page Allocation File Extension Async Consumed/sec is the rate of page allocations from a database file that must be serviced by extending the database file, but which do not stall when doing doing so.  [Dev Only]
1617. 3327
1618. Database 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]
1619. 3329
1620. Log Records/sec is the count of records written to the database log buffers per second.  [Dev Only]
1621. 3331
1622. Log Buffer Capacity Flushes/sec is the count of times the database log buffers must be flushed per second because they are full.  [Dev Only]
1623. 3333
1624. Log Buffer Commit Flushes/sec is the count of times the database log buffers must be flushed per second because a transaction is fully committing its changes.  [Dev Only]
1625. 3335
1626. Log Buffer Flushes/sec is the count of times the database log buffers must be flushed per second.  [Dev Only]
1627. 3337
1628. Log 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.
1629. 3339
1630. Log 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.
1631. 3341
1632. Total number of version buckets allocated
1633. 3343
1634. Total number of version buckets allocated for FlagDelete RCEs  [Dev Only]
1635. 3345
1636. VER 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]
1637. 3347
1638. Average length of bookmark in RCE  [Dev Only]
1639. 3349
1640. Number 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]
1641. 3351
1642. Number of times per second a version store clean task is dispatched asynchronously to be performed  [Dev Only]
1643. 3353
1644. Number of times per second a version store clean task is performed synchronously  [Dev Only]
1645. 3355
1646. Number of times per second a version store clean task was discarded due to load concerns  [Dev Only]
1647. 3357
1648. Number of times per second a dispatched version store cleanup task fails  [Dev Only]
1649. 3359
1650. Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]
1651. 3361
1652. Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]
1653. 3363
1654. Record Deletes/sec is the rate at which records in database tables are being updated.  [Dev Only]
1655. 3365
1656. Record 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]
1657. 3367
1658. Record Redundant Replaces/sec is the rate at which records in database tables are being updated with the exact same content of the original record.  [Dev Only]
1659. 3369
1660. Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]
1661. 3371
1662. Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]
1663. 3373
1664. Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]
1665. 3375
1666. False 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]
1667. 3377
1668. False 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]
1669. 3379
1670. Record 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]
1671. 3381
1672. Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]
1673. 3383
1674. Record 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]
1675. 3385
1676. Record 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]
1677. 3387
1678. Record 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]
1679. 3389
1680. Record 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]
1681. 3391
1682. Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]
1683. 3393
1684. Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]
1685. 3395
1686. Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]
1687. 3397
1688. Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]
1689. 3399
1690. Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]
1691. 3401
1692. Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]
1693. 3403
1694. Separated 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]
1695. 3405
1696. Separated 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]
1697. 3407
1698. Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]
1699. 3409
1700. Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]
1701. 3411
1702. Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]
1703. 3413
1704. Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]
1705. 3415
1706. B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]
1707. 3417
1708. B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]
1709. 3419
1710. B+ 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]
1711. 3421
1712. B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]
1713. 3423
1714. B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]
1715. 3425
1716. B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]
1717. 3427
1718. Right 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]
1719. 3429
1720. B+ 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]
1721. 3431
1722. B+ 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]
1723. 3433
1724. B+ 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]
1725. 3435
1726. B+ 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]
1727. 3437
1728. B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]
1729. 3439
1730. B+ 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]
1731. 3441
1732. B+ 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]
1733. 3443
1734. B+ 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]
1735. 3445
1736. B+ 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]
1737. 3447
1738. B+ 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]
1739. 3449
1740. B+ 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]
1741. 3451
1742. B+ 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]
1743. 3453
1744. B+ 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]
1745. 3455
1746. B+ 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]
1747. 3457
1748. B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]
1749. 3459
1750. B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]
1751. 3461
1752. B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]
1753. 3463
1754. B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]
1755. 3465
1756. B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]
1757. 3467
1758. B+ Tree Creates/sec is the number of B+ Trees and their corresponding space trees (if any) created per second.  This can also be viewed as the number of FDP creates per second.  [Dev Only]
1759. 3469
1760. B+ Tree Creates (Total) is the total number of B+ Trees and their corresponding space trees (if any) created.  This can also be viewed as the total number of FDP creates.  [Dev Only]
1761. 3471
1762. B+ Tree Destroys/sec is the number of B+ Trees and their corresponding space trees (if any) destroyed per second.  This can also be viewed as the number of FDP destroys per second.  [Dev Only]
1763. 3473
1764. B+ Tree Destroys (Total) is the total number of B+ Trees and their corresponding space trees (if any) destroyed.  This can also be viewed as the total number of FDP destroys.  [Dev Only]
1765. 3475
1766. Database 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.
1767. 3477
1768. Database 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.
1769. 3479
1770. No text
1771. 3481
1772. Database Cache Requests/sec is the rate that pages are requested from the database cache.
1773. 3483
1774. Database Cache % Pinned is the percentage of the database cache that pinned in the memory.  [Dev Only]
1775. 3485
1776. No text
1777. 3487
1778. Database Cache % Clean is the percentage of the database cache that does not contain modified data.  [Dev Only]
1779. 3489
1780. No text
1781. 3491
1782. Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]
1783. 3493
1784. Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]
1785. 3495
1786. Database Pages Written/sec is the rate that pages are written to the database file (s) from the database cache.  [Dev Only]
1787. 3497
1788. Database Clean Pages Written/sec is the rate that pages are written to the database file (s) from the database cache.  [Dev Only]
1789. 3499
1790. Database Opportune Write Issued (Total) is the count of IO operationshas been issued for opportune write. [Dev Only]
1791. 3501
1792. Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]
1793. 3503
1794. Database Page Latches/sec is the rate that database pages are latched for access to their data.  [Dev Only]
1795. 3505
1796. Database 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]
1797. 3507
1798. Database 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]
1799. 3509
1800. Database 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]
1801. 3511
1802. No text
1803. 3513
1804. Database 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]
1805. 3515
1806. Database 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]
1807. 3517
1808. Database 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]
1809. 3519
1810. No text
1811. 3521
1812. Database 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.
1813. 3523
1814. Database Page Evictions/sec is the rate that database file page requests that 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.
1815. 3525
1816. Database 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 non-zero most of the time, the clean threshold may be too low.
1817. 3527
1818. Database 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.
1819. 3529
1820. Database 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.
1821. 3531
1822. Database 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]
1823. 3533
1824. Database 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]
1825. 3535
1826. Database 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.
1827. 3537
1828. Database 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.
1829. 3539
1830. Database 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]
1831. 3541
1832. No text
1833. 3543
1834. Database 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]
1835. 3545
1836. No text
1837. 3547
1838. Database 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]
1839. 3549
1840. Database Cached Pages Preread/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache that are already cached.  This is non-ideal behavior that represents a waste of processing time.  [Dev Only]
1841. 3551
1842. Database 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]
1843. 3553
1844. Database 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]
1845. 3555
1846. Database 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]
1847. 3557
1848. Database 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]
1849. 3559
1850. No text
1851. 3561
1852. Database Pages Ordinarily Written/sec is the rate that pages are written to the database file (s) from the database cache in preparation for evicting them from the cache to make room for other data.  [Dev Only]
1853. 3563
1854. Database Pages Anomalously Written/sec is the rate that pages are written to the database file (s) from the database cache before they would ordinarily be written.  [Dev Only]
1855. 3565
1856. Database Pages Opportunely Written/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 seeks required to write all the pages is reduced.  [Dev Only]
1857. 3567
1858. Database 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]
1859. 3569
1860. Database Pages Idly Written/sec is the rate that pages are written to the database file (s) from the database cache because there is low disk activity.  [Dev Only]
1861. 3571
1862. Database 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]
1863. 3573
1864. Database 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]
1865. 3575
1866. Database Page History Records is the current number of database page access history records retained for supporting the LRU-K page replacment algorithm.  [Dev Only]
1867. 3577
1868. Database Page History % Hit is the percentage of database page access history record lookups that were successful.  [Dev Only]
1869. 3579
1870. No text
1871. 3581
1872. Database Page Scans/sec is the rate at which database pages are considered for eviction from the database page cache.  [Dev Only]
1873. 3583
1874. Database Page Scans 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]
1875. 3585
1876. No text
1877. 3587
1878. Database Cache % Resident is the percentage of the database cache that are currently in the process's working set.  [Dev Only]
1879. 3589
1880. No text
1881. 3591
1882. Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups.  [Dev Only]
1883. 3593
1884. Online Defrag Pages Referenced/sec is the rate at which online defragmentation is touching database pages.  [Dev Only]
1885. 3595
1886. Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]
1887. 3597
1888. Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation.  [Dev Only]
1889. 3599
1890. Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]
1891. 3601
1892. Online Defrag Pages Re-Dirtied/sec is the rate at which online defragmentation is modifying database pages that already contained modifications.  [Dev Only]
1893. 3603
1894. Pages Freed/sec is the number of pages per second that are freed from the database by the online defragmentation process [Dev Only]
1895. 3605
1896. Data 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]
1897. 3607
1898. Page Moves/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]
1899. 3609
1900. Online Defrag Log Records/sec is the rate at which online defragmentation is generating log records.  [Dev Only]
1901. 3611
1902. Online Defrag Average Log Bytes is the average size of the log records being generated by online defragmentation.  [Dev Only]
1903. 3613
1904. No text
1905. 3615
1906. Pages Read/sec is the number of pages per second that are read from the database by the scanning process [Dev Only]
1907. 3617
1908. Pages Read is the number of pages that have been read from the database by the scanning process [Dev Only]
1909. 3619
1910. Pages Read/sec is the number of pages per second that are zeroed in the database by the scanning process [Dev Only]
1911. 3621
1912. Pages Read is the number of pages that have been zeroed in the database by the scanning process [Dev Only]
1913. 3623
1914. Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]
1915. 3625
1916. Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]
1917. 3627
1918. Database Tasks Pages Preread/sec is the rate at which database pages are read in anticipation of future use by background database tasks.  [Dev Only]
1919. 3629
1920. Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]
1921. 3631
1922. Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications.  [Dev Only]
1923. 3633
1924. Database Tasks Log Records/sec is the rate at which background database tasks are generating log records.  [Dev Only]
1925. 3635
1926. Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks.  [Dev Only]
1927. 3637
1928. No text
1929. 3639
1930. I/O Database Reads/sec is the rate of database read operations completed.
1931. 3641
1932. I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.
1933. 3643
1934. No text
1935. 3645
1936. I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]
1937. 3647
1938. No text
1939. 3649
1940. I/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]
1941. 3651
1942. I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]
1943. 3653
1944. I/O Database Reads Abnormal Latency/sec is the rate of database read operations that take an abnormally long length of time (default is 1 minute) to be serviced by the OS.  [Dev Only]
1945. 3655
1946. I/O Log Reads/sec is the rate of logfile read operations completed.
1947. 3657
1948. I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation.  [Dev Only]
1949. 3659
1950. No text
1951. 3661
1952. I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation.  [Dev Only]
1953. 3663
1954. No text
1955. 3665
1956. I/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]
1957. 3667
1958. I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion.  [Dev Only]
1959. 3669
1960. I/O Log Reads Abnormal Latency/sec is the rate of logfile read operations that take an abnormally long length of time (default is 1 minute) to be serviced by the OS.  [Dev Only]
1961. 3671
1962. I/O Database Writes/sec is the rate of database write operations completed.
1963. 3673
1964. I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.
1965. 3675
1966. No text
1967. 3677
1968. I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]
1969. 3679
1970. No text
1971. 3681
1972. I/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]
1973. 3683
1974. I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]
1975. 3685
1976. I/O Database Writes Abnormal Latency/sec is the rate of database write operations that take an abnormally long length of time (default is 1 minute) to be serviced by the OS.  [Dev Only]
1977. 3687
1978. I/O Log Writes/sec is the rate of logfile write operations completed.
1979. 3689
1980. I/O Log Writes Average Latency is the average length of time, in milliseconds, per logfile write operation.
1981. 3691
1982. No text
1983. 3693
1984. I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation.  [Dev Only]
1985. 3695
1986. No text
1987. 3697
1988. I/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]
1989. 3699
1990. I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion.  [Dev Only]
1991. 3701
1992. I/O Log Writes Abnormal Latency/sec is the rate of logfile write operations that take an abnormally long length of time (default is 1 minute) to be serviced by the OS.  [Dev Only]
1993. 3703
1994. Threads 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]
1995. 3705
1996. Threads 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]
1997. 3707
1998. Record Failed Compression Bytes/sec is the rate of record bytes that either failed Xpress compression or did not significantly reduce the insert/replace size (10% or less). High results are indicative of wasted cpu resources.  [Dev Only]
1999. 3709
2000. Statistics for the ESE high performance embedded database management system by Table Class
2001. 3711
2002. Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]
2003. 3713
2004. Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]
2005. 3715
2006. Record Deletes/sec is the rate at which records in database tables are being updated.  [Dev Only]
2007. 3717
2008. Record 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]
2009. 3719
2010. Record Redundant Replaces/sec is the rate at which records in database tables are being updated with the exact same content of the original record.  [Dev Only]
2011. 3721
2012. Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]
2013. 3723
2014. Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]
2015. 3725
2016. Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]
2017. 3727
2018. False 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]
2019. 3729
2020. False 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]
2021. 3731
2022. Record 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]
2023. 3733
2024. Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]
2025. 3735
2026. Record 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]
2027. 3737
2028. Record 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]
2029. 3739
2030. Record 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]
2031. 3741
2032. Record 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]
2033. 3743
2034. Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]
2035. 3745
2036. Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]
2037. 3747
2038. Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]
2039. 3749
2040. Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]
2041. 3751
2042. Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]
2043. 3753
2044. Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]
2045. 3755
2046. Separated 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]
2047. 3757
2048. Separated 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]
2049. 3759
2050. Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]
2051. 3761
2052. Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]
2053. 3763
2054. Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]
2055. 3765
2056. Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]
2057. 3767
2058. B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]
2059. 3769
2060. B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]
2061. 3771
2062. B+ 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]
2063. 3773
2064. B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]
2065. 3775
2066. B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]
2067. 3777
2068. B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]
2069. 3779
2070. Right 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]
2071. 3781
2072. B+ 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]
2073. 3783
2074. B+ 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]
2075. 3785
2076. B+ 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]
2077. 3787
2078. B+ 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]
2079. 3789
2080. B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]
2081. 3791
2082. B+ 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]
2083. 3793
2084. B+ 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]
2085. 3795
2086. B+ 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]
2087. 3797
2088. B+ 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]
2089. 3799
2090. B+ 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]
2091. 3801
2092. B+ 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]
2093. 3803
2094. B+ 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]
2095. 3805
2096. B+ 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]
2097. 3807
2098. B+ 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]
2099. 3809
2100. B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]
2101. 3811
2102. B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]
2103. 3813
2104. B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]
2105. 3815
2106. B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]
2107. 3817
2108. B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]
2109. 3819
2110. B+ Tree Creates/sec is the number of B+ Trees and their corresponding space trees (if any) created per second.  This can also be viewed as the number of FDP creates per second.  [Dev Only]
2111. 3821
2112. B+ Tree Creates (Total) is the total number of B+ Trees and their corresponding space trees (if any) created.  This can also be viewed as the total number of FDP creates.  [Dev Only]
2113. 3823
2114. B+ Tree Destroys/sec is the number of B+ Trees and their corresponding space trees (if any) destroyed per second.  This can also be viewed as the number of FDP destroys per second.  [Dev Only]
2115. 3825
2116. B+ Tree Destroys (Total) is the total number of B+ Trees and their corresponding space trees (if any) destroyed.  This can also be viewed as the total number of FDP destroys.  [Dev Only]
2117. 3827
2118. Database 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.
2119. 3829
2120. Database 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.
2121. 3831
2122. Database 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.
2123. 3833
2124. No text
2125. 3835
2126. Database Cache Requests/sec is the rate that pages are requested from the database cache.
2127. 3837
2128. Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]
2129. 3839
2130. Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]
2131. 3841
2132. Database Pages Written/sec is the rate that pages are written to the database file (s) from the database cache.  [Dev Only]
2133. 3843
2134. Database Clean Pages Written/sec is the rate that pages are written to the database file (s) from the database cache.  [Dev Only]
2135. 3845
2136. Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]
2137. 3847
2138. Database 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]
2139. 3849
2140. Database Cached Pages Preread/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache that are already cached.  This is non-ideal behavior that represents a waste of processing time.  [Dev Only]
2141. 3851
2142. Database 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]
2143. 3853
2144. Database 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]
2145. 3855
2146. Database 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]
2147. 3857
2148. Database Pages Ordinarily Written/sec is the rate that pages are written to the database file (s) from the database cache in preparation for evicting them from the cache to make room for other data.  [Dev Only]
2149. 3859
2150. Database Pages Anomalously Written/sec is the rate that pages are written to the database file (s) from the database cache before they would ordinarily be written.  [Dev Only]
2151. 3861
2152. Database Pages Opportunely Written/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 seeks required to write all the pages is reduced.  [Dev Only]
2153. 3863
2154. Database 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]
2155. 3865
2156. Database Pages Idly Written/sec is the rate that pages are written to the database file (s) from the database cache because there is low disk activity.  [Dev Only]
2157. 3867
2158. Database 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]
2159. 3869
2160. Database 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]
2161. 3871
2162. Instances in this process
2163. 3873
2164. Pages Converted/sec is the count of times per second a database page is converted from an older database format
2165. 3875
2166. Pages Converted is the count of database pages that have been converted from an older format
2167. 3877
2168. Records Converted/sec is the count of times per second a database record is converted from an older database format
2169. 3879
2170. Records Converted is the count of database records that have been converted from an older format
2171. 3881
2172. Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.
2173. 3883
2174. Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.
2175. 3885
2176. Defragmentation Tasks Discarded is the count of background database defragmentation tasks that could not be registered. [Dev Only]
2177. 3887
2178. Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]
2179. 3889
2180. Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]
2181. 3891
2182. FCB Asynchronous 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]
2183. 3893
2184. FCB Asynchronous 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]
2185. 3895
2186. FCB Asynchronous Threshold-Scan/sec is the number of cached schema records (FCBs) scanned during asynchronous schema record cleanup.  Cleanup was triggered by a large number of schema records above the preferred limit.  These records are aggressively scanned to age out older schema definitions.  [Dev Only]
2187. 3897
2188. FCB Asynchronous Threshold-Purge/sec is the number of cached schema records (FCBs) purged during asynchronous schema record cleanup.  Cleanup was triggered by a large number of schema records above the preferred limit.  These records are aggressively purged to age out older schema definitions.  [Dev Only]
2189. 3899
2190. FCB Asynchronous Purge Conflicts/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup.  The purge operation failed because exclusive ownership of the schema record could not be obtained.  [Dev Only]
2191. 3901
2192. FCB Synchronous Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second.  [Dev Only]
2193. 3903
2194. FCB Synchronous 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]
2195. 3905
2196. FCB 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]
2197. 3907
2198. FCB 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]
2199. 3909
2200. FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache.  No file operations were required.  [Dev Only]
2201. 3911
2202. No text
2203. 3913
2204. FCB 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]
2205. 3915
2206. FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache.  [Dev Only]
2207. 3917
2208. FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache.  [Dev Only]
2209. 3919
2210. FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated and in use.  [Dev Only]
2211. 3921
2212. FCB 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]
2213. 3923
2214. Sessions In Use is the number of database sessions currently open for use by client threads.
2215. 3925
2216. Sessions % Used is the percentage of database sessions currently open for use by client threads.
2217. 3927
2218. No text
2219. 3929
2220. Table 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.
2221. 3931
2222. No text
2223. 3933
2224. Table 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.
2225. 3935
2226. Table 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.
2227. 3937
2228. Table Opens/sec is the number of database tables opened per second.
2229. 3939
2230. Log Bytes Write per second is the rate bytes are written to the log.
2231. 3941
2232. Log 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.
2233. 3943
2234. Log Buffer Size is the amount of memory, in bytes, allocated for the database log buffers.  [Dev Only]
2235. 3945
2236. Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs.  [Dev Only]
2237. 3947
2238. Log Buffer Bytes Free is the amount of free space available in the log buffers.  [Dev Only]
2239. 3949
2240. Log 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.
2241. 3951
2242. Log File Size is the size, in bytes, of the database log files.  [Dev Only]
2243. 3953
2244. Log 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]
2245. 3955
2246. Log 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.
2247. 3957
2248. Log Generation Checkpoint Depth Target represents the ideal target for the amount of work, in count of log files, that may be redone or undone to the database file(s) if the process crashes.
2249. 3959
2250. Log 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.
2251. 3961
2252. No text
2253. 3963
2254. Log Generation Checkpoint Depth Max represents the maximum allowable amount of work, in count of log files, that may be redone or undone to the database file(s) if the process crashes.
2255. 3965
2256. Log Generation Loss Resiliency Depth represents the amount of work, in count of log files, that may be lost while still allowing the database file(s) to recover (with data loss) if the process crashes.
2257. 3967
2258. Log Files Generated represents the total number of log files generated by an instance since that instance was last initialized.
2259. 3969
2260. Log 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.
2261. 3971
2262. Log File Current Generation gives the generation number of the current log file of an instance.
2263. 3973
2264. User 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]
2265. 3975
2266. User Read/Write Transaction Commits to Level 0/sec is the count of fully committed transactions started by the calling process that modify data stored in the database engine.  [Dev Only]
2267. 3977
2268. User 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]
2269. 3979
2270. User 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]
2271. 3981
2272. User 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]
2273. 3983
2274. User 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]
2275. 3985
2276. System 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]
2277. 3987
2278. System Read/Write Transaction Commits to Level 0/sec is the count of fully committed transactions started internally that modify data stored in the database engine.  [Dev Only]
2279. 3989
2280. System 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]
2281. 3991
2282. System 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]
2283. 3993
2284. System 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]
2285. 3995
2286. System Transaction Rollbacks to Level 0/sec is the count of aborted transactions started internally that access data stored in the database engine.  [Dev Only]
2287. 3997
2288. Database Page Allocation File Extension Async Consumed/sec is the rate of page allocations from a database file that must be serviced by extending the database file, but which do not stall when doing doing so.  [Dev Only]
2289. 3999
2290. Database 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]
2291. 4001
2292. Log Records/sec is the count of records written to the database log buffers per second.  [Dev Only]
2293. 4003
2294. Log Buffer Capacity Flushes/sec is the count of times the database log buffers must be flushed per second because they are full.  [Dev Only]
2295. 4005
2296. Log Buffer Commit Flushes/sec is the count of times the database log buffers must be flushed per second because a transaction is fully committing its changes.  [Dev Only]
2297. 4007
2298. Log Buffer Flushes/sec is the count of times the database log buffers must be flushed per second.  [Dev Only]
2299. 4009
2300. Log 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.
2301. 4011
2302. Log 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.
2303. 4013
2304. Total number of version buckets allocated
2305. 4015
2306. Total number of version buckets allocated for FlagDelete RCEs  [Dev Only]
2307. 4017
2308. VER 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]
2309. 4019
2310. Average length of bookmark in RCE  [Dev Only]
2311. 4021
2312. Number 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]
2313. 4023
2314. Number of times per second a version store clean task is dispatched asynchronously to be performed  [Dev Only]
2315. 4025
2316. Number of times per second a version store clean task is performed synchronously  [Dev Only]
2317. 4027
2318. Number of times per second a version store clean task was discarded due to load concerns  [Dev Only]
2319. 4029
2320. Number of times per second a dispatched version store cleanup task fails  [Dev Only]
2321. 4031
2322. Record Inserts/sec is the rate at which records are being inserted into database tables.  [Dev Only]
2323. 4033
2324. Record Deletes/sec is the rate at which records in database tables are being flagged for deletion.  [Dev Only]
2325. 4035
2326. Record Deletes/sec is the rate at which records in database tables are being updated.  [Dev Only]
2327. 4037
2328. Record 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]
2329. 4039
2330. Record Redundant Replaces/sec is the rate at which records in database tables are being updated with the exact same content of the original record.  [Dev Only]
2331. 4041
2332. Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated.  [Dev Only]
2333. 4043
2334. Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables.  [Dev Only]
2335. 4045
2336. Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion.  [Dev Only]
2337. 4047
2338. False 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]
2339. 4049
2340. False 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]
2341. 4051
2342. Record 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]
2343. 4053
2344. Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables.  [Dev Only]
2345. 4055
2346. Record 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]
2347. 4057
2348. Record 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]
2349. 4059
2350. Record 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]
2351. 4061
2352. Record 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]
2353. 4063
2354. Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed.  [Dev Only]
2355. 4065
2356. Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed.  [Dev Only]
2357. 4067
2358. Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table.  [Dev Only]
2359. 4069
2360. Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified.  [Dev Only]
2361. 4071
2362. Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion.  [Dev Only]
2363. 4073
2364. Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied.  [Dev Only]
2365. 4075
2366. Separated 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]
2367. 4077
2368. Separated 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]
2369. 4079
2370. Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables.  [Dev Only]
2371. 4081
2372. Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced.  [Dev Only]
2373. 4083
2374. Separated Long-Value Chunk Deletes/sec is the rate at which separated long-value chunks in a database table are flagged for deletion.  [Dev Only]
2375. 4085
2376. Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied.  [Dev Only]
2377. 4087
2378. B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second.  [Dev Only]
2379. 4089
2380. B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second.  [Dev Only]
2381. 4091
2382. B+ 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]
2383. 4093
2384. B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second.  [Dev Only]
2385. 4095
2386. B+ Tree Splits/sec is the count of times a page is appended to or split in a database B+ Tree per second.  [Dev Only]
2387. 4097
2388. B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second.  [Dev Only]
2389. 4099
2390. Right 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]
2391. 4101
2392. B+ 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]
2393. 4103
2394. B+ 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]
2395. 4105
2396. B+ 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]
2397. 4107
2398. B+ 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]
2399. 4109
2400. B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second.  [Dev Only]
2401. 4111
2402. B+ 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]
2403. 4113
2404. B+ 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]
2405. 4115
2406. B+ 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]
2407. 4117
2408. B+ 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]
2409. 4119
2410. B+ 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]
2411. 4121
2412. B+ 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]
2413. 4123
2414. B+ 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]
2415. 4125
2416. B+ 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]
2417. 4127
2418. B+ 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]
2419. 4129
2420. B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second.  [Dev Only]
2421. 4131
2422. B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second.  [Dev Only]
2423. 4133
2424. B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second.  [Dev Only]
2425. 4135
2426. B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second.  [Dev Only]
2427. 4137
2428. B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second.  [Dev Only]
2429. 4139
2430. B+ Tree Creates/sec is the number of B+ Trees and their corresponding space trees (if any) created per second.  This can also be viewed as the number of FDP creates per second.  [Dev Only]
2431. 4141
2432. B+ Tree Creates (Total) is the total number of B+ Trees and their corresponding space trees (if any) created.  This can also be viewed as the total number of FDP creates.  [Dev Only]
2433. 4143
2434. B+ Tree Destroys/sec is the number of B+ Trees and their corresponding space trees (if any) destroyed per second.  This can also be viewed as the number of FDP destroys per second.  [Dev Only]
2435. 4145
2436. B+ Tree Destroys (Total) is the total number of B+ Trees and their corresponding space trees (if any) destroyed.  This can also be viewed as the total number of FDP destroys.  [Dev Only]
2437. 4147
2438. Database 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.
2439. 4149
2440. Database 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.
2441. 4151
2442. Database 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.
2443. 4153
2444. No text
2445. 4155
2446. Database Cache Requests/sec is the rate that pages are requested from the database cache.
2447. 4157
2448. Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache.  [Dev Only]
2449. 4159
2450. Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache.  [Dev Only]
2451. 4161
2452. Database Pages Written/sec is the rate that pages are written to the database file (s) from the database cache.  [Dev Only]
2453. 4163
2454. Database Clean Pages Written/sec is the rate that pages are written to the database file (s) from the database cache.  [Dev Only]
2455. 4165
2456. Database Pages Transferred/sec is the rate that pages are transferred from the database file(s) to the database cache and vice versa.  [Dev Only]
2457. 4167
2458. Database 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]
2459. 4169
2460. Database Cached Pages Preread/sec is the rate that pages are read in anticipation of future use from the database file(s) into the database cache that are already cached.  This is non-ideal behavior that represents a waste of processing time.  [Dev Only]
2461. 4171
2462. Database 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]
2463. 4173
2464. Database 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]
2465. 4175
2466. Database 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]
2467. 4177
2468. Database Pages Ordinarily Written/sec is the rate that pages are written to the database file (s) from the database cache in preparation for evicting them from the cache to make room for other data.  [Dev Only]
2469. 4179
2470. Database Pages Anomalously Written/sec is the rate that pages are written to the database file (s) from the database cache before they would ordinarily be written.  [Dev Only]
2471. 4181
2472. Database Pages Opportunely Written/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 seeks required to write all the pages is reduced.  [Dev Only]
2473. 4183
2474. Database 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]
2475. 4185
2476. Database Pages Idly Written/sec is the rate that pages are written to the database file (s) from the database cache because there is low disk activity.  [Dev Only]
2477. 4187
2478. Database 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]
2479. 4189
2480. Database 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]
2481. 4191
2482. Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups.
2483. 4193
2484. Online Defrag Pages Referenced/sec is the rate at which online defragmentation is touching database pages.  [Dev Only]
2485. 4195
2486. Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]
2487. 4197
2488. Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation.  [Dev Only]
2489. 4199
2490. Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]
2491. 4201
2492. Online Defrag Pages Re-Dirtied/sec is the rate at which online defragmentation is modifying database pages that already contained modifications.  [Dev Only]
2493. 4203
2494. Pages Freed/sec is the number of pages per second that are freed from the database by the online defragmentation process [Dev Only]
2495. 4205
2496. Data 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]
2497. 4207
2498. Page Moves/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]
2499. 4209
2500. Online Defrag Log Records/sec is the rate at which online defragmentation is generating log records.  [Dev Only]
2501. 4211
2502. Online Defrag Average Log Bytes is the average size of the log records being generated by online defragmentation.  [Dev Only]
2503. 4213
2504. No text
2505. 4215
2506. Pages Read/sec is the number of pages per second that are read from the database by the scanning process [Dev Only]
2507. 4217
2508. Pages Read is the number of pages that have been read from the database by the scanning process [Dev Only]
2509. 4219
2510. Pages Read/sec is the number of pages per second that are zeroed in the database by the scanning process [Dev Only]
2511. 4221
2512. Pages Read is the number of pages that have been zeroed in the database by the scanning process [Dev Only]
2513. 4223
2514. Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]
2515. 4225
2516. Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]
2517. 4227
2518. Database Tasks Pages Preread/sec is the rate at which database pages are read in anticipation of future use by background database tasks.  [Dev Only]
2519. 4229
2520. Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]
2521. 4231
2522. Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications.  [Dev Only]
2523. 4233
2524. Database Tasks Log Records/sec is the rate at which background database tasks are generating log records.  [Dev Only]
2525. 4235
2526. Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks.  [Dev Only]
2527. 4237
2528. No text
2529. 4239
2530. I/O Database Reads/sec is the rate of database read operations completed.
2531. 4241
2532. I/O Database Reads Average Latency is the average length of time,  in milliseconds, per database read operation.
2533. 4243
2534. No text
2535. 4245
2536. I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation.  [Dev Only]
2537. 4247
2538. No text
2539. 4249
2540. I/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]
2541. 4251
2542. I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion.  [Dev Only]
2543. 4253
2544. I/O Database Reads Abnormal Latency/sec is the rate of database read operations that take an abnormally long length of time (default is 1 minute) to be serviced by the OS.  [Dev Only]
2545. 4255
2546. I/O Log Reads/sec is the rate of logfile read operations completed.
2547. 4257
2548. I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation.  [Dev Only]
2549. 4259
2550. No text
2551. 4261
2552. I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation.  [Dev Only]
2553. 4263
2554. No text
2555. 4265
2556. I/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]
2557. 4267
2558. I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion.  [Dev Only]
2559. 4269
2560. I/O Log Reads Abnormal Latency/sec is the rate of logfile read operations that take an abnormally long length of time (default is 1 minute) to be serviced by the OS.  [Dev Only]
2561. 4271
2562. I/O Database Writes/sec is the rate of database write operations completed.
2563. 4273
2564. I/O Database Writes Average Latency is the average length of time,  in milliseconds, per database write operation.
2565. 4275
2566. No text
2567. 4277
2568. I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation.  [Dev Only]
2569. 4279
2570. No text
2571. 4281
2572. I/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]
2573. 4283
2574. I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion.  [Dev Only]
2575. 4285
2576. I/O Database Writes Abnormal Latency/sec is the rate of database write operations that take an abnormally long length of time (default is 1 minute) to be serviced by the OS.  [Dev Only]
2577. 4287
2578. I/O Log Writes/sec is the rate of logfile write operations completed.
2579. 4289
2580. I/O Log Writes Average Latency is the average length of time, in milliseconds, per logfile write operation.
2581. 4291
2582. No text
2583. 4293
2584. I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation.  [Dev Only]
2585. 4295
2586. No text
2587. 4297
2588. I/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]
2589. 4299
2590. I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion.  [Dev Only]
2591. 4301
2592. I/O Log Writes Abnormal Latency/sec is the rate of logfile write operations that take an abnormally long length of time (default is 1 minute) to be serviced by the OS.  [Dev Only]
2593. 4303
2594. Record Failed Compression Bytes/sec is the rate of record bytes that either failed Xpress compression or did not significantly reduce the insert/replace size (10% or less). High results are indicative of wasted cpu resources.  [Dev Only]
2595. 4305
2596. Microsoft Distributed Transaction Coordinator performance counters
2597. 4307
2598. Number of currently active transactions
2599. 4309
2600. Number of committed transactions
2601. 4311
2602. Number of aborted transactions
2603. 4313
2604. Number of in doubt transactions
2605. 4315
2606. Maximum number of transactions ever concurrently active
2607. 4317
2608. Number of transactions committed by the system administrator
2609. 4319
2610. Number of transactions aborted by the system administrator
2611. 4321
2612. Minimum time delta between transaction begin and commit
2613. 4323
2614. Average time delta between transaction begin and commit
2615. 4325
2616. Maximum time delta between transaction begin and commit
2617. 4327
2618. Transactions performed per second
2619. 4329
2620. Transactions committed per second
2621. 4331
2622. Transactions aborted per second
2623. 4333
2624. Terminal Services per-session resource monitoring.
2625. 4335
2626. Number of bytes input on this session after all protocol overhead has been removed.
2627. 4337
2628. The number of frames input after any additional protocol added frames have been removed.
2629. 4339
2630. The number of times that a wait for an available send buffer was done by the protocols on the client side of the connection.
2631. 4341
2632. Number of frames (packets) input on this Session.
2633. 4343
2634. Number of bytes input on this session that includes all protocol overhead.
2635. 4345
2636. Number of bytes input after compression. This number compared with the Total Bytes input is the compression ratio.
2637. 4347
2638. Number of input compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transferring compressed files over Client Drive Mapping.
2639. 4349
2640. Number of input errors of all types. Some example input errors are lost ACK's, badly formed packets, etc.
2641. 4351
2642. The total number of timeouts on the communication line as seen from the client side of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions.
2643. 4353
2644. Number of input async framing errors. These can be caused by a noisy transmission line. Using a smaller packet size may help in some cases.
2645. 4355
2646. Number of input async overrun errors. These can be caused by the baud rate being faster than the computer can handle, or a non-16550 serial line is used. Overruns can also occur if too many high speed serial lines are active at one time for the processor's power.
2647. 4357
2648. Number of input async overflow errors. These can be caused by a lack of buffer space available on the host.
2649. 4359
2650. Number of input async parity errors. These can be caused by a noisy transmission line
2651. 4361
2652. Number of Terminal Services transport-level errors on input.
2653. 4363
2654. Number of bytes output on this session after all protocol overhead has been removed.
2655. 4365
2656. The number of frames output before any additional protocol frames have been added.
2657. 4367
2658. This is the number of times that a wait for an available send buffer was done by the protocol on the server side of the connection.
2659. 4369
2660. Number of frames (packets) output on this session.
2661. 4371
2662. Number of bytes output on this Session that includes all protocol overhead.
2663. 4373
2664. Number of bytes output after compression. This number compared with the Total Bytes output is the compression ratio.
2665. 4375
2666. Number of output compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transfering compressed files over Client Drive Mapping.
2667. 4377
2668. Number of output errors of all types. Some example output errors are lost ACK's, badly formed packets, etc.
2669. 4379
2670. The total number of timeouts on the communication line from the host side of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions.
2671. 4381
2672. Number of output async framing errors. This could be caused by a hardware or line problem.
2673. 4383
2674. Number of output async overrun errors.
2675. 4385
2676. Number of output async overflow errors.
2677. 4387
2678. Number of output async parity errors. These can be caused by a hardware or line problem.
2679. 4389
2680. Number of Terminal Services transport-level errors on output.
2681. 4391
2682. Total number of bytes on this Session after all protocol overhead has been removed.
2683. 4393
2684. The total number of frames input and output before any additional protocol frames have been added.
2685. 4395
2686. The number of times that a wait for an available send buffer was done by the protocols on both the server and client sides of the connection.
2687. 4397
2688. Total number of frames (packets) on this Session.
2689. 4399
2690. Total number of bytes on this Session that includes all protocol overhead.
2691. 4401
2692. Total number of bytes after compression. This number compared with the total bytes is the compression ratio.
2693. 4403
2694. Total number of compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transfering compressed files over Client Drive Mapping.
2695. 4405
2696. Total number of errors of all types. Some example errors are lost ACK's, badly formed packets, etc.
2697. 4407
2698. The total number of timeouts on the communication line from both the host and client sides of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions.
2699. 4409
2700. Total number of async framing errors. These can be caused by a noisy transmission line. Using a smaller packet size may help in some cases.
2701. 4411
2702. Total number of async overrun errors. These can be caused by the baud rate being faster than the computer can handle, or a non-16550 serial line is used. Overruns can also occur if too many high speed serial lines are active at one time for the processor's power.
2703. 4413
2704. Total number of async overflow errors. These can be caused by a lack of buffer space available on the host.
2705. 4415
2706. Total number of async parity errors. These can be caused by a noisy transmission line.
2707. 4417
2708. Total number of Terminal Services transport-level errors.
2709. 4419
2710. Total references to all protocol caches.
2711. 4421
2712. Total hits in all protocol caches. The protocol caches Windows objects that are likely to be re-used to avoid having to re-send them on the transmission line. Example objects are Windows icons and brushes. Hits in the cache represent objects that did not need to be re-sent.
2713. 4423
2714. Overall hit ratio for all protocol caches.
2715. 4425
2716. Number of references to the protocol bitmap cache.
2717. 4427
2718. Number of hits in the protocol bitmap cache.
2719. 4429
2720. Hit ratio in the protocol bitmap cache. A higher hit ratio means better performance since data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.
2721. 4431
2722. Number of references to the protocol glyph cache.
2723. 4433
2724. Number of hits in the protocol glyph cache.
2725. 4435
2726. Hit ratio in the protocol glyph cache. A higher hit ratio means better performance since data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.
2727. 4437
2728. Number of references to the protocol brush cache.
2729. 4439
2730. Number of hits in the protocol brush cache.
2731. 4441
2732. Hit ratio in the protocol brush cache. A higher hit ratio means better performance since data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.
2733. 4443
2734. Number of references to the protocol save screen bitmap cache.
2735. 4445
2736. Number of hits in the protocol save screen bitmap cache.
2737. 4447
2738. Hit ratio in the protocol save screen bitmap cache. A higher hit ratio means better performance since data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.
2739. 4449
2740. Compression ratio of the server input data stream.
2741. 4451
2742. Compression ratio of the server output data stream.
2743. 4453
2744. Total compression ratio of the server data stream.
2745. 4951
2746. Displays the current bulk transfer rate in bytes/sec.
2747. 4953
2748. Displays the current isochronous transfer rate in bytes/sec.
2749. 4955
2750. Displays the current interrupt transfer rate in bytes/sec.
2751. 4957
2752. Displays the current control transfer rate in bytes/sec.
2753. 4959
2754. Displays the rate of PCI interrupt generation by the USB controller. For controller instances only.
2755. 4961
2756. Displays the current rate Work Signals generated per second by the usbport driver.  For controller instances only.
2757. 4963
2758. Displays the percentage of BW reserved for interrupt transfers
2759. 4965
2760. Displays the percentage of BW reserved for ISO transfers
2761. 4967
2762. USB I/O Counters
2763. 4969
2764. Displays the average size of all transfer URBs. For device instances only.
2765. 4971
2766. Number of ISO packets that are NOT late, but complete with an error. For device instances only.
2767. 4973
2768. Avg number of ms between the current frame and the start frame of an ISO transfer when scheduled.  For device instances only.
2769. 4975
2770. Number of Transfer URBs completing with an error status. For device instances only.
2771. 4977
2772. Non-zero value if the host controller is not running(idle).
2773. 4979
2774. Non-Zero value if the host controller async schedule is not running(idle).
2775. 4981
2776. Incremented each time the controller async cache is flushed.
2777. 4983
2778. Non-Zero if the periodic schedule is not running(idle).
2779. 4985
2780. Incremented each time the controller periodic cache is flushed.
2781. 4987
2782. Help not available.
2783. 4989
2784. The cumulative total number of socket connections established for this process since the process was started.
2785. 4991
2786. The 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.
2787. 4993
2788. The 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.
2789. 4995
2790. The cumulative total number of datagram packets received since the process was started.
2791. 4997
2792. The cumulative total number of datagram packets sent since the process was started.
2793. 4999
2794. Counters for System.Data.SqlClient
2795. 5001
2796. The number of actual connections per second that are being made to servers
2797. 5003
2798. The number of actual disconnects per second that are being made to servers
2799. 5005
2800. The number of connections we get from the pool per second
2801. 5007
2802. The number of connections we return to the pool per second
2803. 5009
2804. The number of connections that are not using connection pooling
2805. 5011
2806. The number of connections that are managed by the connection pooler
2807. 5013
2808. The number of unique connection strings
2809. 5015
2810. The number of unique connection strings waiting for pruning
2811. 5017
2812. The number of active connection pools
2813. 5019
2814. The number of inactive connection pools
2815. 5021
2816. The number of connections currently in-use
2817. 5023
2818. The number of connections currently available for use
2819. 5025
2820. The number of connections currently waiting to be made ready for use
2821. 5027
2822. The number of connections we reclaim from GCed external connections
2823. 5029
2824. .Net CLR Data
2825. 5031
2826. Current number of connections, pooled or not.
2827. 5033
2828. Current number of connections in all pools associated with the process.
2829. 5035
2830. Current number of pools associated with the process.
2831. 5037
2832. The highest number of connections in all pools since the process started.
2833. 5039
2834. The total number of connection open attempts that have failed for any reason.
2835. 5041
2836. The total number of command executes that have failed for any reason.
2837. 5043
2838. Counters for CLR Garbage Collected heap.
2839. 5045
2840. This 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.
2841. 5047
2842. This 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.
2843. 5049
2844. This 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.
2845. 5051
2846. This 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.
2847. 5053
2848. This 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.
2849. 5055
2850. This 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.
2851. 5057
2852. This 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.
2853. 5059
2854. This 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.
2855. 5061
2856. This counter displays the process ID of the CLR process instance being monitored.
2857. 5063
2858. This 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.
2859. 5065
2860. This 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.
2861. 5067
2862. This 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.
2863. 5069
2864. This counter displays the current size of the Large Object Heap in bytes. Objects greater than 20 KBytes are treated as large objects by the Garbage Collector and are directly allocated in a special heap; they are not promoted through the generations. This counter is updated at the end of a GC; its not updated on every allocation.
2865. 5071
2866. This 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.
2867. 5073
2868. This 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.
2869. 5075
2870. This 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.
2871. 5077
2872. This 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.
2873. 5079
2874. % 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.
2875. 5081
2876. Not Displayed.
2877. 5083
2878. This 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.
2879. 5085
2880. This 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).
2881. 5087
2882. This 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.)
2883. 5089
2884. This 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.
2885. 5091
2886. This 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.
2887. 5093
2888. Statistics for CLR Class Loader.
2889. 5095
2890. This counter displays the cumulative number of classes loaded in all Assemblies since the start of this application.
2891. 5097
2892. Reserved for future use.
2893. 5099
2894. Reserved for future use.
2895. 5101
2896. This 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.
2897. 5103
2898. This 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.
2899. 5105
2900. This 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.)
2901. 5107
2902. This 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.
2903. 5109
2904. This 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.
2905. 5111
2906. This counter displays the current number of classes loaded in all Assemblies.
2907. 5113
2908. This 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.
2909. 5115
2910. This 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.
2911. 5117
2912. This 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.
2913. 5119
2914. This 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.
2915. 5121
2916. This 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.
2917. 5123
2918. This 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.
2919. 5125
2920. This 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.
2921. 5127
2922. Stats for CLR Jit.
2923. 5129
2924. This 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.
2925. 5131
2926. This 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.
2927. 5133
2928. This 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.
2929. 5135
2930. This 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.
2931. 5137
2932. This 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.
2933. 5139
2934. This 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.
2935. 5141
2936. Not Displayed.
2937. 5143
2938. Stats for CLR interop.
2939. 5145
2940. This 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.
2941. 5147
2942. This 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.
2943. 5149
2944. This 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.
2945. 5151
2946. Reserved for future use.
2947. 5153
2948. Reserved for future use.
2949. 5155
2950. Stats for CLR Locks and Threads.
2951. 5157
2952. This 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.
2953. 5159
2954. Rate 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.
2955. 5161
2956. This 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.
2957. 5163
2958. This counter displays the total number of threads that waited to acquire some managed lock since the start of the application.
2959. 5165
2960. This 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.
2961. 5167
2962. This 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.
2963. 5169
2964. This 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.
2965. 5171
2966. This 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.
2967. 5173
2968. This 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.
2969. 5175
2970. This 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.
2971. 5177
2972. Stats for CLR Security.
2973. 5179
2974. This 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.
2975. 5181
2976. Reserved for future use.
2977. 5183
2978. This 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.
2979. 5185
2980. This 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.
2981. 5187
2982. Not Displayed.
2983. 5189
2984. This 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.
2985. 5191
2986. Stats for CLR Remoting.
2987. 5193
2988. This 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.
2989. 5195
2990. This 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.
2991. 5197
2992. This 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.
2993. 5199
2994. This 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.
2995. 5201
2996. This 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.
2997. 5203
2998. This 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.
2999. 5205
3000. This 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.
3001. 5207
3002. Runtime statistics on CLR exception handling.
3003. 5209
3004. This 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.
3005. 5211
3006. This 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.
3007. 5213
3008. This 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.
3009. 5215
3010. This 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.
3011. 5217
3012. This 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.
3013. 5219
3014. Counters for System.Data.OracleClient
3015. 5221
3016. The number of actual connections per second that are being made to servers
3017. 5223
3018. The number of actual disconnects per second that are being made to servers
3019. 5225
3020. The number of connections we get from the pool per second
3021. 5227
3022. The number of connections we return to the pool per second
3023. 5229
3024. The number of connections that are not using connection pooling
3025. 5231
3026. The number of connections that are managed by the connection pooler
3027. 5233
3028. The number of unique connection strings
3029. 5235
3030. The number of unique connection strings waiting for pruning
3031. 5237
3032. The number of active connection pools
3033. 5239
3034. The number of inactive connection pools
3035. 5241
3036. The number of connections currently in-use
3037. 5243
3038. The number of connections currently available for use
3039. 5245
3040. The number of connections currently waiting to be made ready for use
3041. 5247
3042. The number of connections we reclaim from GCed external connections
3043. 5355
3044. Counters for the Windows Search Service Gatherer Project object
3045. 5357
3046. The number of add notifications.
3047. 5359
3048. The number of document additions per second.
3049. 5361
3050. The number of delete notifications.
3051. 5363
3052. The number of document deletes per second.
3053. 5365
3054. The number of modify notifications.
3055. 5367
3056. The number of modify notifications per second.
3057. 5369
3058. The 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.
3059. 5371
3060. The number of documents in progress.
3061. 5373
3062. The number of documents on hold because a document with the same URL is currently in process.
3063. 5375
3064. The number of documents delayed due to site hit frequency rules.
3065. 5377
3066. The number of files (URLs) in the history list. This indicates the total size of your document corpus that was indexed.
3067. 5379
3068. The number of documents processed since the history has been reset.
3069. 5381
3070. The number of documents processed per second.
3071. 5383
3072. The number of successfully filtered documents.
3073. 5385
3074. The number of successfully filtered documents per second.
3075. 5387
3076. The number of filtered documents which returned an error.
3077. 5389
3078. The number of filtered documents which returned an error per second.
3079. 5395
3080. The number of file protocol errors received while getting documents.
3081. 5397
3082. The number of file protocol errors received per second.
3083. 5403
3084. The number of documents accessed via file system.
3085. 5405
3086. The number of documents accessed via file system per second.
3087. 5411
3088. The number of office documents filtered.
3089. 5413
3090. The number of office documents filtered per second.
3091. 5415
3092. The number of text documents filtered.
3093. 5417
3094. The number of text documents filtered per second.
3095. 5419
3096. Number of crawls in progress.
3097. 5421
3098. The Gatherer paused flag indicates if the Gatherer has been paused.
3099. 5423
3100. The recovery in progress flag indicates if recovery is currently in progress. Indexing will not be resumed until this flag is off.
3101. 5425
3102. The number of documents which were not filtered because no modification was detected since the last crawl.
3103. 5427
3104. The Iterating history in progress flag indicates if the Gatherer is currently iterating over the URL history.
3105. 5429
3106. Number of incremental crawls in progress.
3107. 5431
3108. The number of documents currently being filtered.
3109. 5433
3110. The 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.
3111. 5435
3112. The total number of times a document access has been retried. Having this number high may indicate a problem with accessing the data.
3113. 5437
3114. The number of retries per second.
3115. 5445
3116. Documents incorrectly rejected by adaptive crawl
3117. 5451
3118. Documents which have changed since the last crawl
3119. 5453
3120. The number of Move/Rename notifications.
3121. 5455
3122. The number of document Moves and Renames per second.
3123. 5457
3124. Number of unique documents in the system. Documents are considered not unique if their contents is the same.
3125. 5459
3126. Percentage of the history recovery completed
3127. 5461
3128. Counters for the Windows Search Service Gathering service object
3129. 5463
3130. Currently connected external notification sources.
3131. 5465
3132. The total number of notifications received from all notification sources excluding file system.
3133. 5467
3134. The rate of external notifications received per second.
3135. 5469
3136. The number of currently connected administrative clients.
3137. 5471
3138. The 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.
3139. 5473
3140. Displays one heartbeat every 10 seconds.
3141. 5475
3142. The total number of filtering threads in the system. This number is calculated based on your system resources.
3143. 5477
3144. The number of threads waiting for documents.
3145. 5479
3146. The number of document entries currently in memory. Zero means no indexing activity is going on.
3147. 5481
3148. Indicates the level of the amount of system resources that the Gatherer service is allowed to use.
3149. 5483
3150. The number of documents waiting for robot threads. If this number is not 0, all threads should be filtering.
3151. 5485
3152. The number of filtering processes in the system.
3153. 5487
3154. The maximum number of filtering processes that have existed in the system since startup.
3155. 5489
3156. The 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.
3157. 5491
3158. The number of documents delayed due to site hit frequency rules.
3159. 5493
3160. The number of servers recently accessed by the system.
3161. 5495
3162. The number of times a new server object had to be created.
3163. 5497
3164. The number of filter objects in the system. Each filter object corresponds to a URL currently being filtered.
3165. 5499
3166. The number of times a filter object was created. This corresponds to the total number of documents filtered in the system since startup.
3167. 5501
3168. The number of documents filtered per second.
3169. 5503
3170. The total number of timeouts detected by the system since startup.
3171. 5505
3172. A server becomes unavailable when a number of requests to that server time out.
3173. 5507
3174. A server becomes unavailable when a number of requests to that server time out.
3175. 5509
3176. The 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.
3177. 5511
3178. The number of threads waiting for plug-ins to complete an operation.
3179. 5513
3180. The number of documents successfully filtered.
3181. 5515
3182. The number of successfully filtered documents per second.
3183. 5517
3184. The 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.
3185. 5519
3186. Number of available cached word breakers instances
3187. 5521
3188. Number of available cached stemmer instances. Too many may indicate a resource usage problem.
3189. 5523
3190. The total number of notifications received from all notification sources including file system.
3191. 5525
3192. The rate of external notifications received per second.
3193. 5527
3194. System IO (disk) traffic rate in KB/s detected by back off logic
3195. 5529
3196. The 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.
3197. 5531
3198. The number of threads blocked due to back off event
3199. 5533
3200. Indexer PlugIn statistics
3201. 5535
3202. The level of the master index.
3203. 5537
3204. Number of Master Merges to Date
3205. 5539
3206. Master Merge Progress
3207. 5541
3208. Shadow Merge Levels
3209. 5543
3210. Shadow Merge Levels Threshold
3211. 5545
3212. Number of Persistent Indexes
3213. 5547
3214. Size of Index
3215. 5549
3216. Number of Unique Keys
3217. 5551
3218. Number of Documents Filtered
3219. 5553
3220. Number of invalidator work items that were created
3221. 5555
3222. Number of invalidator work items that were deleted
3223. 5557
3224. Number of clean WidSets
3225. 5559
3226. Number of dirty WidSets
3227. 5561
3228. Indicator if a master merge is going on.
3229. 5563
3230. Active Connections
3231. 5565
3232. Number of Queries
3233. 5567
3234. Number of Queries Failed
3235. 5569
3236. Number of Queries Succeeded
3237. 5571
3238. The number of L0 Indexes (Wordlists)
3239. 5573
3240. The number of L0 merges (flushes) in progress at any one moment.
3241. 5575
3242. The average value [documents/hour] computed for the speed of L0 merges (flushes) since the catalog has been loaded
3243. 5577
3244. The number of L0 merges (flushes) since the catalog was loaded
3245. 5579
3246. The last value [documents/hour] computed for the speed of L0 merges (flushes).
3247. 5581
3248. The number of L1 Indexes
3249. 5583
3250. The number of L1 merges in progress at any one moment.
3251. 5585
3252. The average value [documents/hour] computed for the speed of L1 merges since the catalog has been loaded
3253. 5587
3254. The number of L1 merges since the catalog was loaded
3255. 5589
3256. The last value [documents/hour] computed for the speed of L1 merges.
3257. 5591
3258. The number of L2 Indexes
3259. 5593
3260. The number of L2 merges in progress at any one moment.
3261. 5595
3262. The average value [documents/hour] computed for the speed of L2 merges since the catalog has been loaded
3263. 5597
3264. The number of L2 merges since the catalog was loaded
3265. 5599
3266. The last value [documents/hour] computed for the speed of L2 merges.
3267. 5601
3268. The number of L3 Indexes
3269. 5603
3270. The number of L3 merges in progress at any one moment.
3271. 5605
3272. The average value [documents/hour] computed for the speed of L3 merges since the catalog has been loaded
3273. 5607
3274. The number of L3 merges since the catalog was loaded
3275. 5609
3276. The last value [documents/hour] computed for the speed of L3 merges.
3277. 5611
3278. The number of L4 Indexes
3279. 5613
3280. The number of L4 merges in progress at any one moment.
3281. 5615
3282. The average value [documents/hour] computed for the speed of L4 merges since the catalog has been loaded
3283. 5617
3284. The number of L4 merges since the catalog was loaded
3285. 5619
3286. The last value [documents/hour] computed for the speed of L4 merges.
3287. 5621
3288. The number of L5 Indexes
3289. 5623
3290. The number of L5 merges in progress at any one moment.
3291. 5625
3292. The average value [documents/hour] computed for the speed of L5 merges since the catalog has been loaded
3293. 5627
3294. The number of L5 merges since the catalog was loaded
3295. 5629
3296. The last value [documents/hour] computed for the speed of L5 merges.
3297. 5631
3298. The number of L6 Indexes
3299. 5633
3300. The number of L6 merges in progress at any one moment.
3301. 5635
3302. The average value [documents/hour] computed for the speed of L6 merges since the catalog has been loaded
3303. 5637
3304. The number of L6 merges since the catalog was loaded
3305. 5639
3306. The last value [documents/hour] computed for the speed of L6 merges.
3307. 5641
3308. The number of L7 Indexes
3309. 5643
3310. The number of L7 merges in progress at any one moment.
3311. 5645
3312. The average value [documents/hour] computed for the speed of L7 merges since the catalog has been loaded
3313. 5647
3314. The number of L7 merges since the catalog was loaded
3315. 5649
3316. The last value [documents/hour] computed for the speed of L7 merges.
3317. 5651
3318. The number of L8 Indexes
3319. 5653
3320. The number of L8 merges in progress at any one moment.
3321. 5655
3322. The average value [documents/hour] computed for the speed of L8 merges since the catalog has been loaded
3323. 5657
3324. The number of L8 merges since the catalog was loaded
3325. 5659
3326. The last value [documents/hour] computed for the speed of L8 merges.
3327. 5661
3328. Displays performance statistics about ReadyBoost Caches.
3329. 5663
3330. The total (uncompressed) amount of data currently stored in ReadyBoost caches.
3331. 5665
3332. Amount of space in bytes taken by data cached in ReadyBoost caches.
3333. 5667
3334. (Cache space used) / (Bytes cached)
3335. 5669
3336. Total size, in bytes, of all caches regardless of how much data they contain.
3337. 5671
3338. Number of I/Os satisfied from ReadyBoost caches per second.
3339. 5673
3340. Bytes of I/Os satisfied from ReadyBoost caches per second.
3341. 5675
3342. Number of read I/Os ignored by ReadyBoost due to policy.
3343. 5677
3344. Bytes of read I/Os ignored by ReadyBoost due to policy.
3345. 5679
3346. Number of read I/Os that are received by ReadyBoost. This counter includes all reads whether or not they were satisfied by ReadyBoost caches.
3347. 5681
3348. Bytes of read I/Os that are received by ReadyBoost. This counter includes all reads whether or not they were satisfied by ReadyBoost caches.
3349. 5909
3350. Windows Workflow Foundation Performance Counters
3351. 5911
3352. Total number of workflows created.
3353. 5913
3354. Rate of workflows created per second.
3355. 5915
3356. Total number of workflows unloaded.
3357. 5917
3358. Rate of workflows unloaded per second.
3359. 5919
3360. Total number of workflows loaded.
3361. 5921
3362. Rate of workflows loaded per second.
3363. 5923
3364. Total number of workflows completed.
3365. 5925
3366. Rate of workflows completed per second.
3367. 5927
3368. Total number of workflows suspended.
3369. 5929
3370. Rate of workflows suspended per second.
3371. 5931
3372. Total number of workflows terminated.
3373. 5933
3374. Rate of workflows terminated per second.
3375. 5935
3376. Total number of workflows in memory.
3377. 5937
3378. Total number of workflows aborted.
3379. 5939
3380. Rate of workflows aborted per second.
3381. 5941
3382. Total number of workflows persisted.
3383. 5943
3384. Rate of workflows persisted per second.
3385. 5945
3386. Total number of workflow instances actively executing.
3387. 5947
3388. Rate of workflows becoming idle per second.
3389. 5949
3390. Total number of workflows ready to execute.
3391. 5951
3392. Total number of workflows waiting for a thread.
3393. 5953
3394. ServiceModelEndpoint 3.0.0.0 performance counters
3395. 5955
3396. The number of calls to this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.Calls.aspx
3397. 5957
3398. The number of calls to this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsPerSecond.aspx
3399. 5959
3400. The number of calls to this endpoint that are in progress. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsOutstanding.aspx
3401. 5961
3402. The number of calls with unhandled exceptions at this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFailed.aspx
3403. 5963
3404. The number of calls with unhandled exceptions at this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFailedPerSecond.aspx
3405. 5965
3406. The number of calls to this endpoint that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFaulted.aspx
3407. 5967
3408. The number of calls to this endpoint that returned faults per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFaultedPerSecond.aspx
3409. 5969
3410. The average duration of calls to this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallDuration.aspx
3411. 5971
3412. Base counter for the 'Calls Duration' counter.
3413. 5973
3414. The number of transactions that flowed to operations at this endpoint. This counter is incremented any time a transaction ID is present in the message that is sent to the endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.TxFlowed.aspx
3415. 5975
3416. The number of transactions that flowed to operations at this endpoint per second. This counter is incremented any time a transaction ID is present in the message that is sent to the endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.TxFlowedPerSecond.aspx
3417. 5977
3418. The number of calls to this endpoint that failed validation or authentication. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityValidationAuthenticationFailures.aspx
3419. 5979
3420. The number of calls to this endpoint that failed validation or authentication per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityValidationAuthenticationFailuresPerSecond.aspx
3421. 5981
3422. The number of calls to this endpoint that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityCallsNotAuthorized.aspx
3423. 5983
3424. The number of calls to this endpoint that failed authorization per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityCallsNotAuthorizedPerSecond.aspx
3425. 5985
3426. The number of reliable messaging sessions that faulted at this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.RMSessionsFaulted.aspx
3427. 5987
3428. The number of reliable messaging sessions that faulted at this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.RMSessionsFaultedPerSecond.aspx
3429. 5989
3430. The number of reliable messaging messages that were dropped at this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.RMMessagesDropped.aspx
3431. 5991
3432. The number of reliable messaging messages that were dropped at this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.RMMessagesDroppedPerSecond.aspx
3433. 6047
3434. ServiceModelService 3.0.0.0 performance counters
3435. 6049
3436. The number of calls to this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.Calls.aspx
3437. 6051
3438. The number of calls to this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsPerSecond.aspx
3439. 6053
3440. The number of calls to this service that are in progress. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsOutstanding.aspx
3441. 6055
3442. The number of calls with unhandled exceptions in this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFailed.aspx
3443. 6057
3444. The number of calls with unhandled exceptions in this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFailedPerSecond.aspx
3445. 6059
3446. The number of calls to this service that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFaulted.aspx
3447. 6061
3448. The number of calls to this service that returned faults per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFaultedPerSecond.aspx
3449. 6063
3450. The average duration of calls to this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallDuration.aspx
3451. 6065
3452. Base counter for the 'Calls Duration' counter.
3453. 6067
3454. The number of transactions that flowed to operations in this service. This counter is incremented any time a transaction ID is present in the message that is sent to the service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxFlowed.aspx
3455. 6069
3456. The number of transactions that flowed to operations in this service per second. This counter is incremented any time a transaction ID is present in the message that is sent to the service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxFlowedPerSecond.aspx
3457. 6071
3458. The number of transacted operations with the outcome committed in this service. Work done under such operations is fully committed. Resources are updated in accordance with the work done in the operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxCommitted.aspx
3459. 6073
3460. The number of transacted operations with the outcome committed in this service per second. Work done under such operations is fully committed. Resources are updated in accordance with the work done in the operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxCommittedPerSecond.aspx
3461. 6075
3462. The number of transacted operations with the outcome aborted in this service. Work done under such operations is rolled back. Resources are reverted to their previous state. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxAborted.aspx
3463. 6077
3464. The number of transacted operations with the outcome aborted in this service per second. Work done under such operations is rolled back. Resources are reverted to their previous state. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxAbortedPerSecond.aspx
3465. 6079
3466. The number of transacted operations with an outcome in doubt in this service. Work done with an outcome in doubt is in an indeterminate state. Resources are held pending outcome. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxInDoubt.aspx
3467. 6081
3468. The number of transacted operations with an outcome in doubt in this service per second. Work done with an outcome in doubt is in an indeterminate state. Resources are held pending outcome. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.TxInDoubtPerSecond.aspx
3469. 6083
3470. The number of calls to this service that failed validation or authentication. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityValidationAuthenticationFailures.aspx
3471. 6085
3472. The number of calls to this service that failed validation or authentication per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityValidationAuthenticationFailuresPerSecond.aspx
3473. 6087
3474. The number of calls to this service that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityCallsNotAuthorized.aspx
3475. 6089
3476. The number of calls to this service that failed authorization per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityCallsNotAuthorizedPerSecond.aspx
3477. 6091
3478. The total number of instances of the service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.Instances.aspx
3479. 6093
3480. The creation rate of service instances per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.InstancesPerSecond.aspx
3481. 6095
3482. The number of reliable messaging sessions that were faulted in this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.RMSessionsFaulted.aspx
3483. 6097
3484. The number of reliable messaging sessions that were faulted in this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.RMSessionsFaultedPerSecond.aspx
3485. 6099
3486. The number of reliable messaging messages that were dropped in this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.RMMessagesDropped.aspx
3487. 6101
3488. The number of reliable messaging messages that were dropped in this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.RMMessagesDroppedPerSecond.aspx
3489. 6103
3490. The number of messages to this service that were marked poisoned by the queued transport. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqPoisonMessages.aspx
3491. 6105
3492. The number of messages to this service that were marked poisoned by the queued transport per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqPoisonMessagesPerSecond.aspx
3493. 6107
3494. The number of messages to this servcie that were rejected by the queued transport. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqRejectedMessages.aspx
3495. 6109
3496. The number of messages to this service that were rejected by the queued transport per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqRejectedMessagesPerSecond.aspx
3497. 6111
3498. The number of messages to this service that were dropped by the queued transport. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqDroppedMessages.aspx
3499. 6113
3500. The number of messages to this service that were dropped by the queued transport per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.MsmqDroppedMessagesPerSecond.aspx
3501. 6115
3502. ServiceModelOperation 3.0.0.0 performance counters
3503. 6117
3504. The number of calls to this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.Calls.aspx
3505. 6119
3506. The number of calls to this operation per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsPerSecond.aspx
3507. 6121
3508. The number of calls to this operation that are in progress. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsOutstanding.aspx
3509. 6123
3510. The number of calls with unhandled exceptions in this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFailed.aspx
3511. 6125
3512. The number of calls with unhandled exceptions in this operation per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFailedPerSecond.aspx
3513. 6127
3514. The number of calls to this operation that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFaulted.aspx
3515. 6129
3516. The number of calls to this operation that returned faults per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFaultedPerSecond.aspx
3517. 6131
3518. The average duration of calls to this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallDuration.aspx
3519. 6133
3520. Base counter for the 'Calls Duration' counter.
3521. 6135
3522. The number of transactions that flowed to this operation. This counter is incremented any time a transaction ID is present in the message sent to the operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.TxFlowed.aspx
3523. 6137
3524. The number of transactions that flowed to this operation per second. This counter is incremented any time a transaction ID is present in the message sent to the operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.TxFlowedPerSecond.aspx
3525. 6139
3526. The number of calls to this operation that failed validation or authentication. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityValidationAuthenticationFailures.aspx
3527. 6141
3528. The number of calls to this operation that failed validation or authentication per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityValidationAuthenticationFailuresPerSecond.aspx
3529. 6143
3530. The number of calls to this operation that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityCallsNotAuthorized.aspx
3531. 6145
3532. The number of calls to this operation that failed authorization per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityCallsNotAuthorizedPerSecond.aspx
3533. 6147
3534. SMSvcHost 3.0.0.0 performance counters
3535. 6149
3536. The total number of failures at the protocol layer of net.tcp.
3537. 6151
3538. The total number of failures at the protocol layer of net.pipe.
3539. 6153
3540. The total number of failures dispatching messages received over net.tcp.
3541. 6155
3542. The total number of failures dispatching messages received over net.pipe.
3543. 6157
3544. The total number of connections dispatched over net.tcp.
3545. 6159
3546. The total number of connections dispatched over net.pipe.
3547. 6161
3548. The total number of TCP connections accepted over net.tcp.
3549. 6163
3550. The total number of named pipe connections accepted over net.pipe.
3551. 6165
3552. The number of uri registrations currently active for net.tcp.
3553. 6167
3554. The number of uri registrations currently active for net.pipe.
3555. 6169
3556. The total number of uris that were succesfully registered for net.tcp.
3557. 6171
3558. The total number of uris that were succesfully registered for net.pipe.
3559. 6173
3560. The total number of uris that were succesfully unregistered for net.tcp.
3561. 6175
3562. The total number of uris that were succesfully unregistered for net.pipe.
3563. 6177
3564. MSDTC Bridge 3.0.0.0 performance counters
3565. 6179
3566. The number of WS-AT protocol messages that the WS-AT service failed to send per second.
3567. 6181
3568. The number of Prepare retry messages that the WS-AT service has sent per second.
3569. 6183
3570. The number of Commit retry messages that the WS-AT service has sent per second.
3571. 6185
3572. The number of Prepared retry messages that the WS-AT service has sent per second.
3573. 6187
3574. The number of Replay retry messages that the WS-AT service has sent per second.
3575. 6189
3576. The number of Fault messages that the WS-AT service has received per second.
3577. 6191
3578. The number of Fault messages that the WS-AT service has sent per second.
3579. 6193
3580. Average time in milliseconds for the WS-AT service to receive a Prepare message response from a participant.
3581. 6195
3582. Base counter for the 'Average participant prepare response time' counter.
3583. 6197
3584. Average time in milliseconds for the WS-AT service to receive a Commit message response from a participant.
3585. 6199
3586. Base counter for the 'Average participant commit response time' counter.
3587. 6369
3588. System.Runtime.Caching.MemoryCache Performance Counters
3589. 6371
3590. The number of cache hits.
3591. 6373
3592. The number of cache misses.
3593. 6375
3594. The percentage of cache hits in the total number of cache requests.
3595. 6377
3596. Cache Hit Ratio Base
3597. 6379
3598. Total number of entries removed from the cache due to memory pressure or Trim invocations.
3599. 6381
3600. The number of entries within the cache.
3601. 6383
3602. The number of entries added to the cache or removed from the cache per second.
3603. 6619
3604. ASP.NET global performance counters
3605. 6621
3606. ASP.NET application performance counters
3607. 6623
3608. Number of times the application has been restarted during the web server's lifetime.
3609. 6625
3610. Number of currently running web applications.
3611. 6627
3612. The number of requests disconnected due to communication errors or user terminated.
3613. 6629
3614. The number of milliseconds that it took to execute the most recent request.
3615. 6631
3616. The number of requests rejected because the request queue was full.
3617. 6633
3618. The number of requests waiting to be processed.
3619. 6635
3620. Number of worker processes running on the machine.
3621. 6637
3622. Number of times a worker process has restarted on the machine.
3623. 6639
3624. The number of milliseconds the most recent request was waiting in the queue.
3625. 6641
3626. The current number of sessions currently active.
3627. 6643
3628. The number of sessions that have been explicitly abandoned.
3629. 6645
3630. The number of sessions timed out.
3631. 6647
3632. The number of sessions total.
3633. 6649
3634. The current number of requests, including those that are queued, currently executing, or waiting to be written to the client.  Under the ASP.NET process model, when this counter exceeds the requestQueueLimit defined in the processModel configuration section, ASP.NET will begin rejecting requests.
3635. 6651
3636. Number of audit successes in the application since it was started.
3637. 6653
3638. Number of audit failures in the application since it was started.
3639. 6655
3640. Number of error events raised since the application was started.
3641. 6657
3642. Number of runtime error events raised since the application was started.
3643. 6659
3644. Number of HTTP error events raised since the application was started.
3645. 6661
3646. Requests queued because the concurrency limits have been exceeded.
3647. 6663
3648. Number of requests utilizing anonymous authentication.
3649. 6665
3650. Number of Authentication Anonymous Requests/Sec
3651. 6667
3652. Total number of entries within the cache (both internal and user added)
3653. 6669
3654. Number of additions and removals to the total cache per second.
3655. 6671
3656. Total number of hits from the cache.
3657. 6673
3658. Total number of cache misses.
3659. 6675
3660. Ratio of hits from all cache calls.
3661. 6677
3662. Cache Total Hit Ratio Base
3663. 6679
3664. Total number of entries within the cache added by the user.
3665. 6681
3666. Number of additions and removals to the API cache per second.
3667. 6683
3668. Number of cache hits from user code.
3669. 6685
3670. Number of cache misses called from user code.
3671. 6687
3672. Ratio of hits called from user code.
3673. 6689
3674. Cache API Hit Ratio Base
3675. 6691
3676. Current number of entries in the output cache.
3677. 6693
3678. Number of additions and removals to the output cache per second.
3679. 6695
3680. Total number of output cacheable requests served from the output cache.
3681. 6697
3682. Total number of output cacheable requests not served from the output cache.
3683. 6699
3684. Ratio of hits to requests for output cacheable requests.
3685. 6701
3686. Output Cache Hit Ratio Base
3687. 6703
3688. Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled.
3689. 6705
3690. Number of debugging requests processed.
3691. 6707
3692. Number of errors that have occurred during parsing and configuration.
3693. 6709
3694. Number of errors that have occurred during compilation.
3695. 6711
3696. Number of errors that have occurred during the processing of a request.
3697. 6713
3698. Number of errors not handled by user code, but by the default error handler.
3699. 6715
3700. Rate of unhandled errors.
3701. 6717
3702. Total number of errors occurred.
3703. 6719
3704. Rate of errors occurred.
3705. 6721
3706. Number of active pipeline instances.
3707. 6723
3708. The total size, in bytes, of all requests.
3709. 6725
3710. The total size, in bytes, of responses sent to a client.  This does not include standard HTTP response headers.
3711. 6727
3712. The number of requests currently executing.
3713. 6729
3714. Total number of failed requests.
3715. 6731
3716. The number of requests for resources that were not found.
3717. 6733
3718. Number of requests failed due to unauthorized access.
3719. 6735
3720. The number of requests in the application request queue.
3721. 6737
3722. The number of requests that timed out.
3723. 6739
3724. The number of requests that executed successfully.
3725. 6741
3726. The total number of requests since the application was started.
3727. 6743
3728. The number of requests executed per second.
3729. 6745
3730. The current number of sessions currently active.
3731. 6747
3732. The number of sessions that have been explicitly abandoned.
3733. 6749
3734. The number of sessions timed out.
3735. 6751
3736. Total number of sessions since the application was started.
3737. 6753
3738. The number of transactions aborted.
3739. 6755
3740. The number of transactions committed.
3741. 6757
3742. Number of transactions in progress.
3743. 6759
3744. The total number of transactions since the application was started.
3745. 6761
3746. Transactions started per second.
3747. 6763
3748. The total number of connections to the State Server used by session state.
3749. 6765
3750. The total number of connections to the SQL Server used by session state.
3751. 6767
3752. Total number of instrumentation events raised since the application was started.
3753. 6769
3754. Total number of instrumentation events per second.
3755. 6771
3756. Number of application events raised since the application was started.
3757. 6773
3758. Number of application events raised per second.
3759. 6775
3760. Number of error events raised since the application was started.
3761. 6777
3762. Number of error events per second.
3763. 6779
3764. Number of runtime error events raised since the application was started.
3765. 6781
3766. Number of runtime error events per second.
3767. 6783
3768. Number of HTTP error events raised since the application was started.
3769. 6785
3770. Number of HTTP error events raised per second.
3771. 6787
3772. Number of request events raised since the application was started
3773. 6789
3774. Number of request events raised per second.
3775. 6791
3776. Number of audit successes in the application since it was started.
3777. 6793
3778. Number of audit failures in the application since it was started.
3779. 6795
3780. Number of successful membership credential validations since the application was started.
3781. 6797
3782. Number of failed membership credential validations since the application was started.
3783. 6799
3784. Number of successful forms authentication ticket validations since the application was started.
3785. 6801
3786. Number of failed forms authentication ticket validations since the application was started.
3787. 6803
3788. Number of viewstate MAC validations that failed since the application was started.
3789. 6805
3790. The number of milliseconds that it took to execute the most recent request.
3791. 6807
3792. The number of requests disconnected due to communication errors or user terminated.
3793. 6809
3794. The number of requests rejected because the application request queue was full.
3795. 6811
3796. The number of milliseconds the most recent request was waiting in the queue.
3797. 6813
3798. The amount of physical memory used by the machine divided by the physical memory limit for the cache, as a percentage.  When this reaches 100%, half of the cache entries will be forcibly removed.  The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.
3799. 6815
3800. Cache % Machine Memory Limit Used Base
3801. 6817
3802. The value of private bytes for the worker process divided by the private bytes memory limit for the cache, as a percentage.  When this reaches 100%, half of the cache entries will be forcibly removed.  The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.
3803. 6819
3804. Cache % Process Memory Limit Used Base
3805. 6821
3806. Total number of entries forcibly removed from the cache due to memory pressure.
3807. 6823
3808. Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache using one of the public cache APIs.
3809. 6825
3810. Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache by the output cache feature.
3811. 6827
3812. Estimated percentage of elapsed time that the processor spends executing managed application code.  This counter only tracks processor time of managed threads in the application.  It does not include additional processor time spent executing on non-managed threads.  Note that this counter is only updated with new data every five seconds.
3813. 6829
3814. % Managed Processor Time Base (estimated)
3815. 6831
3816. Estimated managed heap memory consumption (in KB) by the application.  The accuracy of this counter varies depending on the duration of elapsed time since the last full managed memory heap collection.  Note that this counter is only updated with new data every five seconds.
3817. 6833
3818. The total size, in bytes, of data received by ASP.NET on WebSocket connections.
3819. 6835
3820. The total size, in bytes, of data sent to a client on WebSocket connections.
3821. 6837
3822. The number of WebSocket requests currently executing.
3823. 6839
3824. Total number of WebSocket requests that ended up in an aborted state.
3825. 6841
3826. Total number of WebSocket requests that completed gracefully.
3827. 6843
3828. The total number of WebSocket requests since the application was started.
3829. 7471
3830. SMSvcHost 4.0.0.0 performance counters
3831. 7473
3832. The total number of failures at the protocol layer of net.tcp.
3833. 7475
3834. The total number of failures at the protocol layer of net.pipe.
3835. 7477
3836. The total number of failures dispatching messages received over net.tcp.
3837. 7479
3838. The total number of failures dispatching messages received over net.pipe.
3839. 7481
3840. The total number of connections dispatched over net.tcp.
3841. 7483
3842. The total number of connections dispatched over net.pipe.
3843. 7485
3844. The total number of TCP connections accepted over net.tcp.
3845. 7487
3846. The total number of named pipe connections accepted over net.pipe.
3847. 7489
3848. The number of uri registrations currently active for net.tcp.
3849. 7491
3850. The number of uri registrations currently active for net.pipe.
3851. 7493
3852. The total number of uris that were succesfully registered for net.tcp.
3853. 7495
3854. The total number of uris that were succesfully registered for net.pipe.
3855. 7497
3856. The total number of uris that were succesfully unregistered for net.tcp.
3857. 7499
3858. The total number of uris that were succesfully unregistered for net.pipe.
3859. 7501
3860. MSDTC Bridge 4.0.0.0 performance counters
3861. 7503
3862. The number of WS-AT protocol messages that the WS-AT service failed to send per second.
3863. 7505
3864. The number of Prepare retry messages that the WS-AT service has sent per second.
3865. 7507
3866. The number of Commit retry messages that the WS-AT service has sent per second.
3867. 7509
3868. The number of Prepared retry messages that the WS-AT service has sent per second.
3869. 7511
3870. The number of Replay retry messages that the WS-AT service has sent per second.
3871. 7513
3872. The number of Fault messages that the WS-AT service has received per second.
3873. 7515
3874. The number of Fault messages that the WS-AT service has sent per second.
3875. 7517
3876. Average time in milliseconds for the WS-AT service to receive a Prepare message response from a participant.
3877. 7519
3878. Base counter for the 'Average participant prepare response time' counter.
3879. 7521
3880. Average time in milliseconds for the WS-AT service to receive a Commit message response from a participant.
3881. 7523
3882. Base counter for the 'Average participant commit response time' counter.
3883. 7525
3884. Windows Workflow Foundation Performance Counters
3885. 7527
3886. Total number of workflows created.
3887. 7529
3888. Rate of workflows created per second.
3889. 7531
3890. Total number of workflows unloaded.
3891. 7533
3892. Rate of workflows unloaded per second.
3893. 7535
3894. Total number of workflows loaded.
3895. 7537
3896. Rate of workflows loaded per second.
3897. 7539
3898. Total number of workflows completed.
3899. 7541
3900. Rate of workflows completed per second.
3901. 7543
3902. Total number of workflows suspended.
3903. 7545
3904. Rate of workflows suspended per second.
3905. 7547
3906. Total number of workflows terminated.
3907. 7549
3908. Rate of workflows terminated per second.
3909. 7551
3910. Total number of workflows in memory.
3911. 7553
3912. Total number of workflows aborted.
3913. 7555
3914. Rate of workflows aborted per second.
3915. 7557
3916. Total number of workflows persisted.
3917. 7559
3918. Rate of workflows persisted per second.
3919. 7561
3920. Total number of workflow instances actively executing.
3921. 7563
3922. Rate of workflows becoming idle per second.
3923. 7565
3924. Total number of workflows ready to execute.
3925. 7567
3926. Total number of workflows waiting for a thread.
3927. 7569
3928. Counters for classes in the System.Net namespace.
3929. 7571
3930. The cumulative total number of socket connections established for this process since the process was started.
3931. 7573
3932. The 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.
3933. 7575
3934. The 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.
3935. 7577
3936. The cumulative total number of datagram packets received since the process was started.
3937. 7579
3938. The cumulative total number of datagram packets sent since the process was started.
3939. 7581
3940. The number of HttpWebRequest objects created during the last sample interval (typically 1 sec).
3941. 7583
3942. The 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.
3943. 7585
3944. HttpWebRequests Average Lifetime Base
3945. 7587
3946. The 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.
3947. 7589
3948. The 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.
3949. 7591
3950. HttpWebRequests Average Queue Time Base
3951. 7593
3952. The 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.
3953. 7595
3954. The 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()
3955. 7831
3956. ASP.NET State Service
3957. 8057
3958. The current number of sessions currently active.
3959. 8059
3960. The number of sessions that have been explicitly abandoned.
3961. 8061
3962. The number of sessions timed out.
3963. 8063
3964. The number of sessions total.
3965. 8065
3966. ASP.NET global performance counters
3967. 8067
3968. ASP.NET application performance counters
3969. 8069
3970. Number of times the application has been restarted during the web server's lifetime.
3971. 8071
3972. Number of currently running web applications.
3973. 8073
3974. The number of requests disconnected due to communication errors or user terminated.
3975. 8075
3976. The number of milliseconds that it took to execute the most recent request.
3977. 8077
3978. The number of requests rejected because the request queue was full.
3979. 8079
3980. The number of requests waiting to be processed.
3981. 8081
3982. Number of worker processes running on the machine.
3983. 8083
3984. Number of times a worker process has restarted on the machine.
3985. 8085
3986. The number of milliseconds the most recent request was waiting in the queue.
3987. 8087
3988. The current number of sessions currently active.
3989. 8089
3990. The number of sessions that have been explicitly abandoned.
3991. 8091
3992. The number of sessions timed out.
3993. 8093
3994. The number of sessions total.
3995. 8095
3996. The current number of requests, including those that are queued, currently executing, or waiting to be written to the client.  Under the ASP.NET process model, when this counter exceeds the requestQueueLimit defined in the processModel configuration section, ASP.NET will begin rejecting requests.
3997. 8097
3998. Number of audit successes in the application since it was started.
3999. 8099
4000. Number of audit failures in the application since it was started.
4001. 8101
4002. Number of error events raised since the application was started.
4003. 8103
4004. Number of runtime error events raised since the application was started.
4005. 8105
4006. Number of HTTP error events raised since the application was started.
4007. 8107
4008. Requests queued because the concurrency limits have been exceeded.
4009. 8109
4010. Number of requests utilizing anonymous authentication.
4011. 8111
4012. Number of Authentication Anonymous Requests/Sec
4013. 8113
4014. Total number of entries within the cache (both internal and user added)
4015. 8115
4016. Number of additions and removals to the total cache per second.
4017. 8117
4018. Total number of hits from the cache.
4019. 8119
4020. Total number of cache misses.
4021. 8121
4022. Ratio of hits from all cache calls.
4023. 8123
4024. Cache Total Hit Ratio Base
4025. 8125
4026. Total number of entries within the cache added by the user.
4027. 8127
4028. Number of additions and removals to the API cache per second.
4029. 8129
4030. Number of cache hits from user code.
4031. 8131
4032. Number of cache misses called from user code.
4033. 8133
4034. Ratio of hits called from user code.
4035. 8135
4036. Cache API Hit Ratio Base
4037. 8137
4038. Current number of entries in the output cache.
4039. 8139
4040. Number of additions and removals to the output cache per second.
4041. 8141
4042. Total number of output cacheable requests served from the output cache.
4043. 8143
4044. Total number of output cacheable requests not served from the output cache.
4045. 8145
4046. Ratio of hits to requests for output cacheable requests.
4047. 8147
4048. Output Cache Hit Ratio Base
4049. 8149
4050. Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled.
4051. 8151
4052. Number of debugging requests processed.
4053. 8153
4054. Number of errors that have occurred during parsing and configuration.
4055. 8155
4056. Number of errors that have occurred during compilation.
4057. 8157
4058. Number of errors that have occurred during the processing of a request.
4059. 8159
4060. Number of errors not handled by user code, but by the default error handler.
4061. 8161
4062. Rate of unhandled errors.
4063. 8163
4064. Total number of errors occurred.
4065. 8165
4066. Rate of errors occurred.
4067. 8167
4068. Number of active pipeline instances.
4069. 8169
4070. The total size, in bytes, of all requests.
4071. 8171
4072. The total size, in bytes, of responses sent to a client.  This does not include standard HTTP response headers.
4073. 8173
4074. The number of requests currently executing.
4075. 8175
4076. Total number of failed requests.
4077. 8177
4078. The number of requests for resources that were not found.
4079. 8179
4080. Number of requests failed due to unauthorized access.
4081. 8181
4082. The number of requests in the application request queue.
4083. 8183
4084. The number of requests that timed out.
4085. 8185
4086. The number of requests that executed successfully.
4087. 8187
4088. The total number of requests since the application was started.
4089. 8189
4090. The number of requests executed per second.
4091. 8191
4092. The current number of sessions currently active.
4093. 8193
4094. The number of sessions that have been explicitly abandoned.
4095. 8195
4096. The number of sessions timed out.
4097. 8197
4098. Total number of sessions since the application was started.
4099. 8199
4100. The number of transactions aborted.
4101. 8201
4102. The number of transactions committed.
4103. 8203
4104. Number of transactions in progress.
4105. 8205
4106. The total number of transactions since the application was started.
4107. 8207
4108. Transactions started per second.
4109. 8209
4110. The total number of connections to the State Server used by session state.
4111. 8211
4112. The total number of connections to the SQL Server used by session state.
4113. 8213
4114. Total number of instrumentation events raised since the application was started.
4115. 8215
4116. Total number of instrumentation events per second.
4117. 8217
4118. Number of application events raised since the application was started.
4119. 8219
4120. Number of application events raised per second.
4121. 8221
4122. Number of error events raised since the application was started.
4123. 8223
4124. Number of error events per second.
4125. 8225
4126. Number of runtime error events raised since the application was started.
4127. 8227
4128. Number of runtime error events per second.
4129. 8229
4130. Number of HTTP error events raised since the application was started.
4131. 8231
4132. Number of HTTP error events raised per second.
4133. 8233
4134. Number of request events raised since the application was started
4135. 8235
4136. Number of request events raised per second.
4137. 8237
4138. Number of audit successes in the application since it was started.
4139. 8239
4140. Number of audit failures in the application since it was started.
4141. 8241
4142. Number of successful membership credential validations since the application was started.
4143. 8243
4144. Number of failed membership credential validations since the application was started.
4145. 8245
4146. Number of successful forms authentication ticket validations since the application was started.
4147. 8247
4148. Number of failed forms authentication ticket validations since the application was started.
4149. 8249
4150. Number of viewstate MAC validations that failed since the application was started.
4151. 8251
4152. The number of milliseconds that it took to execute the most recent request.
4153. 8253
4154. The number of requests disconnected due to communication errors or user terminated.
4155. 8255
4156. The number of requests rejected because the application request queue was full.
4157. 8257
4158. The number of milliseconds the most recent request was waiting in the queue.
4159. 8259
4160. The amount of physical memory used by the machine divided by the physical memory limit for the cache, as a percentage.  When this reaches 100%, half of the cache entries will be forcibly removed.  The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.
4161. 8261
4162. Cache % Machine Memory Limit Used Base
4163. 8263
4164. The value of private bytes for the worker process divided by the private bytes memory limit for the cache, as a percentage.  When this reaches 100%, half of the cache entries will be forcibly removed.  The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.
4165. 8265
4166. Cache % Process Memory Limit Used Base
4167. 8267
4168. Total number of entries forcibly removed from the cache due to memory pressure.
4169. 8269
4170. Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache using one of the public cache APIs.
4171. 8271
4172. Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache by the output cache feature.
4173. 8273
4174. Estimated percentage of elapsed time that the processor spends executing managed application code.  This counter only tracks processor time of managed threads in the application.  It does not include additional processor time spent executing on non-managed threads.  Note that this counter is only updated with new data every five seconds.
4175. 8275
4176. % Managed Processor Time Base (estimated)
4177. 8277
4178. Estimated managed heap memory consumption (in KB) by the application.  The accuracy of this counter varies depending on the duration of elapsed time since the last full managed memory heap collection.  Note that this counter is only updated with new data every five seconds.
4179. 8279
4180. The total size, in bytes, of data received by ASP.NET on WebSocket connections.
4181. 8281
4182. The total size, in bytes, of data sent to a client on WebSocket connections.
4183. 8283
4184. The number of WebSocket requests currently executing.
4185. 8285
4186. Total number of WebSocket requests that ended up in an aborted state.
4187. 8287
4188. Total number of WebSocket requests that completed gracefully.
4189. 8289
4190. The total number of WebSocket requests since the application was started.
4191. 8291
4192. Number of WMI High Performance provider returned by WMI Adapter
4193. 8293
4194. Shows High Performance Classes
4195. 8295
4196. Shows if High Performance Classes are valid
4197. 8297
4198. MSiSCSI_ConnectionStatistics
4199. 8299
4200. BytesReceived
4201. 8301
4202. BytesSent
4203. 8303
4204. PDUCommandsSent
4205. 8305
4206. PDUResponsesReceived
4207. 8307
4208. MSiSCSI_InitiatorInstanceStatistics
4209. 8309
4210. SessionConnectionTimeoutErrorCount
4211. 8311
4212. SessionDigestErrorCount
4213. 8313
4214. SessionFailureCount
4215. 8315
4216. SessionFormatErrorCount
4217. 8317
4218. MSiSCSI_InitiatorLoginStatistics
4219. 8319
4220. LoginAcceptRsps
4221. 8321
4222. LoginAuthenticateFails
4223. 8323
4224. LoginAuthFailRsps
4225. 8325
4226. LoginFailures
4227. 8327
4228. LoginNegotiateFails
4229. 8329
4230. LoginOtherFailRsps
4231. 8331
4232. LoginRedirectRsps
4233. 8333
4234. LogoutNormals
4235. 8335
4236. LogoutOtherCodes
4237. 8337
4238. MSiSCSI_MMIPSECStats
4239. 8339
4240. AcquireFailures
4241. 8341
4242. AcquireHeapSize
4243. 8343
4244. ActiveAcquire
4245. 8345
4246. ActiveReceive
4247. 8347
4248. AuthenticationFailures
4249. 8349
4250. ConnectionListSize
4251. 8351
4252. GetSPIFailures
4253. 8353
4254. InvalidCookiesReceived
4255. 8355
4256. InvalidPackets
4257. 8357
4258. KeyAdditionFailures
4259. 8359
4260. KeyAdditions
4261. 8361
4262. KeyUpdateFailures
4263. 8363
4264. KeyUpdates
4265. 8365
4266. NegotiationFailures
4267. 8367
4268. OakleyMainMode
4269. 8369
4270. OakleyQuickMode
4271. 8371
4272. ReceiveFailures
4273. 8373
4274. ReceiveHeapSize
4275. 8375
4276. SendFailures
4277. 8377
4278. SoftAssociations
4279. 8379
4280. TotalGetSPI
4281. 8381
4282. MSiSCSI_NICPerformance
4283. 8383
4284. BytesReceived
4285. 8385
4286. BytesTransmitted
4287. 8387
4288. PDUReceived
4289. 8389
4290. PDUTransmitted
4291. 8391
4292. MSiSCSI_QMIPSECStats
4293. 8393
4294. ActiveSA
4295. 8395
4296. ActiveTunnels
4297. 8397
4298. AuthenticatedBytesReceived
4299. 8399
4300. AuthenticatedBytesSent
4301. 8401
4302. BadSPIPackets
4303. 8403
4304. ConfidentialBytesReceived
4305. 8405
4306. ConfidentialBytesSent
4307. 8407
4308. KeyAdditions
4309. 8409
4310. KeyDeletions
4311. 8411
4312. PacketsNotAuthenticated
4313. 8413
4314. PacketsNotDecrypted
4315. 8415
4316. PacketsWithReplayDetection
4317. 8417
4318. PendingKeyOperations
4319. 8419
4320. ReKeys
4321. 8421
4322. TransportBytesReceived
4323. 8423
4324. TransportBytesSent
4325. 8425
4326. TunnelBytesReceived
4327. 8427
4328. TunnelBytesSent
4329. 8429
4330. MSiSCSI_RequestTimeStatistics
4331. 8431
4332. AverageProcessingTime
4333. 8433
4334. MaximumProcessingTime
4335. 8435
4336. MSiSCSI_SessionStatistics
4337. 8437
4338. BytesReceived
4339. 8439
4340. BytesSent
4341. 8441
4342. ConnectionTimeoutErrors
4343. 8443
4344. DigestErrors
4345. 8445
4346. FormatErrors
4347. 8447
4348. PDUCommandsSent
4349. 8449
4350. PDUResponsesReceived
4351. 8451
4352. ProcessorPerformance
4353. 8453
4354. frequency
4355. 8455
4356. percentage
4357. 8457
4358. power
4359. 3199
4360. Informations de résumé des services Terminal Server
4361. 3201
4362. Nombre de sessions actives des services Terminal Server
4363. 3203
4364. Nombre de sessions inactives des services Terminal Server
4365. 3205
4366. Nombre total de sessions des services Terminal Server
4367. 4455
4368. Le jeu de compteurs de performance Flux Pacer comprend des statistiques de flux du planificateur de paquets.
4369. 4457
4370. Nombre de paquets ignorés par le planificateur de paquets.
4371. 4459
4372. Nombre de paquets planifiés d’une façon quelconque (au lieu d’être envoyés directement au miniport sous-jacent).
4373. 4461
4374. Nombre de paquets envoyés par seconde appartenant à ce flux.
4375. 4463
4376. Nombre d’octets planifiés d’une façon quelconque (au lieu d’être envoyés directement au miniport sous-jacent).
4377. 4465
4378. Nombre d’octets envoyés appartenant à ce flux.
4379. 4467
4380. Nombre d’octets envoyés par seconde appartenant à ce flux.
4381. 4469
4382. Nombre d’octets planifiés par seconde appartenant à ce flux.
4383. 4471
4384. Nombre de paquets envoyés par seconde appartenant à ce flux.
4385. 4473
4386. Nombre de paquets planifiés par seconde appartenant à ce flux.
4387. 4475
4388. Nombre de paquets de ce flux ignorés par seconde par le planificateur de paquets.
4389. 4477
4390. Nombre de paquets entrés dans le planificateur de paquets à un taux supérieur aux paramètres de flux.
4391. 4479
4392. Taux auquel les paquets non conformes sont entrés dans le planificateur de paquets.
4393. 4481
4394. Nombre moyen de paquets dans le modélisateur pendant la dernière période d’échantillonnage.
4395. 4483
4396. Nombre maximal de paquets présents simultanément dans le modélisateur.
4397. 4485
4398. Nombre moyen de paquets dans le séquenceur pendant la dernière période d’échantillonnage.
4399. 4487
4400. Nombre maximal de paquets présents simultanément dans le séquenceur.
4401. 4489
4402. Nombre maximal de paquets mis en file d’attente dans la carte réseau par ce flux.
4403. 4491
4404. Nombre moyen de paquets mis en file d’attente dans la carte réseau par ce flux.
4405. 4493
4406. Nombre de paquets envoyés par le planificateur de paquets à un taux supérieur aux paramètres de flux.
4407. 4495
4408. Taux auquel les paquets non conformes sont envoyés par le planificateur de paquets.
4409. 4497
4410. Le jeu de compteurs de performance Canal Pacer comprend des statistiques de canal du planificateur de paquets.
4411. 4499
4412. Nombre de fois où Pacer n’a pas pu allouer un paquet.
4413. 4501
4414. Nombre de flux ouverts sur ce canal (certains peuvent être maintenant fermés).
4415. 4503
4416. Nombre de flux qui ont été fermés.
4417. 4505
4418. Nombre de flux qui ont été rejetés.
4419. 4507
4420. Nombre de fois où un flux a été modifié.
4421. 4509
4422. Nombre de fois où une modification de flux a été rejetée.
4423. 4511
4424. Nombre maximal de flux qui ont été ouverts simultanément sur ce canal.
4425. 4513
4426. Nombre de paquets entrés dans le planificateur de paquets à un taux supérieur aux paramètres de flux de paquet.
4427. 4515
4428. Taux auquel les paquets non conformes sont entrés dans le planificateur de paquets.
4429. 4517
4430. Nombre moyen de paquets dans le modélisateur pendant la dernière période d’échantillonnage.
4431. 4519
4432. Nombre maximal de paquets présents simultanément dans le modélisateur.
4433. 4521
4434. Nombre moyen de paquets dans le séquenceur pendant la dernière période d’échantillonnage.
4435. 4523
4436. Nombre maximal de paquets présents simultanément dans le séquenceur.
4437. 4525
4438. Nombre maximal de paquets présents simultanément dans la carte réseau.
4439. 4527
4440. Nombre moyen de paquets dans la carte réseau pendant la dernière période d’échantillonnage.
4441. 4529
4442. Nombre de paquets envoyés par le planificateur de paquets à un taux supérieur aux paramètres de flux de paquet.
4443. 4531
4444. Taux auquel les paquets non conformes sont envoyés par le planificateur de paquets.
4445. 2259
4446. WFPv4 est l’ensemble de compteurs de la plateforme de filtrage Windows qui s’appliquent au trafic et aux connexions via le protocole IPv4.
4447. 2261
4448. Le compteur Paquets entrants rejetés par seconde représente le nombre de paquets entrants qui sont rejetés en une seconde par la plateforme de filtrage Windows.
4449. 2263
4450. Le compteur Paquets sortants rejetés par seconde représente le nombre de paquets sortants qui sont rejetés en une seconde par la plateforme de filtrage Windows.
4451. 2265
4452. Le compteur Paquets rejetés par seconde représente le nombre total de paquets entrants et sortants qui sont rejetés en une seconde par la plateforme de filtrage Windows.
4453. 2267
4454. Le compteur Liaisons bloquées représente le nombre de demandes d’affectation de ressource réseau bloquées par la plateforme de filtrage Windows depuis que l’ordinateur a été démarré.
4455. 2269
4456. Le compteur Connexions entrantes bloquées par seconde représente le nombre de connexions entrantes bloquées en une seconde par la plateforme de filtrage Windows.
4457. 2271
4458. Le compteur Connexions sortantes bloquées par seconde représente le nombre de connexions sortantes bloquées en une seconde par la plateforme de filtrage Windows.
4459. 2273
4460. Le compteur Connexions entrantes autorisées par seconde représente le nombre de connexions entrantes autorisées en une seconde par la plateforme de filtrage Windows.
4461. 2275
4462. Le compteur Connexions sortantes autorisées par seconde représente le nombre de connexions sortantes autorisées en une seconde par la plateforme de filtrage Windows.
4463. 2277
4464. Le compteur Connexions entrantes représente le nombre de connexions entrantes autorisées par la plateforme de filtrage Windows depuis que l’ordinateur a été démarré.
4465. 2279
4466. Le compteur Connexions sortantes représente le nombre de connexions sortantes autorisées par la plateforme de filtrage Windows depuis que l’ordinateur a été démarré.
4467. 2281
4468. Le compteur Connexions entrantes actives représente le nombre de connexions entrantes autorisées par la plateforme de filtrage Windows.
4469. 2283
4470. Le compteur Connexions sortantes actives représente le nombre de connexions sortantes autorisées par la plateforme de filtrage Windows.
4471. 2285
4472. Le compteur Classifications autorisées par seconde représente le nombre d’évaluations de règle de sécurité autorisant une activité réseau effectuées en une seconde par la plateforme de filtrage Windows.
4473. 2319
4474. Pilote IPSec est l’ensemble de compteurs du pilote de sécurité du protocole IP (IPsec) qui s’appliquent au trafic sur le protocole IPv4 et le protocole IPv6.
4475. 2321
4476. Le compteur Associations de sécurité active représente le nombre d’associations de sécurité de mode rapide actives.
4477. 2323
4478. Le compteur Associations de sécurité en attente représente le nombre d’associations de sécurité de mode rapide en attente.
4479. 2325
4480. Le compteur Paquets SPI incorrects représente le nombre de paquets pour lesquels l’index de paramètre de sécurité (SPI) était incorrect depuis le dernier démarrage de l’ordinateur. Un grand nombre de paquets avec des index SPI sur une courte période de temps peut indiquer une tentative d’attaque par usurpation d’identité des paquets.
4481. 2327
4482. Le compteur Paquets SPI incorrects par seconde représente le nombre de paquets pour lesquels l’index de paramètre de sécurité (SPI) était incorrect depuis le dernier démarrage de l’ordinateur. Un grand nombre de paquets avec des SPI incorrects sur une courte période de temps peut indiquer une tentative d’attaque par usurpation d’identité des paquets.
4483. 2329
4484. Le compteur Octets reçus en mode tunnel par seconde représente le nombre d’octets reçus par seconde avec le mode tunnel.
4485. 2331
4486. Le compteur Octets envoyés en mode tunnel par seconde représente le nombre d’octets envoyés par seconde avec le mode tunnel.
4487. 2333
4488. Le compteur Octets reçus en mode transport par seconde représente le nombre d’octets reçus par seconde avec le mode transport.
4489. 2335
4490. Le compteur Octets envoyés en mode transport par seconde représente le nombre d’octets envoyés par seconde avec le mode transport.
4491. 2337
4492. Le compteur Associations de sécurité déchargées représente le nombre d’associations de sécurité de mode rapide actives déchargées sur le matériel. Certaines cartes réseau peuvent accélérer le traitement IPSec en se déchargeant sur le matériel des fonctions de chiffrement d’IPSec.
4493. 2339
4494. Le compteur Octets déchargés reçus par seconde représente le nombre d’octets reçus par seconde avec le déchargement matériel d’IPSec. Certaines cartes réseau peuvent accélérer le traitement IPSec en se déchargeant sur le matériel des fonctions de chiffrement d’IPSec.
4495. 2341
4496. Le compteur Octets déchargés envoyés par seconde représente le nombre d’octets envoyés par seconde avec le déchargement matériel d’IPSec. Certaines cartes réseau peuvent accélérer le traitement IPSec en se déchargeant sur le matériel des fonctions de chiffrement d’IPSec.
4497. 2343
4498. Le compteur Paquets ayant échoué à la détection de relecture représente le nombre de paquets qui contenaient un numéro de séquence non valide depuis le dernier démarrage de l’ordinateur. Des augmentations de ce compteur peuvent indiquer un problème réseau ou une attaque par relecture.
4499. 2345
4500. Le compteur Paquets ayant échoué à la détection de relecture par seconde représente le nombre de paquets par seconde qui contenaient un numéro de séquence non valide depuis le dernier démarrage de l’ordinateur. Des augmentations de ce compteur peuvent indiquer un problème réseau ou une attaque par relecture.
4501. 2347
4502. Le compteur Paquets non authentifiés représente le nombre de paquets pour lesquels des données n’ont pas pu être vérifiées (pour lesquels la vérification du hachage d’intégrité à échoué) depuis le dernier démarrage de l’ordinateur. Des augmentations de ce compteur peuvent indiquer une tentative d’attaque par modification ou usurpation d’identité de paquets IPSec, ou bien la corruption de paquets par des périphériques réseau.
4503. 2349
4504. Le compteur Paquets non authentifiés par seconde représente le nombre de paquets par seconde pour lesquels des données n’ont pas pu être vérifiées (pour lesquels la vérification du hachage d’intégrité à échoué) depuis le dernier démarrage de l’ordinateur. Des augmentations de ce compteur peuvent indiquer une tentative d’attaque par modification ou usurpation d’identité de paquets IPSec, ou bien des paquets endommagés par des périphériques réseau.
4505. 2351
4506. Le compteur Paquets non déchiffrés représente le nombre de paquets qui n’ont pas pu être déchiffrés depuis le dernier démarrage de l’ordinateur. Un paquet peut ne pas être déchiffré s’il échoue à une vérification de validation.
4507. 2353
4508. Le compteur Paquets non déchiffrés par seconde représente le nombre de paquets par seconde qui n’ont pas pu être déchiffrés depuis le dernier démarrage de l’ordinateur. Un paquet peut ne pas être déchiffré s’il échoue à une vérification de validation.
4509. 2355
4510. Le compteur Nouvelles clés d’association de sécurité représente le nombre d’opérations de nouvelle clé réussies pour les associations de sécurité de mode rapide depuis le dernier démarrage de l’ordinateur.
4511. 2357
4512. Le compteur Associations de sécurité ajoutées est le nombre d’associations de sécurité ajoutées depuis le dernier démarrage de l’ordinateur.
4513. 2359
4514. Le compteur Paquets ayant échoué à la validation ESP représente le nombre de paquets reçus qui ont échoué à la validation ESP depuis le dernier démarrage de l’ordinateur.
4515. 2361
4516. Le compteur Paquets ayant échoué à la validation ESP par seconde représente le nombre de paquets reçus par seconde qui ont échoué à la validation ESP depuis le dernier démarrage de l’ordinateur.
4517. 2363
4518. Le compteur Paquets ayant échoué à la validation UDP-ESP représente le nombre de paquets reçus qui ont échoué la validation UDP-ESP (utilisée pour les parcours NAT) depuis le dernier démarrage de l’ordinateur.
4519. 2365
4520. Le compteur Paquets ayant échoué à la validation UDP-ESP par seconde représente le nombre de paquets reçus par seconde qui ont échoué à la validation UDP-ESP (utilisée pour les parcours NAT) depuis le dernier démarrage de l’ordinateur.
4521. 2367
4522. Le compteur Paquets reçus avec une association de sécurité erronée représente le nombre de paquets reçus avec l’association de sécurité erronée depuis le dernier démarrage de l’ordinateur.
4523. 2369
4524. Le compteur Paquets reçus avec une association de sécurité erronée par seconde représente le nombre de paquets reçus par seconde avec l’association de sécurité erronée depuis le dernier démarrage de l’ordinateur.
4525. 2371
4526. Le compteur Paquets en texte clair reçus représente le nombre de paquets en texte clair reçus depuis le dernier démarrage de l’ordinateur.
4527. 2373
4528. Le compteur Paquets en texte clair reçus par seconde représente le nombre de paquets en texte clair reçus par seconde depuis le dernier démarrage de l’ordinateur.
4529. 2375
4530. Le compteur Total des paquets entrants reçus représente le nombre total de paquets entrants correctement traités par IPSec depuis le dernier démarrage de l’ordinateur.
4531. 2377
4532. Le compteur Total des paquets entrants reçus par seconde représente le nombre de paquets entrants par seconde correctement traités par IPSec.
4533. 2379
4534. Le compteur Total des paquets entrants supprimés représente le nombre total de paquets entrants supprimés par IPSec depuis le dernier démarrage de l’ordinateur.
4535. 2381
4536. Le compteur Paquets entrants supprimés par seconde représente le nombre de paquets entrants par seconde supprimés par IPSec.
4537. 2315
4538. WFP est l’ensemble de compteurs de la plateforme de filtrage Windows qui ne s’appliquent à aucune version spécifique du protocole IP.
4539. 2317
4540. Le compteur Nombre de fournisseurs est le nombre de fournisseurs inscrits avec la plateforme de filtrage Windows.
4541. 2287
4542. WFPv6 est l’ensemble de compteurs de la plateforme de filtrage Windows qui s’appliquent au trafic et aux connexions sur le protocole IPv6.
4543. 2289
4544. Le compteur Paquets entrants rejetés par seconde représente le nombre de paquets entrants qui sont rejetés en une seconde par la plateforme de filtrage Windows.
4545. 2291
4546. Le compteur Paquets sortants rejetés par seconde représente le nombre de paquets sortants qui sont rejetés en une seconde par la plateforme de filtrage Windows.
4547. 2293
4548. Le compteur Paquets rejetés par seconde représente le nombre total de paquets entrants et sortants qui sont rejetés en une seconde par la plateforme de filtrage Windows.
4549. 2295
4550. Le compteur Liaisons bloquées représente le nombre de demandes d’affectation de ressource réseau bloquées par la plateforme de filtrage Windows depuis que l’ordinateur a été démarré.
4551. 2297
4552. Le compteur Connexions entrantes bloquées par seconde représente le nombre de connexions entrantes bloquées en une seconde par la plateforme de filtrage Windows.
4553. 2299
4554. Le compteur Connexions sortantes bloquées par seconde représente le nombre de connexions sortantes bloquées en une seconde par la plateforme de filtrage Windows.
4555. 2301
4556. Le compteur Connexions entrantes autorisées par seconde représente le nombre de connexions entrantes autorisées en une seconde par la plateforme de filtrage Windows.
4557. 2303
4558. Le compteur Connexions sortantes autorisées par seconde représente le nombre de connexions sortantes autorisées en une seconde par la plateforme de filtrage Windows.
4559. 2305
4560. Le compteur Connexions entrantes représente le nombre de connexions entrantes autorisées par la plateforme de filtrage Windows depuis que l’ordinateur a été démarré.
4561. 2307
4562. Le compteur Connexions sortantes représente le nombre de connexions sortantes autorisées par la plateforme de filtrage Windows depuis que l’ordinateur a été démarré.
4563. 2309
4564. Le compteur Connexions entrantes actives représente le nombre de connexions entrantes autorisées par la plateforme de filtrage Windows.
4565. 2311
4566. Le compteur Connexions sortantes actives représente le nombre de connexions sortantes autorisées par la plateforme de filtrage Windows.
4567. 2313
4568. Le compteur Classifications autorisées par seconde représente le nombre d’évaluations de règle de sécurité autorisant une activité réseau effectuées en une seconde par la plateforme de filtrage Windows.
4569. 5683
4570. L’objet de performance Protocole PNRP est composé de compteurs qui analysent chacun des nuages PNRP disponibles. Ces compteurs analysent le cache PNRP local et mesurent le rythme auquel les messages de protocole PNRP sont envoyés et reçus.
4571. 5685
4572. Nombre d’inscriptions pour ce nuage PNRP
4573. 5687
4574. Nombre de résolutions pour ce nuage PNRP
4575. 5689
4576. Nombre d’entrées de cache pour ce nuage PNRP
4577. 5691
4578. Nombre moyen d’octets envoyés pour ce nuage PNRP
4579. 5693
4580. Nombre moyen d’octets reçus pour ce nuage PNRP
4581. 5695
4582. Taille estimée de ce nuage PNRP
4583. 5697
4584. Nombre d’entrées de cache périmées pour ce nuage PNRP
4585. 5699
4586. Nombre d’échecs d’envoi pour ce nuage PNRP
4587. 5701
4588. Nombre d’échecs de réception pour ce nuage PNRP
4589. 5703
4590. Nombre de messages de sollicitation envoyés par seconde pour ce nuage PNRP
4591. 5705
4592. Nombre de messages de sollicitation reçus par seconde pour ce nuage PNRP
4593. 5707
4594. Nombre de messages d’annonce envoyés par seconde pour ce nuage PNRP
4595. 5709
4596. Nombre de messages d’annonce reçus par seconde pour ce nuage PNRP
4597. 5711
4598. Nombre de messages de demande envoyés par seconde pour ce nuage PNRP
4599. 5713
4600. Nombre de messages de demande reçus par seconde pour ce nuage PNRP
4601. 5715
4602. Nombre de messages de saturation envoyés par seconde pour ce nuage PNRP
4603. 5717
4604. Nombre de messages de saturation reçus par seconde pour ce nuage PNRP
4605. 5719
4606. Nombre de messages de renseignement envoyés par seconde pour ce nuage PNRP
4607. 5721
4608. Nombre de messages de renseignement reçus par seconde pour ce nuage PNRP
4609. 5723
4610. Nombre de messages d’autorité envoyés par seconde pour ce nuage PNRP
4611. 5725
4612. Nombre de messages d’autorité reçus par seconde pour ce nuage PNRP
4613. 5727
4614. Nombre de messages d’accusé de réception envoyés par seconde pour ce nuage PNRP
4615. 5729
4616. Nombre de messages d’accusé de réception reçus par seconde pour ce nuage PNRP
4617. 5731
4618. Nombre de messages de recherche envoyés par seconde pour ce nuage PNRP
4619. 5733
4620. Nombre de messages de recherche reçus par seconde pour ce nuage PNRP
4621. 5735
4622. Nombre de messages de type inconnu reçus pour ce nuage PNRP
4623. 4939
4624. Ensemble de compteurs pour l’objet d’application Gestionnaire d’autorisations
4625. 4941
4626. Affiche le nombre total d’étendues dans l’application
4627. 4943
4628. Affiche le nombre d’étendues actuellement chargées en mémoire
4629. 5791
4630. Ensemble de compteurs du service de télécopie
4631. 5793
4632. Nombre total de minutes pendant lesquelles le service a envoyé et reçu des télécopies.
4633. 5795
4634. Nombre total de pages envoyées et reçues.
4635. 5797
4636. Nombre total de télécopies envoyées et reçues.
4637. 5799
4638. Nombre total d’octets envoyés et reçus.
4639. 5801
4640. Nombre de télécopies qui ont échoué.
4641. 5803
4642. Nombre de connexions sortantes qui ont échoué.
4643. 5805
4644. Durée en minutes pendant laquelle le service a correctement envoyé des télécopies transmises.
4645. 5807
4646. Nombre de pages envoyées.
4647. 5809
4648. Nombre de télécopies envoyées.
4649. 5811
4650. Nombre d’octets envoyés.
4651. 5813
4652. Nombre de télécopies que le service n’a pas pu recevoir.
4653. 5815
4654. Nombre de minutes pendant lesquelles le service a reçu des télécopies.
4655. 5817
4656. Nombre de pages reçues.
4657. 5819
4658. Nombres de télécopies reçues avec succès.
4659. 5821
4660. Nombre d’octets reçus.
4661. 2579
4662. Generic IKEv1, AuthIP, and IKEv2 is the set of Internet Protocol security (IPsec) Internet Key Exchange Version 1 (IKEv1), Authenticated IP (AuthIP), and Internet Key Exchange Version 2 (IKEv2) counters that are generic and do not apply to a specific Internet Protocol version.
4663. 2581
4664. Le compteur Durée de négociation en mode principal IKEv1 représente le nombre de millisecondes requis par la dernière association de sécurité négociée en mode principal IKEv1.
4665. 2583
4666. Le compteur Durée de négociation en mode principal AuthIP représente le nombre de millisecondes requis par la dernière association de sécurité négociée en mode principal Authenticated IP.
4667. 2585
4668. Le compteur Durée de négociation en mode rapide IKEv1 représente le nombre de millisecondes requis par la dernière association de sécurité négociée en mode rapide IKEv1.
4669. 2587
4670. Le compteur Durée de négociation en mode rapide AuthIP représente le nombre de millisecondes requis par la dernière association de sécurité négociée en mode rapide Authenticated IP.
4671. 2589
4672. Le compteur Durée de négociation en mode étendu représente le nombre de millisecondes requis par la dernière association de sécurité négociée en mode étendu.
4673. 2591
4674. Le compteur Paquets reçus par seconde représente le nombre de paquets IPSec valides reçus par seconde.
4675. 2593
4676. Le compteur Paquets non valides reçus par seconde représente le nombre de paquets IPSec non valides reçus par seconde.
4677. 2595
4678. Le compteur Négociations réussies représente le nombre de négociations réalisées pour IKEv1, AuthIP et IKEv2 depuis le dernier démarrage d’IPSec.
4679. 2597
4680. Le compteur Négociations réussies par seconde représente le nombre de négociations réalisées par seconde pour IKEv1, AuthIP et IKEv2.
4681. 2599
4682. Le compteur Négociations en échec représente le nombre de négociations en échec pour IKEv1, AuthIP et IKEv2 depuis le dernier démarrage d’IPSec.
4683. 2601
4684. Le compteur Négociations en échec par seconde représente le nombre de négociations ayant échoué par seconde pour IKEv1, AuthIP et IKEv2.
4685. 2603
4686. Le compteur Durée de négociation en mode principal IKEv2 représente le nombre de millisecondes requis par la dernière association de sécurité en mode principal IKEv2 négociée.
4687. 2605
4688. La durée de négociation en mode rapide IKEv2 est le nombre de millisecondes requis par la dernière association de sécurité en mode rapide IKEv2 négociée.
4689. 2607
4690. IPSec IKEv2 IPv4 est l’ensemble de compteurs IPSec (Internet Protocol security) IKEv2 (Internet Key Exchange Version 2) qui s’appliquent au trafic et aux connexions via le protocole IPv4 (Internet Protocol version 4).
4691. 2609
4692. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
4693. 2611
4694. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
4695. 2613
4696. Le compteur Négociations en mode principal représente le nombre de négociations en mode principal tentées depuis le dernier démarrage d’IPSec.
4697. 2615
4698. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées par seconde.
4699. 2617
4700. Le compteur Négociations en mode principal réussies représente le nombre de négociations en mode principal achevées depuis le dernier démarrage d’IPSec.
4701. 2619
4702. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées par seconde.
4703. 2621
4704. Le compteur Négociations en mode principal en échec représente le nombre de négociations en mode principal ayant échoué depuis le dernier démarrage d’IPSec.
4705. 2623
4706. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué par seconde.
4707. 2625
4708. Le compteur Demandes de négociations en mode principal reçues représente le nombre de négociations en mode principal initiées par un pair depuis le dernier démarrage d’IPSec.
4709. 2627
4710. Le compteur Demandes de négociations en mode principal reçues par seconde représente le nombre de négociations en mode principal initiées par un pair par seconde.
4711. 2629
4712. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
4713. 2631
4714. Le compteur Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
4715. 2633
4716. Le compteur Négociations en mode rapide représente le nombre de négociations en mode rapide tentées depuis le dernier démarrage d’IPSec.
4717. 2635
4718. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées par seconde.
4719. 2637
4720. Le compteur Négociations en mode rapide réussies représente le nombre de négociations en mode rapide achevées depuis le dernier démarrage d’IPSec.
4721. 2639
4722. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées par seconde.
4723. 2641
4724. Le compteur Négociations en mode rapide en échec représente le nombre de négociations en mode rapide ayant échoué depuis le dernier démarrage d’IPSec.
4725. 2643
4726. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué par seconde.
4727. 2459
4728. IPSec AuthIP IPv4 est l’ensemble de compteurs Internet Protocol Security (IPSec) Authenticated IP (AuthIP) qui s’appliquent au trafic et aux connexions via le protocole Internet version 4.
4729. 2461
4730. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
4731. 2463
4732. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
4733. 2465
4734. Le compteur Négociations en mode principal représente le nombre de négociations en mode principal tentées depuis le dernier démarrage d’IPSec.
4735. 2467
4736. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées par seconde.
4737. 2469
4738. Le compteur Négociations en mode principal réussies représente le nombre de négociations en mode principal achevées depuis le dernier démarrage d’IPSec.
4739. 2471
4740. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées par seconde.
4741. 2473
4742. Le compteur Négociations en mode principal en échec représente le nombre de négociations en mode principal ayant échoué depuis le dernier démarrage d’IPSec.
4743. 2475
4744. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué par seconde.
4745. 2477
4746. Le compteur Demandes de négociations en mode principal reçues représente le nombre de négociations en mode principal initiées par un pair depuis le dernier démarrage d’IPSec.
4747. 2479
4748. Le compteur Demandes de négociations en mode principal reçues par seconde représente le nombre de négociations en mode principal initiées par un pair par seconde.
4749. 2481
4750. Le compteur Associations de sécurité en mode principal ayant utilisé l’emprunt d’identité est le nombre d’associations de sécurité en mode principal réalisées à l’aide de l’emprunt d’identité depuis le dernier démarrage d’IPSec.
4751. 2483
4752. Le compteur Associations de sécurité en mode principal ayant utilisé l’emprunt d’identité par seconde est le nombre d’associations de sécurité en mode principal réalisées à l’aide de l’emprunt d’identité par seconde.
4753. 2485
4754. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
4755. 2487
4756. Le compteur Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
4757. 2489
4758. Le compteur Négociations en mode rapide représente le nombre de négociations en mode rapide tentées depuis le dernier démarrage d’IPSec.
4759. 2491
4760. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées par seconde.
4761. 2493
4762. Le compteur Négociations en mode rapide réussies représente le nombre de négociations en mode rapide achevées depuis le dernier démarrage d’IPSec.
4763. 2495
4764. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées par seconde.
4765. 2497
4766. Le compteur Négociations en mode rapide en échec représente le nombre de négociations en mode rapide ayant échoué depuis le dernier démarrage d’IPSec.
4767. 2499
4768. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué par seconde.
4769. 2501
4770. Le compteur Associations de sécurité actives en mode étendu représente le nombre d’associations de sécurité en mode étendu actuellement actives.
4771. 2503
4772. Le compteur Associations de sécurité en mode étendu en attente représente le nombre d’associations de sécurité en mode étendu en attente.
4773. 2505
4774. Le compteur Négociations en mode étendu représente le nombre de négociations en mode étendu tentées depuis le dernier démarrage d’IPSec.
4775. 2507
4776. Le compteur Négociations en mode étendu par seconde représente le nombre de négociations en mode étendu tentées par seconde.
4777. 2509
4778. Le compteur Négociations en mode étendu réussies représente le nombre de négociations en mode étendu réalisées depuis le dernier démarrage d’IPSec.
4779. 2511
4780. Le compteur Négociations en mode étendu réussies par seconde représente le nombre de négociations en mode étendu réalisées par seconde.
4781. 2513
4782. Le compteur Négociations en mode étendu en échec par seconde représente le nombre de négociations en mode étendu en échec depuis le dernier démarrage d’IPSec.
4783. 2515
4784. Le compteur Négociations en mode étendu en échec par seconde représente le nombre de négociations en mode étendu ayant échoué par seconde.
4785. 2517
4786. Le compteur Associations de sécurité en mode étendu ayant utilisé l’emprunt d’identité représente le nombre d’associations de sécurité en mode étendu réalisées à l’aide de l’emprunt d’identité depuis le dernier démarrage d’IPSec.
4787. 2519
4788. IPSec AuthIP IPv6 est le jeu de compteurs Internet Protocol Security (IPSec) Authenticated IP (AuthIP) qui s’appliquent au trafic et aux connexions via le protocole Internet version 6.
4789. 2521
4790. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
4791. 2523
4792. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
4793. 2525
4794. Le compteur Négociations en mode principal représente le nombre de négociations en mode principal tentées depuis le dernier démarrage d’IPSec.
4795. 2527
4796. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées par seconde.
4797. 2529
4798. Le compteur Négociations en mode principal réussies représente le nombre de négociations en mode principal achevées depuis le dernier démarrage d’IPSec.
4799. 2531
4800. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées par seconde.
4801. 2533
4802. Le compteur Négociations en mode principal en échec représente le nombre de négociations en mode principal ayant échoué depuis le dernier démarrage d’IPSec.
4803. 2535
4804. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué par seconde.
4805. 2537
4806. Le compteur Demandes de négociations en mode principal reçues représente le nombre de négociations en mode principal initiées par un pair depuis le dernier démarrage d’IPSec.
4807. 2539
4808. Le compteur Demandes de négociations en mode principal reçues par seconde représente le nombre de négociations en mode principal initiées par un pair par seconde.
4809. 2541
4810. Le compteur Associations de sécurité en mode principal ayant utilisé l’emprunt d’identité est le nombre d’associations de sécurité en mode principal réalisées à l’aide de l’emprunt d’identité depuis le dernier démarrage d’IPSec.
4811. 2543
4812. Le compteur Associations de sécurité en mode principal ayant utilisé l’emprunt d’identité par seconde est le nombre d’associations de sécurité en mode principal réalisées à l’aide de l’emprunt d’identité par seconde.
4813. 2545
4814. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
4815. 2547
4816. Le compteur Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
4817. 2549
4818. Le compteur Négociations en mode rapide représente le nombre de négociations en mode rapide tentées depuis le dernier démarrage d’IPSec.
4819. 2551
4820. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées par seconde.
4821. 2553
4822. Le compteur Négociations en mode rapide réussies représente le nombre de négociations en mode rapide achevées depuis le dernier démarrage d’IPSec.
4823. 2555
4824. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées par seconde.
4825. 2557
4826. Le compteur Négociations en mode rapide en échec représente le nombre de négociations en mode rapide ayant échoué depuis le dernier démarrage d’IPSec.
4827. 2559
4828. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué par seconde.
4829. 2561
4830. Le compteur Associations de sécurité actives en mode étendu représente le nombre d’associations de sécurité en mode étendu actuellement actives.
4831. 2563
4832. Le compteur Associations de sécurité en mode étendu en attente représente le nombre d’associations de sécurité en mode étendu en attente.
4833. 2565
4834. Le compteur Négociations en mode étendu représente le nombre de négociations en mode étendu tentées depuis le dernier démarrage d’IPSec.
4835. 2567
4836. Le compteur Négociations en mode étendu par seconde représente le nombre de négociations en mode étendu tentées par seconde.
4837. 2569
4838. Le compteur Négociations en mode étendu réussies représente le nombre de négociations en mode étendu réalisées depuis le dernier démarrage d’IPSec.
4839. 2571
4840. Le compteur Négociations en mode étendu réussies par seconde représente le nombre de négociations en mode étendu réalisées par seconde.
4841. 2573
4842. Le compteur Négociations en mode étendu en échec par seconde représente le nombre de négociations en mode étendu en échec depuis le dernier démarrage d’IPSec.
4843. 2575
4844. Le compteur Négociations en mode étendu en échec par seconde représente le nombre de négociations en mode étendu ayant échoué par seconde.
4845. 2577
4846. Le compteur Associations de sécurité en mode étendu ayant utilisé l’emprunt d’identité représente le nombre d’associations de sécurité en mode étendu réalisées à l’aide de l’emprunt d’identité depuis le dernier démarrage d’IPSec.
4847. 2645
4848. IPSec IKEv2 IPv6 est l’ensemble de compteurs IPSec (Internet Protocol security) IKEv2 (Internet Key Exchange Version 2) qui s’appliquent au trafic et aux connexions via le protocole IPv6 (Internet Protocol version 6).
4849. 2647
4850. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
4851. 2649
4852. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
4853. 2651
4854. Le compteur Négociations en mode principal représente le nombre de négociations en mode principal tentées depuis le dernier démarrage d’IPSec.
4855. 2653
4856. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées par seconde.
4857. 2655
4858. Le compteur Négociations en mode principal réussies représente le nombre de négociations en mode principal achevées depuis le dernier démarrage d’IPSec.
4859. 2657
4860. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées par seconde.
4861. 2659
4862. Le compteur Négociations en mode principal en échec représente le nombre de négociations en mode principal ayant échoué depuis le dernier démarrage d’IPSec.
4863. 2661
4864. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué par seconde.
4865. 2663
4866. Le compteur Demandes de négociations en mode principal reçues représente le nombre de négociations en mode principal initiées par un pair depuis le dernier démarrage d’IPSec.
4867. 2665
4868. Le compteur Demandes de négociations en mode principal reçues par seconde représente le nombre de négociations en mode principal initiées par un pair par seconde.
4869. 2667
4870. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
4871. 2669
4872. Le compteur Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
4873. 2671
4874. Le compteur Négociations en mode rapide représente le nombre de négociations en mode rapide tentées depuis le dernier démarrage d’IPSec.
4875. 2673
4876. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées par seconde.
4877. 2675
4878. Le compteur Négociations en mode rapide réussies représente le nombre de négociations en mode rapide achevées depuis le dernier démarrage d’IPSec.
4879. 2677
4880. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées par seconde.
4881. 2679
4882. Le compteur Négociations en mode rapide en échec représente le nombre de négociations en mode rapide ayant échoué depuis le dernier démarrage d’IPSec.
4883. 2681
4884. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué par seconde.
4885. 2383
4886. IPSec IKEv4 est l’ensemble de compteurs Internet Key Exchange version 1 (IKEv1) Internet Protocol Security (IPSec) qui s’appliquent au trafic et aux connexions via IPv4.
4887. 2385
4888. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
4889. 2387
4890. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
4891. 2389
4892. Le compteur Négociations en mode principal représente le nombre de négociations en mode principal tentées depuis le dernier démarrage d’IPSec.
4893. 2391
4894. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées par seconde.
4895. 2393
4896. Le compteur Négociations en mode principal réussies représente le nombre de négociations en mode principal achevées depuis le dernier démarrage d’IPSec.
4897. 2395
4898. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées par seconde.
4899. 2397
4900. Le compteur Négociations en mode principal en échec représente le nombre de négociations en mode principal ayant échoué depuis le dernier démarrage d’IPSec.
4901. 2399
4902. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué par seconde.
4903. 2401
4904. Le compteur Demandes de négociations en mode principal reçues représente le nombre de négociations en mode principal initiées par un pair depuis le dernier démarrage d’IPSec.
4905. 2403
4906. Le compteur Demandes de négociations en mode principal reçues par seconde représente le nombre de négociations en mode principal initiées par un pair par seconde.
4907. 2405
4908. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
4909. 2407
4910. Le compteur Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
4911. 2409
4912. Le compteur Négociations en mode rapide représente le nombre de négociations en mode rapide tentées depuis le dernier démarrage d’IPSec.
4913. 2411
4914. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées par seconde.
4915. 2413
4916. Le compteur Négociations en mode rapide réussies représente le nombre de négociations en mode rapide achevées depuis le dernier démarrage d’IPSec.
4917. 2415
4918. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées par seconde.
4919. 2417
4920. Le compteur Négociations en mode rapide en échec représente le nombre de négociations en mode rapide ayant échoué depuis le dernier démarrage d’IPSec.
4921. 2419
4922. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué par seconde.
4923. 2421
4924. IPSec IKEv6 est l’ensemble de compteurs Internet Protocol Security (IPSec) Internet Key Exchange version 1 (IKEv1) qui s’appliquent au trafic et aux connexions via le protocole Internet version 6.
4925. 2423
4926. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
4927. 2425
4928. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
4929. 2427
4930. Le compteur Négociations en mode principal représente le nombre de négociations en mode principal tentées depuis le dernier démarrage d’IPSec.
4931. 2429
4932. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées par seconde.
4933. 2431
4934. Le compteur Négociations en mode principal réussies représente le nombre de négociations en mode principal achevées depuis le dernier démarrage d’IPSec.
4935. 2433
4936. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées par seconde.
4937. 2435
4938. Le compteur Négociations en mode principal en échec représente le nombre de négociations en mode principal ayant échoué depuis le dernier démarrage d’IPSec.
4939. 2437
4940. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué par seconde.
4941. 2439
4942. Le compteur Demandes de négociations en mode principal reçues représente le nombre de négociations en mode principal initiées par un pair depuis le dernier démarrage d’IPSec.
4943. 2441
4944. Le compteur Demandes de négociations en mode principal reçues par seconde représente le nombre de négociations en mode principal initiées par un pair par seconde.
4945. 2443
4946. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
4947. 2445
4948. Le compteur Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
4949. 2447
4950. Le compteur Négociations en mode rapide représente le nombre de négociations en mode rapide tentées depuis le dernier démarrage d’IPSec.
4951. 2449
4952. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées par seconde.
4953. 2451
4954. Le compteur Négociations en mode rapide réussies représente le nombre de négociations en mode rapide achevées depuis le dernier démarrage d’IPSec.
4955. 2453
4956. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées par seconde.
4957. 2455
4958. Le compteur Négociations en mode rapide en échec représente le nombre de négociations en mode rapide ayant échoué depuis le dernier démarrage d’IPSec.
4959. 2457
4960. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué par seconde.
4961. 4717
4962. Statistiques du relais Teredo hébergé sur cet ordinateur.
4963. 4719
4964. Nombre total de paquets reçus par le relais Teredo.
4965. 4721
4966. Nombre total de paquets valides reçus par le relais Teredo.
4967. 4723
4968. Nombre total de bulles reçues par le relais Teredo.
4969. 4725
4970. Nombre total de paquets de données reçus par le relais Teredo.
4971. 4727
4972. Nombre total de paquets non valides reçus par le relais Teredo.
4973. 4729
4974. Nombre total de paquets non valides (erreur d’en-tête) reçus par le relais Teredo.
4975. 4731
4976. Nombre total de paquets non valides (erreur de source) reçus par le relais Teredo.
4977. 4733
4978. Nombre total de paquets non valides (erreur de destination) reçus par le relais Teredo.
4979. 4735
4980. Nombre total de paquets envoyés par le relais Teredo.
4981. 4737
4982. Nombre total de paquets correctement envoyés par le relais Teredo.
4983. 4739
4984. Nombre total de bulles envoyées par le relais Teredo.
4985. 4741
4986. Nombre total de paquets de données envoyés par le relais Teredo.
4987. 4743
4988. Nombre total de paquets qui n’ont pas pu être envoyés par le relais Teredo.
4989. 4745
4990. Nombre total de paquets qui n’ont pas pu être envoyés (erreur d’en-tête) par le relais Teredo.
4991. 4747
4992. Nombre total de paquets qui n’ont pas pu être envoyés (erreur de source) par le relais Teredo.
4993. 4749
4994. Nombre total de paquets qui n’ont pas pu être envoyés (erreur de destination) par le relais Teredo.
4995. 4751
4996. Taux de paquets reçus par le relais Teredo.
4997. 4753
4998. Taux de paquets envoyés par le relais Teredo.
4999. 4755
5000. Nombre total de paquets de données reçus par le relais Teredo en mode utilisateur.
5001. 4757
5002. Nombre total de paquets de données reçus par le relais Teredo en mode noyau.
5003. 4759
5004. Nombre total de paquets de données envoyés par le relais Teredo en mode utilisateur.
5005. 4761
5006. Nombre total de paquets de données envoyés par le relais Teredo en mode noyau.
5007. 4763
5008. Statistiques par session sur ce serveur IPHTTPS.
5009. 4765
5010. Nombre total de paquets IPv6 reçus dans cette session IPHTTPS.
5011. 4767
5012. Nombre total de paquets IPv6 envoyés dans cette session IPHTTPS.
5013. 4769
5014. Nombre total d’octets reçus dans cette session IPHTTPS.
5015. 4771
5016. Nombre total d’octets envoyés dans cette session IPHTTPS.
5017. 4773
5018. Nombre total d’erreurs de transmission dans cette session.
5019. 4775
5020. Nombre total d’erreurs de réception dans cette session.
5021. 4777
5022. Durée en secondes qui s’est écoulée depuis l’établissement de cette session.
5023. 4779
5024. Statistiques du serveur IPHTTPS sur cet ordinateur.
5025. 4781
5026. Nombre total d’octets reçus sur le serveur IPHTTPS.
5027. 4783
5028. Nombre total d’octets envoyés sur le serveur IPHTTPS.
5029. 4785
5030. Nombre total de paquets abandonnés lors de l’attente de la résolution d’un voisin.
5031. 4787
5032. Nombre total d’erreurs d’authentification.
5033. 4789
5034. Nombre total d’octets transférés au niveau de la couche liaison.
5035. 4791
5036. Nombre total d’erreurs de transmission sur le serveur.
5037. 4793
5038. Nombre total d’erreurs de réception sur le serveur.
5039. 4795
5040. Nombre total de paquets reçus sur le serveur.
5041. 4797
5042. Nombre total de paquets envoyés du serveur.
5043. 4799
5044. Nombre total de sessions sur le serveur.
5045. 4687
5046. Statistiques du serveur Teredo hébergé sur cet ordinateur.
5047. 4689
5048. Nombre total de paquets reçus par le serveur Teredo.
5049. 4691
5050. Nombre total de paquets valides reçus par le serveur Teredo.
5051. 4693
5052. Nombre total de bulles reçues par le serveur Teredo.
5053. 4695
5054. Nombre total de paquets d’écho reçus par le serveur Teredo.
5055. 4697
5056. Nombre total de sollicitations de routeur reçues par le serveur principal.
5057. 4699
5058. Nombre total de sollicitations de routeur reçues par le serveur secondaire
5059. 4701
5060. Nombre total de paquets non valides reçus par le serveur Teredo.
5061. 4703
5062. Nombre total de paquets non valides (erreur d’en-tête) reçus par le serveur Teredo.
5063. 4705
5064. Nombre total de paquets non valides (erreur de source) reçus par le serveur Teredo.
5065. 4707
5066. Nombre total de paquets non valides (erreur de destination) reçus par le serveur Teredo.
5067. 4709
5068. Nombre total de paquets non valides (erreur d’authentification) reçus par le serveur Teredo.
5069. 4711
5070. Nombre total d’annonces de routeur envoyées par le serveur principal.
5071. 4713
5072. Nombre total d’annonces de routeur envoyées par le serveur secondaire.
5073. 4715
5074. Taux de paquets reçus par le serveur Teredo.
5075. 4663
5076. Statistiques du client Teredo.
5077. 4665
5078. Nombre total de paquets de publication de routeur reçus par le client Teredo.
5079. 4667
5080. Nombre total de paquets de bulles reçus par le client Teredo.
5081. 4669
5082. Nombre total de paquets de données reçus par le client Teredo.
5083. 4671
5084. Nombre total de paquets non valides reçus par le client Teredo.
5085. 4673
5086. Nombre total de paquets de sollicitations de routeur envoyés par le client Teredo.
5087. 4675
5088. Nombre total de paquets de bulles envoyés par le client Teredo.
5089. 4677
5090. Nombre total de paquets de données envoyés par le client Teredo.
5091. 4679
5092. Nombre total de paquets de données reçus par le client Teredo en mode utilisateur.
5093. 4681
5094. Nombre total de paquets de données reçus par le client Teredo en mode noyau.
5095. 4683
5096. Nombre total de paquets de données envoyés par le client Teredo en mode utilisateur.
5097. 4685
5098. Nombre total de paquets de données envoyés par le client Teredo en mode noyau.
5099. 2247
5100. Cet ensemble de compteurs affiche des informations sur la jauge d’alimentation et l’allocation de réserve d’énergie
5101. 2249
5102. Ce compteur affiche la consommation d’énergie en milliwatts.
5103. 2251
5104. Ce compteur affiche l’allocation de réserve d’énergie pour ce périphérique ou ce sous-composant en milliwatts.
5105. 4645
5106. Ensemble des compteurs de file d’attente des requêtes
5107. 4647
5108. Nombre de requêtes dans la file d’attente
5109. 4649
5110. Antériorité de la requête la plus ancienne de la file d’attente
5111. 4651
5112. Taux auquel les requêtes arrivent dans la file d’attente
5113. 4653
5114. Taux auquel les requêtes sont rejetées de la file d’attente
5115. 4655
5116. Nombre total de requêtes rejetées de la file d’attente
5117. 4657
5118. Taux des accès cache pour la file d’attente
5119. 4625
5120. Ensemble de compteurs d’URL spécifiques au groupe
5121. 4627
5122. Taux de données envoyées par le service HTTP pour ce site
5123. 4629
5124. Taux de données reçues par le service HTTP pour ce site
5125. 4631
5126. Taux d’octets transférés (envoyés et reçus) par le service HTTP pour ce site
5127. 4633
5128. Nombre de connexions actuellement établies pour ce site
5129. 4635
5130. Nombre maximal de connexions simultanées établies pour ce site
5131. 4637
5132. Taux auquel les tentatives de connexion sont effectuées pour ce site
5133. 4639
5134. Taux auquel les demandes de méthode GET sont effectuées pour ce site
5135. 4641
5136. Taux auquel les demandes de méthode HEAD sont effectuées pour ce site
5137. 4643
5138. Nombre total de requêtes HTTP effectuées pour ce site
5139. 4611
5140. Ensemble de compteurs de service HTTP
5141. 4613
5142. Nombre total d’URI actuellement mis en cache par le noyau
5143. 4615
5144. Nombre total d’URI ajoutés au noyau depuis le démarrage du service
5145. 4617
5146. Nombre total de recherches abouties dans la mémoire cache URI du noyau
5147. 4619
5148. Nombre total de recherches infructueuses dans la mémoire cache URI du noyau
5149. 4621
5150. Nombre total de vidages du cache URI (complets ou partiels) depuis le démarrage du service
5151. 4623
5152. Nombre total d’URI supprimés du cache URI du noyau depuis le démarrage du service
5153. 7597
5154. L’objet de performance de codage RemoteFX est composé de compteurs qui mesurent la performance du codage vidéo RemoteFX
5155. 7599
5156. Nombre d’images sources fournies comme entrée au module vidéo RemoteFX par seconde
5157. 7601
5158. Rapport du nombre d’octets codés sur le nombre d’octets entrés
5159. 7603
5160. Nombre d’images envoyées au client par seconde
5161. 7605
5162. Nombre d’images ignorées par seconde en raison de l’insuffisance des ressources du client
5163. 7607
5164. Nombre d’images ignorées par seconde en raison de l’insuffisance des ressources du réseau
5165. 7609
5166. Nombre d’images ignorées par seconde en raison de l’insuffisance des ressources du serveur
5167. 7611
5168. Qualité de l’image de sortie, exprimée sous forme de pourcentage par rapport à la qualité de l’image source
5169. 7613
5170. Durée moyenne de codage d’une image
5171. 7615
5172. Nombre d’images composées par la source (DWM) par seconde
5173. 7617
5174. Compteur défini pour les compteurs réseau RemoteFX par session
5175. 7619
5176. Durée du parcours circulaire (RTT) TCP de base détectée en millisecondes
5177. 7621
5178. Durée moyenne du parcours circulaire TCP détectée en millisecondes
5179. 7623
5180. Bande passante TCP détectée en bits par seconde (bits/s)
5181. 7625
5182. Débit en bits par seconde (bits/s) de réception des données
5183. 7627
5184. Débit en bits par seconde (bits/s) de réception des données par TCP
5185. 7629
5186. Débit en bits par seconde (bits/s) de réception des données par UDP
5187. 7631
5188. Débit en paquets par seconde de réception de paquets par UDP
5189. 7633
5190. Débit en bits par seconde (bits/s) d’envoi des données
5191. 7635
5192. Débit en bits par seconde (bits/s) d’envoi des données par TCP
5193. 7637
5194. Débit en bits par seconde (bits/s) d’envoi des données par UDP
5195. 7639
5196. Débit en paquets par seconde d’envoi de paquets par UDP
5197. 7641
5198. Débit en bits par seconde (bits/s) d’envoi des données avec la priorité 0
5199. 7643
5200. Débit en bits par seconde (bits/s) d’envoi des données avec la priorité 1
5201. 7645
5202. Débit en bits par seconde (bits/s) d’envoi des données avec la priorité 2
5203. 7647
5204. Débit en bits par seconde (bits/s) d’envoi des données avec la priorité 3
5205. 7649
5206. Pourcentage de perte
5207. 7651
5208. Pourcentage de paquets retransmis
5209. 7653
5210. Pourcentage de correction des erreurs de transfert (FEC, Forward Error Correction)
5211. 7657
5212. Durée du parcours circulaire (RTT) UDP de base détectée en millisecondes
5213. 7659
5214. Durée moyenne du parcours circulaire (RTT) UDP de base détectée en millisecondes
5215. 7661
5216. Bande passante UDP détectée en bits par seconde (bits/s)
5217. 3171
5218. Compteurs de mesure des performances de Netlogon.
5219. 3173
5220. Nombre de threads attendant l’acquisition du sémaphore.
5221. 3175
5222. Nombre de threads actuellement détenteurs du sémaphore.
5223. 3177
5224. Nombre total de fois où le sémaphore a été acquis pendant la durée de vie de la connexion sur canal sécurisé (ou depuis le démarrage de l’ordinateur, pour _Total).
5225. 3179
5226. Nombre total de fois où un thread a dépassé le délai maximal en attendant le sémaphore pendant la durée de vie de la connexion sur canal sécurisé (ou depuis le démarrage de l’ordinateur, pour _Total).
5227. 3181
5228. Durée moyenne de retenue du sémaphore lors du dernier échantillonnage.
5229. 3183
5230. La valeur de base utilisée pour calculer le temps moyen de retenue du sémaphore.
5231. 5855
5232. L’objet de performance Table de routage distribué (DRT, Distributed Routing Table) est composé de compteurs qui analysent le cache DRT local ainsi que de compteurs qui mesurent le rythme auquel les messages de protocole DRT sont envoyés et reçus.
5233. 5857
5234. Le nombre de clés qui sont actuellement inscrites dans cette instance DRT.
5235. 5859
5236. Le nombre total de recherches qui ont été effectuées à l’aide de cette instance DRT.
5237. 5861
5238. Le nombre de nœuds homologues référencés dans le cache associé à cette instance DRT.
5239. 5863
5240. La mesure de la bande passante utilisée pour transmettre les messages de protocole DRT pendant l’intervalle d’échantillonnage.
5241. 5865
5242. La mesure de la bande passante utilisée pour recevoir les messages de protocole DRT pendant l’intervalle d’échantillonnage.
5243. 5867
5244. Estimation du nombre total de nœuds participant au système DRT auquel participe cette instance DRT.
5245. 5869
5246. Le nombre total de nœuds homologues ne répondant pas qui ont été supprimés du cache associé à cette instance DRT.
5247. 5871
5248. Le nombre de messages que l’instance DRT locale n’a pas réussi à envoyer en raison d’erreurs de transport DRT.
5249. 5873
5250. Le nombre de messages que l’instance DRT locale n’a pas réussi à recevoir en raison de la fragmentation des messages et du réassemblage qui a suivi, ou d’autres erreurs de transport DRT.
5251. 5875
5252. Le nombre de messages de sollicitation DRT envoyés par seconde par l’instance DRT.
5253. 5877
5254. Le nombre de messages de sollicitation DRT reçus par seconde par l’instance DRT.
5255. 5879
5256. Le nombre de messages d’annonce DRT envoyés par seconde par l’instance DRT.
5257. 5881
5258. Le nombre de messages d’annonce DRT reçus par seconde par l’instance DRT.
5259. 5883
5260. Le nombre de messages de demande DRT envoyés par seconde par l’instance DRT.
5261. 5885
5262. Le nombre de messages de demande DRT reçus par seconde par l’instance DRT.
5263. 5887
5264. Le nombre de messages de saturation DRT envoyés par seconde par l’instance DRT.
5265. 5889
5266. Le nombre de messages de saturation DRT reçus par seconde par l’instance DRT.
5267. 5891
5268. Le nombre de messages de renseignement DRT envoyés par seconde par l’instance DRT.
5269. 5893
5270. Le nombre de messages de renseignement DRT reçus par seconde par l’instance DRT.
5271. 5895
5272. Le nombre de messages d’autorité DRT envoyés par seconde par l’instance DRT.
5273. 5897
5274. Le nombre de messages d’autorité DRT reçus par seconde par l’instance DRT.
5275. 5899
5276. Le nombre de messages d’accusé de réception DRT envoyés par seconde par l’instance DRT.
5277. 5901
5278. Le nombre de messages d’accusé de réception DRT reçus par seconde par l’instance DRT.
5279. 5903
5280. Le nombre de messages de recherche DRT envoyés par seconde par l’instance DRT.
5281. 5905
5282. Le nombre de messages de recherche DRT reçus par seconde par l’instance DRT.
5283. 5907
5284. Le nombre total de messages de type non reconnu qui ont été reçus par l’instance DRT.
5285. 3107
5286. L’ensemble de compteurs Activité d’une carte d’interface réseau par processeur mesure l’activité réseau d’une carte d’interface réseau par processeur.
5287. 3109
5288. Le nombre de DPC mis en file d’attente/s est le taux moyen, en incidents par seconde, auquel NDIS a placé en file d’attente un appel de procédure différé (DPC) pour une interface.
5289. 3111
5290. Interruptions/s est le taux moyen, en incidents par seconde, auquel NDIS a reçu et traité des interruptions matérielles pour une interface.
5291. 3113
5292. Interruptions/s est le taux moyen, en incidents par seconde, auquel NDIS a reçu un appel d’indication de réception d’une interface.
5293. 3115
5294. Appels de paquets renvoyés/s est le taux moyen, en incidents par seconde, auquel la pile a renvoyé les paquets reçus à une interface.
5295. 3117
5296. Paquets reçus/s est le taux moyen, en paquets par seconde, auquel NDIS a reçu les paquets d’une interface.
5297. 3119
5298. Paquets renvoyés/s est le taux moyen, en paquets par seconde, auquel la pile a renvoyé les paquets reçus à une interface.
5299. 3121
5300. Appels de demande d’envoi/s est le taux moyen, en incidents par seconde, auquel la pile a demandé une transmission sur une interface.
5301. 3123
5302. Appels d’envoi terminés/s est le taux moyen, en incidents par seconde, auquel NDIS a reçu une notification de fin de transmission en provenance d’une interface.
5303. 3125
5304. Paquets envoyés/s est le taux moyen, en paquets par seconde, auquel la pile a demandé une transmission sur une interface.
5305. 3127
5306. Paquets terminés envoyés/s est le taux moyen, en paquets par seconde, auquel NDIS a reçu une notification de fin de transmission en provenance d’une interface.
5307. 3129
5308. Appels de création de liste Scatter Gather/s est le taux moyen, en incidents par seconde, auquel NDIS a reçu une demande de la part d’une interface en vue de créer une liste DMA Scatter Gather.
5309. 3131
5310. Appels de modification de table d’indirection RSS/s est le taux moyen, en incidents par seconde, auquel la pile a soumis une demande de modification de la table d’indirection d’une interface.
5311. 3133
5312. Indications de réception de ressources faibles/s est le taux moyen, en incidents par seconde, auquel NDIS a reçu un appel d’indication de réception en provenance d’une interface avec des ressources de réception faibles.
5313. 3135
5314. Paquets de faibles ressources reçus/s est le taux moyen, en paquets par seconde, auquel NDIS a reçu des paquets en provenance d’une interface avec des ressources de réception faibles.
5315. 3137
5316. Appels d’indication de réception de déchargement TCP/s est le taux moyen, en incidents par seconde, auquel NDIS a reçu un appel d’indication de réception de déchargement TCP provenant d’une interface réseau.
5317. 3139
5318. Appels de demande d’envoi de déchargement TCP/s est le taux moyen, en incidents par seconde, auquel le protocole TCP/IP a demandé une transmission de déchargement TCP sur une interface réseau.
5319. 3141
5320. Octets de réception de déchargement TCP/s est le taux moyen, en octets par seconde, auquel les données ont été remises par une interface réseau à l’aide de l’appel d’indication de réception de déchargement TCP.
5321. 3143
5322. Octets de déchargement TCP envoyés/s est le taux moyen, exprimé en octets par seconde, auquel les données ont été remises à une interface réseau à l’aide de l’appel de demande d’envoi de déchargement TCP. 
5323. 3145
5324. L’ensemble de compteurs Cycles d’activité réseau par processeur mesure les cycles processeur liés à l’activité réseau d’une interface sur chaque processeur.
5325. 3147
5326. Cycles d’interruptions DPC/s est le taux moyen, en cycles par seconde, auquel NDIS a traité un appel de procédure différé (DPC) pour une interface.
5327. 3149
5328. Cycles d’interruptions/s est le taux moyen, en cycles par seconde, auquel NDIS a traité les interruptions matérielles pour une interface.
5329. 3151
5330. Cycles d’indications de réception NDIS/s est le taux moyen, en cycles par seconde, auquel NDIS a traité un appel d’indication de réception provenant d’une interface.
5331. 3153
5332. Cycles d’indications de réception de pile/s est le taux moyen, en cycles par seconde, auquel la pile a traité un appel d’indication de réception provenant d’une interface.
5333. 3155
5334. Cycles de paquets renvoyés NDIS/s est le taux moyen, en cycles par seconde, auquel NDIS a traité le renvoi de paquets reçus à une interface.
5335. 3157
5336. Cycles de paquets renvoyés Miniport/s est le taux moyen, en cycles par seconde, auquel une interface a traité le renvoi de paquets reçus.
5337. 3159
5338. Cycles d’envoi NDIS/s est le taux moyen, en cycles par seconde, auquel NDIS a traité les demandes de transmission provenant de la pile pour une interface.
5339. 3161
5340. Cycles d’envoi Miniport/s est le taux moyen, en cycles par seconde, auquel une interface a traité la transmission des paquets.
5341. 3163
5342. Cycles d’envois NDIS terminés/s est le taux moyen, en cycles par seconde, auquel NDIS a traité les notifications de fin de transmission provenant d’une interface.
5343. 3165
5344. Cycles de création de ventilation-regroupement/s est le taux moyen, en cycles par seconde, auquel NDIS a traité la création de listes DMA de ventilation-regroupement pour une interface.
5345. 3167
5346. Cycles de modification de table d’indirection RSS Miniport est le taux moyen, en cycles par seconde, auquel une interface a traité la modification de la table d’indirection RSS.
5347. 3169
5348. Cycles d’envois de pile terminés/s est le taux moyen, en cycles par seconde, auquel la pile a traité les notifications de fin de transmission provenant d’une interface.
5349. 1991
5350. Les compteurs de cette collection concernent le suivi des événements individuel pour les sessions Windows.
5351. 1993
5352. Taille actuelle de la mémoire paginée allouée pour les mémoires tampons associées à cette session (en octets).
5353. 1995
5354. Taille actuelle de la mémoire non paginée allouée pour les mémoires tampons associées à cette session (en octets).
5355. 1997
5356. Vitesse à laquelle les événements sont consignés pour cette session par les fournisseurs activés pour cette session (événements/seconde).
5357. 1999
5358. Nombre total d’événements qui n’ont pas été correctement enregistrés dans le journal depuis le début de la session de suivi. Les événements sont perdus en raison d’un espace limité dans les tampons de la session. Pour éviter de perdre des événements, envisagez d’augmenter la taille ou le nombre des tampons.
5359. 2001
5360. Nombre de consommateurs qui lisent actuellement des événements provenant de cette session, en mode temps réel.
5361. 1849
5362. L’ensemble de compteurs de performance Informations sur le processeur est constitué de compteurs qui mesurent différents aspects de l’activité du processeur. Le processeur est le composant de l’ordinateur qui effectue des calculs arithmétiques et logiques, initie des opérations sur des périphériques et exécute les threads des processus. Un ordinateur peut avoir plusieurs processeurs. L’ensemble de compteurs Informations concernant le processeur représente chaque processeur sous la forme d’une instance de l’ensemble de compteurs.
5363. 1851
5364. % temps processeur est le pourcentage de temps passé par le processeur à exécuter un thread non inactif. Il est calculé en mesurant le pourcentage de temps que le processeur passe à exécuter le thread inactif, puis en soustrayant cette valeur de 100 %. (Chaque processeur a un thread inactif dont le temps d’exécution est cumulé quand aucun autre thread n’est prêt à s’exécuter.) Ce compteur est le principal indicateur de l’activité d’un processeur et il affiche le pourcentage moyen du temps occupé observé durant l’intervalle d’échantillonnage. Notez que la détermination du moment où le processeur est inactif est effectuée selon un intervalle d’échantillonnage interne du battement de l’horloge système. Sur les processeurs rapides actuels, « Pourcentage de temps processeur » peut par conséquent sous-estimer l’utilisation du processeur car celui-ci peut passer beaucoup de temps à servir des threads entre les intervalles d’échantillonnage de l’horloge système. Les applications de minutage basées sur la charge de travail sont un exemple d’applications qui seront très probablement mal mesurées, puisque les minuteurs sont signalés juste après l’échantillon.
5365. 1853
5366. % temps utilisateur est le pourcentage du temps passé par le processeur en mode Utilisateur. (Le mode Utilisateur est un mode de traitement restreint conçu pour les applications, les sous-systèmes d’environnement et les sous-systèmes intégraux. Le mode Privilégié, alternatif, est prévu pour les composants du système d’exploitation et permet l’accès direct au matériel et à toute la mémoire. Le système d’exploitation exécute les threads d’application en mode Privilégié pour accéder aux services du système d’exploitation). Ce compteur affiche le temps moyen d’occupation en tant que pourcentage de l’intervalle échantillonné.
5367. 1855
5368. % temps privilégié est le pourcentage du temps écoulé passé par les threads de processus à exécuter du code en mode Privilégié. Lorsqu’un service système Windows est appelé, le service s’exécute souvent en mode privilégié afin d’obtenir l’accès aux données privées du système. Les threads s’exécutant en mode Utilisateur n’ont pas accès à de telles données. Les appels système peuvent être explicites ou implicites tels que les défauts de page et les interruptions. À l’inverse de certains anciens systèmes d’exploitation, Windows utilise les frontières de processus pour la protection des sous-systèmes en plus de la protection traditionnelle apportée par l’utilisation des modes Utilisateur et Privilégié. Ces processus de sous-système apportent une protection supplémentaire. Ainsi, certains travaux effectués par Windows NT pour le compte de votre application peuvent apparaître dans d’autres processus de sous-système en plus du temps privilégié pour votre processus.
5369. 1857
5370. Interruptions/s est le taux moyen, en incidents par seconde auquel le processeur a reçu et corrigé des interruptions matérielles. Cela n’inclut pas les appels de procédure différés (DPC), qui sont comptés séparément. Cette valeur est un indicateur indirect de l’activité des périphériques tels que l’horloge système, la souris, les pilotes de disque, les lignes de communication de données, les cartes d’interface réseau et d’autres périphériques. Ces périphériques interrompent normalement le processeur quand ils ont fini une tâche ou qu’ils ont besoin d’assistance. L’exécution d’un thread normale est interrompue. L’horloge système interrompt le processeur toutes les 10 millisecondes, créant un arrière-plan à l’activité de l’interruption. Ce compteur affiche la différence entre les valeurs observées dans les deux derniers échantillons, divisée par la durée de l’intervalle d’échantillon.
5371. 1859
5372. % Temps DPC est le pourcentage de temps que le processeur passe à recevoir et à traiter des appels de procédures différés (DPC). Les DPC sont des interruptions qui s’exécutent à un niveau de priorité plus bas que les interruptions standard. Le % Temps DPC est un composant du % Temps privilégié puisque les DPC sont exécutés en mode Privilégié. Ils sont comptés séparément et ne font pas partie des compteurs d’interruptions. Ce compteur affiche le temps moyen d’occupation comme un pourcentage du temps échantillon.
5373. 1861
5374. % temps d’interruption est le temps que le processeur passe à recevoir et traiter des interruptions matérielles pendant l’intervalle échantillon. Cette valeur est un indicateur indirect de l’activité des périphériques qui génèrent des interruptions tels que les horloges système, la souris, les pilotes de disques, les lignes de communication de données, les cartes d’interface réseau et d’autres périphériques. Ces périphériques interrompent généralement le processeur quand une tâche est finie ou nécessite de l’attention. L’exécution d’un thread normale est interrompue pendant les interruptions. L’horloge système interrompt de manière typique le processeur toutes les 10 millisecondes, créant un arrière-plan d’activité d’interruption. Le système d’exploitation suspend l’exécution normale de thread pendant les interruptions. Ce compteur affiche le temps moyen d’occupation comme un pourcentage du temps échantillon.
5375. 1863
5376. DPC mis en file d’attente/s est le taux moyen, en incidents par secondes, auquel les appels de procédures différés (DPC) sont placés en file d’attente sur la file DPC de ce processeur. Les DPC sont des interruptions qui s’exécutent à des niveaux de priorité plus bas que les interruptions standard. Chaque processeur a sa propre file DPC. Ce compteur mesure le taux auquel les DPC sont ajoutés à la file, et non le nombre de DPC dans la file. Il affiche la différence entre les valeurs observées dans les deux derniers intervalles de temps, divisée par la durée de l’intervalle échantillon.
5377. 1865
5378. Le Taux DPC est le taux moyen auquel les appels de procédures différés (DPC) sont placés dans les files d’attente sur la file DPC de processeurs entre chaque top d’horloge du processeur. (Les DPC équivalent à des interruptions qui s’exécutent à des niveaux de priorité plus bas que les interruptions standard. Chaque processeur a sa propre file DPC). Ce compteur mesure le taux auquel les DPC sont ajoutés à la file, et non le nombre de DPC dans la file et correspond à la dernière valeur observée seulement et non à une moyenne.
5379. 1867
5380. % d’inactivité est le pourcentage de temps pendant lequel le processeur est inactif lors de l’intervalle d’échantillonnage
5381. 1869
5382. % durée C1 est le pourcentage de temps utilisé par le processeur pour l’état d’inactivité en basse puissance C1. % durée C1 est un sous-ensemble du temps total d’inactivité du processeur. L’état d’inactivité en basse puissance C1 active le processeur pour maintenir son contexte entier et le remettre rapidement en état d’exécution. L’état % C1 n’est pas pris en charge par tous les systèmes.
5383. 1871
5384. % durée C2 est le pourcentage de temps passé par le processeur dans l’état d’inactivité en basse puissance de C2. % durée C2 est un sous-ensemble de la durée totale d’inactivité du processeur. L’état d’inactivité en basse puissance C2 permet au processeur de maintenir le contexte des mémoires cache système. L’état de puissance C2 est moins performant que C1 et possède un état de latence de sortie supérieur. L’état C2 n’est pas pris en charge par tous les systèmes.
5385. 1873
5386. % durée C3 est le pourcentage de temps passé par le processeur dans l’état d’inactivité en basse puissance de C3. % durée C3 est un sous-ensemble de la durée totale d’inactivité du processeur. Lorsque le processeur est en état d’inactivité en basse puissance, il n’est pas en mesure de maintenir la cohérence de ses caches. L’état de puissance C3 est moins performant que C2 et possède un état de latence de sortie supérieur. L’état C3 n’est pas pris en charge par tous les systèmes.
5387. 1875
5388. C1 Transitions/s est la vitesse à laquelle le processeur passe en mode faible consommation C1. Le processeur passe en état C1 lorsqu’il est suffisamment inactif, et le quitte dès qu’il reçoit une interruption. Ce compteur affiche la différence entre les valeurs observées dans les deux derniers intervalles de temps, divisée par la durée de l’intervalle échantillon.
5389. 1877
5390. C2 Transitions/s est la vitesse à laquelle le processeur passe en mode faible consommation C2. Le processeur passe en état C2 lorsqu’il est suffisamment inactif, et le quitte dès qu’il reçoit une interruption. Ce compteur affiche la différence entre les valeurs observées dans les deux derniers intervalles de temps, divisée par la durée de l’intervalle échantillon.
5391. 1879
5392. C3 Transitions/s est la vitesse à laquelle le processeur passe en mode faible consommation C3. Le processeur passe en état C3 lorsqu’il est suffisamment inactif, et le quitte dès qu’il reçoit une interruption. Ce compteur affiche la différence entre les valeurs observées dans les deux derniers intervalles de temps, divisée par la durée de l’intervalle échantillon.
5393. 1881
5394. % Temps de priorité est le pourcentage de temps passé par le processeur à exécuter des threads qui n’ont pas une priorité basse. Il est calculé en mesurant le pourcentage de temps que le processeur passe à exécuter des threads de priorité basse ou le thread inactif, puis en soustrayant cette valeur de 100 %. (Chaque processeur a un thread inactif dont le temps d’exécution est cumulé quand aucun autre thread n’est prêt à s’exécuter.) Ce compteur affiche le pourcentage moyen du temps occupé observé durant l’intervalle d’échantillonnage en excluant le travail de basse priorité effectué en arrière-plan. Notez que la détermination du moment où le processeur est inactif est effectuée selon un intervalle d’échantillonnage interne du battement de l’horloge système. % Temps de priorité peut par conséquent sous-estimer l’utilisation du processeur car celui-ci peut passer beaucoup de temps à servir des threads entre les intervalles d’échantillonnage de l’horloge système. Les applications de minutage basées sur la charge de travail sont un exemple d’applications qui seront très probablement mal mesurées, puisque les minuteurs sont signalés juste après l’échantillon.
5395. 1883
5396. L’état de parcage indique si un processeur est parqué ou non.
5397. 1885
5398. La fréquence du processeur correspond à la fréquence du processeur actuel en mégahertz.
5399. 1887
5400. « % de fréquence maximale » correspond au pourcentage de fréquence maximale du processeur actuel.
5401. 1889
5402. Indicateurs de l’état du processeur
5403. 1977
5404. Les compteurs de cette collection se réfèrent à des mesures à l’échelle du système quant aux performances du suivi des événements du sous-système Windows.
5405. 1979
5406. Nombre de fournisseurs d’événements distincts qui sont activés pour les sessions ETW ; les instances multiples d’un même fournisseur ne sont comptées qu’une seule fois.
5407. 1981
5408. Nombres de fournisseurs de suivi distincts qui ont été activés pour une session de suivi, mais qui ne se sont pas encore inscrits auprès d’ETW.
5409. 1983
5410. Nombre de fournisseurs de suivi distincts qui sont inscrits auprès du sous-système de suivi, mais qui ne sont effectivement activés sur aucune session de suivi ; les instances multiples d’un même fournisseur ne sont comptées qu’une seule fois.
5411. 1985
5412. Nombre de sessions de suivi ETW actuellement actives.
5413. 1987
5414. Taille actuelle de la mémoire paginée allouée pour les mémoires tampons associées à toutes les sessions actives (en octets).
5415. 1989
5416. Taille actuelle de la mémoire non paginée allouée pour les mémoires tampons associées à toutes les sessions actives (en octets).
5417. 1891
5418. L’objet de performance Synchronisation est constitué de compteurs pour la synchronisation du noyau. L’objet de synchronisation représente chaque processeur sous la forme d’une instance de l’objet.
5419. 1893
5420. « Acquisitions de verrouillages spinlock » correspond au taux d’acquisition des verrouillages spinlock. Il inclut les acquisitions de verrouillages spinlock de base, mis en file d’attente, mis en file d’attente dans une pile et partagés.
5421. 1895
5422. « Contentions de verrouillages spinlock/seconde » correspond au taux de contention des verrouillages spinlock. Il inclut les contentions de verrouillages spinlock de base, mis en file d’attente, mis en file d’attente dans une pile et partagés.
5423. 1897
5424. « Spins de verrouillages spinlock/seconde » correspond au taux de spin des verrouillages spinlock. Il inclut les spins permettant d’acquérir des verrouillages spinlock de base, mis en file d’attente, mis en file d’attente dans une pile et partagés.
5425. 1899
5426. « Demandes de diffusion d’envoi IPI/seconde » correspond au taux des demandes de diffusion IPI. 
5427. 1901
5428. « Demandes de routine d’envoi IPI/seconde » correspond au taux des demandes de routine IPI.
5429. 1903
5430. « Interruptions logicielles d’envoi IPI/seconde » correspond au taux des interruptions logicielles.
5431. 1905
5432. Fréquence des opérations d’initialisation sur des ressources d’exécution.
5433. 1907
5434. Fréquence des opérations de réinitialisation sur des ressources d’exécution.
5435. 1909
5436. Fréquence des opérations de suppression sur des ressources d’exécution.
5437. 1911
5438. Fréquence des opérations d’acquisition sur des ressources d’exécution.
5439. 1913
5440. Taux de contention sur des ressources d’exécution.
5441. 1915
5442. Fréquence des libérations exclusives sur des ressources d’exécution.
5443. 1917
5444. Fréquence des libérations partagées sur des ressources d’exécution.
5445. 1919
5446. Fréquence des libérations partagées sur des ressources d’exécution.
5447. 1921
5448. Fréquence des tentatives d’acquisitions exclusives sur des ressources d’exécution à partir de ExAcquireResourceExclusiveLite.
5449. 1923
5450. Fréquence des premières acquisitions exclusives à partir de ExAcquireResourceExclusiveLite.
5451. 1925
5452. Fréquence des acquisitions exclusives récursives à partir de ExAcquireResourceExclusiveLite.
5453. 1927
5454. Fréquence des attentes pendant les tentatives d’acquisitions exclusives à partir de ExAcquireResourceExclusiveLite.
5455. 1929
5456. Fréquence des non-attentes pendant les tentatives d’acquisitions exclusives à partir de ExAcquireResourceExclusiveLite.
5457. 1931
5458. Fréquence des tentatives d’acquisitions partagées sur des ressources d’exécution à partir de ExAcquireResourceSharedLite.
5459. 1933
5460. Fréquence des acquisitions exclusives récursives à partir de ExAcquireResourceSharedLite.
5461. 1935
5462. Fréquence des premières acquisitions partagées à partir de ExAcquireResourceSharedLite.
5463. 1937
5464. Fréquence des acquisitions partagées récursives à partir de ExAcquireResourceSharedLite.
5465. 1939
5466. Fréquence des attentes pendant les tentatives d’acquisition à partir de ExAcquireResourceSharedLite.
5467. 1941
5468. Fréquence des non-attentes pendant les tentatives d’acquisition à partir de ExAcquireResourceSharedLite.
5469. 1943
5470. Fréquence des tentatives d’acquisitions partagées sur des ressources d’exécution à partir de ExAcquireSharedStarveExclusive.
5471. 1945
5472. Fréquence des acquisitions exclusives récursives à partir de ExAcquireSharedStarveExclusive.
5473. 1947
5474. Fréquence des premières acquisitions partagées à partir de ExAcquireSharedStarveExclusive.
5475. 1949
5476. Fréquence des acquisitions partagées récursives à partir de ExAcquireSharedStarveExclusive.
5477. 1951
5478. Fréquence des attentes pendant les tentatives d’acquisitions partagées à partir de ExAcquireSharedStarveExclusive.
5479. 1953
5480. Fréquence des non-attentes pendant les tentatives d’acquisitions partagées à partir de ExAcquireSharedStarveExclusive.
5481. 1955
5482. Fréquence des tentatives d’acquisitions partagées sur des ressources d’exécution à partir de ExAcquireSharedWaitForExclusive.
5483. 1957
5484. Fréquence des acquisitions exclusives récursives à partir de ExAcquireSharedWaitForExclusive.
5485. 1959
5486. Fréquence des premières acquisitions partagées à partir de ExAcquireSharedWaitForExclusive.
5487. 1961
5488. Fréquence des acquisitions partagées récursives à partir de ExAcquireSharedWaitForExclusive.
5489. 1963
5490. Fréquence des attentes pendant les tentatives d’acquisitions partagées à partir de ExAcquireSharedWaitForExclusive.
5491. 1965
5492. Fréquence des non-attentes pendant les tentatives d’acquisitions exclusives à partir de ExAcquireSharedWaitForExclusive.
5493. 1967
5494. Fréquence de ExSetResourceOwnerPointer pour un propriétaire exclusif.
5495. 1969
5496. Fréquence de ExSetResourceOwnerPointer pour un nouveau propriétaire partagé.
5497. 1971
5498. Fréquence de ExSetResourceOwnerPointer pour un propriétaire partagé existant.
5499. 1973
5500. Fréquence de boosting du propriétaire exclusif lors de l’attente de cette ressource d’exécution.
5501. 1975
5502. Fréquence de boosting des propriétaires partagés lors de l’attente de cette ressource d’exécution.
5503. 5249
5504. Affiche des informations sur l’utilisation et la violation des quotas pour les processus de la Gestion des services Web.
5505. 5251
5506. Affiche le nombre de demandes approuvées et rejetées par seconde provenant d’utilisateurs autorisés.
5507. 5253
5508. Affiche le nombre de violations de quota d’utilisateur.
5509. 5255
5510. Affiche le nombre de demandes ayant fait l’objet d’une limitation du système.
5511. 5257
5512. Affiche le nombre actuel de shells actifs pour tous les utilisateurs.
5513. 5259
5514. Affiche le nombre actuel d’opérations actives pour tous les utilisateurs.
5515. 5261
5516. Affiche le nombre actuel d’utilisateurs actifs autorisés.
5517. 2175
5518. Compteurs de performance du composant des services de base de module de plateforme sécurisée.
5519. 2177
5520. Le nombre de contextes TBS qui sont actuellement actifs.
5521. 2179
5522. Le nombre de ressources qui sont actuellement gérées par le TBS.
5523. " (REG_MULTI_SZ)
5524. 
5525. [HKLM\Software\Skype\Installer]
5526. "BINGSRCHFF"="7" (REG_DWORD)
5527. 
5528. [HKLM\Software\Skype\Installer]
5529. "BINGSRCHIE"="7" (REG_DWORD)
5530. 
5531. [HKLM\Software\Skype\Installer]
5532. "BINGSRCHGC"="2" (REG_DWORD)
5533. 
5534. [HKLM\System\ControlSet001\services\NlaSvc\Parameters\Internet]
5535. "EnableActiveProbing"="1" (REG_DWORD)
5536. 
5537. [HKLM\System\ControlSet002\services\NlaSvc\Parameters\Internet]
5538. "EnableActiveProbing"="1" (REG_DWORD)
5539. 
5540. [HKLM\System\CurrentControlSet\services\NlaSvc\Parameters\Internet]
5541. "EnableActiveProbing"="1" (REG_DWORD)
5542. 
5543. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5544. "SuggestionsURLFallback"="http://api.bing.com/qsml.aspx?query={searchTerms}&maxwidth={ie:maxWidth}&rowheight={ie:rowHeight}&sectionHeight={ie:sectionHeight}&FORM=IE11SS&market={language}" (REG_SZ)
5545. 
5546. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5547. "FaviconURLFallback"="http://www.bing.com/favicon.ico" (REG_SZ)
5548. 
5549. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5550. "DisplayName"="Bing" (REG_SZ)
5551. 
5552. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5553. "URL"="http://www.bing.com/search?q={searchTerms}&src=IE-SearchBox&FORM=IE11SR" (REG_SZ)
5554. 
5555. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5556. "TopResultURLFallback"="http://www.bing.com/search?q={searchTerms}&src=IE-TopResult&FORM=IE11TR" (REG_SZ)
5557. 
5558. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}]
5559. "ProviderName"="Bing" (REG_SZ)
5560. 
5561. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}]
5562. "QueryPath"="http://api.bing.com:80/officequery.asmx" (REG_SZ)
5563. 
5564. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}]
5565. "RegistrationPath"="http://api.bing.com:80/officeregistration.asmx" (REG_SZ)
5566. 
5567. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}]
5568. "AboutPath"="http://www.bing.com" (REG_SZ)
5569. 
5570. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{01ECFE54-6447-4366-815C-0CC7E68FC315}]
5571. "ServiceName"="Bing (Switzerland, French)" (REG_SZ)
5572. 
5573. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{01ECFE54-6447-4366-815C-0CC7E68FC315}]
5574. "Description"="Use the Bing Service to search for web results relevant to your query." (REG_SZ)
5575. 
5576. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{01ECFE54-6447-4366-815C-0CC7E68FC315}]
5577. "AboutPath"="http://www.bing.com?mkt=fr-ch" (REG_SZ)
5578. 
5579. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{28A79371-BD52-4D19-BEF9-D18DFC6A80E1}]
5580. "ServiceName"="Bing" (REG_SZ)
5581. 
5582. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{28A79371-BD52-4D19-BEF9-D18DFC6A80E1}]
5583. "Description"="Use the Bing Service to search for web results relevant to your query." (REG_SZ)
5584. 
5585. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{28A79371-BD52-4D19-BEF9-D18DFC6A80E1}]
5586. "AboutPath"="http://www.bing.com?mkt=en-us" (REG_SZ)
5587. 
5588. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{35200299-B488-4E67-9153-8D1E92AA30FF}]
5589. "ServiceName"="Bing (France)" (REG_SZ)
5590. 
5591. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{35200299-B488-4E67-9153-8D1E92AA30FF}]
5592. "Description"="Use the Bing Service to search for web results relevant to your query." (REG_SZ)
5593. 
5594. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{35200299-B488-4E67-9153-8D1E92AA30FF}]
5595. "AboutPath"="http://www.bing.com?mkt=fr-fr" (REG_SZ)
5596. 
5597. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{718543C7-9FEF-4D17-88CB-25B11901DF8C}]
5598. "ServiceName"="Bing (Canada, French)" (REG_SZ)
5599. 
5600. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{718543C7-9FEF-4D17-88CB-25B11901DF8C}]
5601. "Description"="Use the Bing Service to search for web results relevant to your query." (REG_SZ)
5602. 
5603. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{718543C7-9FEF-4D17-88CB-25B11901DF8C}]
5604. "AboutPath"="http://www.bing.com?mkt=fr-ca" (REG_SZ)
5605. 
5606. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{77588EDE-305E-46F0-839E-E69E3824AAE8}]
5607. "ServiceName"="Bing (Belgium, French)" (REG_SZ)
5608. 
5609. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{77588EDE-305E-46F0-839E-E69E3824AAE8}]
5610. "Description"="Use the Bing Service to search for web results relevant to your query." (REG_SZ)
5611. 
5612. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{77588EDE-305E-46F0-839E-E69E3824AAE8}]
5613. "AboutPath"="http://www.bing.com?mkt=fr-be" (REG_SZ)
5614. 
5615. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{C220179B-60CF-4693-98DC-EC98FEFB5F4A}]
5616. "ServiceName"="Bing (Canada, English)" (REG_SZ)
5617. 
5618. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{C220179B-60CF-4693-98DC-EC98FEFB5F4A}]
5619. "Description"="Use the Bing Service to search for web results relevant to your query." (REG_SZ)
5620. 
5621. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Office\14.0\Common\Research\Sources\{CFAB0A76-A2D1-4C43-A41A-3867F724B3A0}\{C220179B-60CF-4693-98DC-EC98FEFB5F4A}]
5622. "AboutPath"="http://www.bing.com?mkt=en-ca" (REG_SZ)
5623. 
5624. [HKU\S-1-5-21-4109276982-2011761245-780375862-1000\Software\Microsoft\Windows\CurrentVersion\Explorer\WordWheelQuery]
5625. "0"="bing" (REG_BINARY)
5626. 
5627. =========================
5628. 
5629. Fin à: 15:22:15 le 06/08/2014
5630. 316845 Éléments analysés
5631. 
5632. =========================
5633. E.O.F