1. ========================= SEAF 1.0.1.0 - C_XX
2.
3. Commencé à: 12:55:14 le 04/03/2019
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:\ProgramData\AVAST Software\Avast\pam\icons\bing_com.png" [ NOT_CONTENT_INDEXED|ARCHIVE | 5 Ko ]
16. TC: 10/03/2017,09:45:54 | TM: 10/03/2017,09:45:54 | DA: 10/03/2017,09:45:54
17.
18.
19. =========================
20.
21.
22. "C:\Users\All Users\AVAST Software\Avast\pam\icons\bing_com.png" [ NOT_CONTENT_INDEXED|ARCHIVE | 5 Ko ]
23. TC: 10/03/2017,09:45:54 | TM: 10/03/2017,09:45:54 | DA: 10/03/2017,09:45:54
24.
25.
26. =========================
27.
28.
29. "C:\Users\SAMSUNG\AppData\Local\Google\Chrome\User Data\Profile 2\Extensions\ibbfklbaljofpaanmpaeadejijfdddco\1.2.2_0\icons\bing.svg" [ NOT_CONTENT_INDEXED|ARCHIVE | 1 Ko ]
30. TC: 14/03/2018,12:23:17 | TM: 22/03/2017,07:22:20 | DA: 14/03/2018,12:23:17
31.
32.
33. =========================
34.
35.
36. "C:\Users\SAMSUNG\AppData\Local\Microsoft\BingSvc\BingSvc.exe" [ NOT_CONTENT_INDEXED|ARCHIVE | 144 Ko ]
37. TC: 03/02/2016,19:41:09 | TM: 03/02/2016,19:51:23 | DA: 03/02/2016,19:51:23
38.
39.
40. =========================
41.
42.
43. "C:\Users\SAMSUNG\AppData\Roaming\Mozilla\Firefox\Profiles\r738pixk.default\extensions\bingsearch.full@microsoft.com.xpi" [ NOT_CONTENT_INDEXED|ARCHIVE | 17 Ko ]
44. TC: 03/02/2016,19:40:53 | TM: 03/02/2016,19:40:53 | DA: 03/02/2016,19:40:53
45.
46.
47. =========================
48.
49.
50. "C:\Users\SAMSUNG\AppData\Roaming\Mozilla\Firefox\Profiles\r738pixk.default\searchplugins\bing-.xml" [ NOT_CONTENT_INDEXED|ARCHIVE | 6 Ko ]
51. TC: 03/02/2016,19:41:09 | TM: 03/02/2016,19:41:09 | DA: 03/02/2016,19:41:09
52.
53.
54. =========================
55.
56.
57.
58. ====== Entrée(s) du registre ======
59.
60.
61. [HKLM\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
62. ""="Bing" (REG_SZ)
63.
64. [HKLM\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
65. "URL"="http://www.bing.com/search?q={searchTerms}&FORM=IE8SRC" (REG_SZ)
66.
67. [HKLM\Software\Microsoft\Speech\PhoneConverters\Tokens\Chinese]
68. "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)
69.
70. [HKLM\Software\Microsoft\Windows NT\CurrentVersion\Perflib\009]
71. "Help"="3
72. The System performance object consists of counters that apply to more than one instance of a component processors on the computer.
73. 5
74. 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.
75. 7
76. % 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.
77. 9
78. % 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.
79. 11
80. 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.
81. 13
82. 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.
83. 15
84. 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.
85. 17
86. 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.
87. 19
88. 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.
89. 21
90. 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.
91. 23
92. % 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.
93. 25
94. 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.
95. 27
96. 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.
97. 29
98. 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.
99. 31
100. 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.
101. 33
102. 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.
103. 35
104. 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.
105. 37
106. 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.
107. 39
108. 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.
109. 41
110. 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.
111. 43
112. 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.
113. 45
114. 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.
115. 47
116. 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.
117. 49
118. 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.
119. 51
120. 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.
121. 53
122. The Browser performance object consists of counters that measure the rates of announcements, enumerations, and other Browser transmissions.
123. 55
124. Announcements Server/sec is the rate at which the servers in this domain have announced themselves to this server.
125. 57
126. 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.
127. 59
128. 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.
129. 61
130. 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.
131. 63
132. 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.
133. 65
134. 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.
135. 67
136. 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.
137. 69
138. 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.
139. 71
140. 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.
141. 73
142. 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.
143. 75
144. 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.
145. 77
146. 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.
147. 79
148. Announcements Domain/sec is the rate at which a domain has announced itself to the network.
149. 81
150. Election Packets/sec is the rate at which browser election packets have been received by this workstation.
151. 83
152. Mailslot Writes/sec is the rate at which mailslot messages have been successfully received.
153. 85
154. Server List Requests/sec is the rate at which requests to retrieve a list of browser servers have been processed by this workstation.
155. 87
156. 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.
157. 89
158. 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.
159. 91
160. 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.
161. 93
162. 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.
163. 95
164. 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.
165. 97
166. 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.
167. 99
168. 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.
169. 101
170. 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.
171. 103
172. 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.
173. 105
174. 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.
175. 107
176. 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.
177. 109
178. 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.
179. 111
180. 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.
181. 113
182. 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.
183. 115
184. 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.
185. 117
186. 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.
187. 119
188. 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.
189. 121
190. 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.
191. 123
192. 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.
193. 125
194. 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.
195. 127
196. 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.
197. 129
198. 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.
199. 131
200. Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request.
201. 133
202. 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.
203. 135
204. 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.
205. 137
206. 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.
207. 139
208. 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.
209. 141
210. 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.
211. 143
212. % 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.
213. 145
214. % 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.
215. 147
216. 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.
217. 149
218. 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.
219. 151
220. 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.
221. 153
222. 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.
223. 155
224. 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.
225. 157
226. % 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.
227. 159
228. % 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.
229. 161
230. Enumerations Server/sec is the rate at which server browse requests have been processed by this workstation.
231. 163
232. Enumerations Domain/sec is the rate at which domain browse requests have been processed by this workstation.
233. 165
234. Enumerations Other/sec is the rate at which browse requests processed by this workstation are not domain or server browse requests.
235. 167
236. Missed Server Announcements is the number of server announcements that have been missed due to configuration or allocation limits.
237. 169
238. Missed Mailslot Datagrams is the number of Mailslot Datagrams that have been discarded due to configuration or allocation limits.
239. 171
240. 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.
241. 173
242. 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.
243. 175
244. 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.
245. 177
246. 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.
247. 179
248. 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.
249. 181
250. 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.
251. 183
252. 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.
253. 185
254. 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.
255. 187
256. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes.
257. 189
258. % 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.
259. 191
260. % 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.
261. 193
262. % 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.
263. 195
264. % 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.
265. 197
266. 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.
267. 199
268. 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.
269. 201
270. % Disk Time is the percentage of elapsed time that the selected disk drive was busy servicing read or write requests.
271. 203
272. % Disk Read Time is the percentage of elapsed time that the selected disk drive was busy servicing read requests.
273. 205
274. % Disk Write Time is the percentage of elapsed time that the selected disk drive was busy servicing write requests.
275. 207
276. Avg. Disk sec/Transfer is the time, in seconds, of the average disk transfer.
277. 209
278. Avg. Disk sec/Read is the average time, in seconds, of a read of data from the disk.
279. 211
280. Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk.
281. 213
282. Disk Transfers/sec is the rate of read and write operations on the disk.
283. 215
284. Disk Reads/sec is the rate of read operations on the disk.
285. 217
286. Disk Writes/sec is the rate of write operations on the disk.
287. 219
288. Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations.
289. 221
290. Disk Read Bytes/sec is the rate at which bytes are transferred from the disk during read operations.
291. 223
292. Disk Write Bytes/sec is rate at which bytes are transferred to the disk during write operations.
293. 225
294. Avg. Disk Bytes/Transfer is the average number of bytes transferred to or from the disk during write or read operations.
295. 227
296. Avg. Disk Bytes/Read is the average number of bytes transferred from the disk during read operations.
297. 229
298. Avg. Disk Bytes/Write is the average number of bytes transferred to the disk during write operations.
299. 231
300. 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.
301. 233
302. 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.
303. 235
304. 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.
305. 237
306. 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.
307. 239
308. 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.
309. 241
310. % 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%.
311. 243
312. % 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.
313. 245
314. % 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.
315. 247
316. 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.
317. 249
318. 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.
319. 251
320. 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.
321. 253
322. 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.
323. 255
324. 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.
325. 257
326. 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.
327. 259
328. 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.
329. 261
330. 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.
331. 263
332. The Redirector performance object consists of counter that monitor network connections originating at the local computer.
333. 265
334. 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).
335. 267
336. 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).
337. 269
338. 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).
339. 271
340. 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.
341. 273
342. 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).
343. 275
344. 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).
345. 277
346. 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).
347. 279
348. 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.
349. 281
350. 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).
351. 283
352. 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.
353. 285
354. 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.
355. 287
356. 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).
357. 289
358. 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.
359. 291
360. 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.
361. 293
362. 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.
363. 295
364. 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.
365. 297
366. 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.
367. 299
368. 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.
369. 301
370. 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.
371. 303
372. 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.
373. 305
374. 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.
375. 307
376. 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.
377. 309
378. 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.
379. 311
380. 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.
381. 313
382. 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.
383. 315
384. 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.
385. 317
386. 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.
387. 319
388. 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.
389. 321
390. Connects LAN Manager 2.0 counts connections to LAN Manager 2.0 servers, including LMX servers.
391. 323
392. Connects LAN Manager 2.1 counts connections to LAN Manager 2.1 servers, including LMX servers.
393. 325
394. Connects Windows NT counts the connections to Windows 2000 or earlier computers.
395. 327
396. Server Disconnects counts the number of times a Server has disconnected your Redirector. See also Server Reconnects.
397. 329
398. 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.
399. 331
400. The Server performance object consists of counters that measure communication between the local computer and the network.
401. 333
402. The number of bytes the server has received from the network. Indicates how busy the server is.
403. 335
404. The number of bytes the server has sent on the network. Indicates how busy the server is.
405. 337
406. 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).
407. 339
408. % 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.
409. 341
410. 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.
411. 343
412. 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.
413. 345
414. The number of sessions that have terminated normally. Useful in interpreting the Sessions Times Out and Sessions Errored Out statistics--allows percentage calculations.
415. 347
416. The number of sessions that have been forced to logoff. Can indicate how many sessions were forced to logoff due to logon time constraints.
417. 349
418. 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.
419. 351
420. 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.
421. 353
422. The number of times accesses to files opened successfully were denied. Can indicate attempts to access files without proper access authorization.
423. 355
424. The number of times an internal Server Error was detected. Unexpected errors usually indicate a problem with the Server.
425. 357
426. 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.
427. 359
428. 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.
429. 361
430. 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.
431. 363
432. The number of files currently opened in the server. Indicates current server activity.
433. 365
434. The number of sessions currently active in the server. Indicates current server activity.
435. 367
436. The number of searches for files currently active in the server. Indicates current server activity.
437. 369
438. 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.
439. 371
440. The number of times allocations from nonpaged pool have failed. Indicates that the computer's physical memory is too small.
441. 373
442. 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.
443. 375
444. The number of bytes of pageable computer memory the server is currently using. Can help in determining good values for the MaxPagedMemoryUsage parameter.
445. 377
446. The number of times allocations from paged pool have failed. Indicates that the computer's physical memory or paging file are too small.
447. 379
448. 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.
449. 381
450. Server Announce Allocations Failed/sec is the rate at which server (or domain) announcements have failed due to lack of memory.
451. 383
452. Mailslot Allocations Failed is the number of times the datagram receiver has failed to allocate a buffer to hold a user mailslot write.
453. 385
454. Mailslot Receives Failed indicates the number of mailslot messages that could not be received due to transport failures.
455. 387
456. Mailslot Writes Failed is the total number of mailslot messages that have been successfully received, but that could not be written to the mailslot.
457. 389
458. 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.
459. 391
460. 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.
461. 393
462. 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.
463. 395
464. 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.
465. 397
466. % 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.
467. 399
468. The NWLink NetBIOS performance object consists of counters that monitor IPX transport rates and connections.
469. 401
470. 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.
471. 405
472. 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.
473. 407
474. 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.
475. 409
476. % Free Space is the percentage of total usable space on the selected logical disk drive that was free.
477. 411
478. Free Megabytes displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.
479. 413
480. 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.
481. 415
482. 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.
483. 417
484. 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.
485. 419
486. 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.
487. 421
488. 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.
489. 423
490. 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.
491. 425
492. 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.
493. 427
494. 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.
495. 429
496. Connections Canceled is the number of connections that were canceled. This number is an accumulator and shows a running total.
497. 431
498. 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.
499. 433
500. 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.
501. 435
502. 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.
503. 437
504. Failures No Listen is the number of connections that were rejected because the remote computer was not listening for connection requests.
505. 439
506. 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.
507. 441
508. 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.
509. 443
510. 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.
511. 445
512. 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.
513. 447
514. 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.
515. 449
516. 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.
517. 451
518. 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.
519. 453
520. 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.
521. 455
522. 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.
523. 457
524. 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.
525. 459
526. 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.
527. 461
528. 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.
529. 463
530. 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.
531. 465
532. 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.
533. 467
534. 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.
535. 469
536. 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.
537. 471
538. 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.
539. 473
540. Frames Rejected/sec is the rate at which data frames are rejected. This counter only counts the frames (packets) that carry data.
541. 475
542. 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.
543. 477
544. Expirations Response is the count of T1 timer expirations.
545. 479
546. Expirations Ack is the count of T2 timer expirations.
547. 481
548. Window Send Maximum is the maximum number of bytes of data that will be sent before waiting for an acknowledgment from the remote computer.
549. 483
550. Window Send Average is the running average number of data bytes that were sent before waiting for an acknowledgment from the remote computer.
551. 485
552. 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.
553. 487
554. 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.
555. 489
556. The NWLink IPX performance object consists of counters that measure datagram transmission to and from computers using the IPX protocol.
557. 491
558. The NWLink SPX performance object consist of counters that measure data transmission and session connections for computers using the SPX protocol.
559. 493
560. The NetBEUI performance object consists of counters that measure data transmission for network activity which conforms to the NetBIOS End User Interface standard.
561. 495
562. The NetBEUI Resource performance object consists of counters that track the use of buffers by the NetBEUI protocol.
563. 497
564. 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.
565. 499
566. 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.
567. 501
568. 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.
569. 503
570. 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.
571. 505
572. 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.
573. 507
574. 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.
575. 509
576. 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.
577. 511
578. 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.
579. 513
580. 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.
581. 515
582. Packets/sec is the rate at which packets are sent and received on the network interface.
583. 517
584. Packets Received/sec is the rate at which packets are received on the network interface.
585. 519
586. Packets Sent/sec is the rate at which packets are sent on the network interface.
587. 521
588. 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.
589. 523
590. 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.
591. 525
592. Packets Received Unicast/sec is the rate at which (subnet) unicast packets are delivered to a higher-layer protocol.
593. 527
594. 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.
595. 529
596. 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.
597. 531
598. Packets Received Errors is the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
599. 533
600. Packets Received Unknown is the number of packets received through the interface that were discarded because of an unknown or unsupported protocol.
601. 535
602. 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.
603. 537
604. 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.
605. 539
606. 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.
607. 541
608. 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.
609. 543
610. Packets Outbound Errors is the number of outbound packets that could not be transmitted because of errors.
611. 545
612. 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.
613. 547
614. 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.
615. 549
616. 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.
617. 551
618. 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.
619. 553
620. 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.
621. 555
622. 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.
623. 557
624. 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.
625. 559
626. 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.
627. 561
628. 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.
629. 563
630. 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).
631. 565
632. 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.
633. 567
634. 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.
635. 569
636. 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.
637. 571
638. Fragments Received/sec is the rate, in incidents per second, at which IP fragments that need to be reassembled at this entity are received.
639. 573
640. Fragments Re-assembled/sec is the rate, in incidents per second, at which IP fragments were successfully reassembled.
641. 575
642. 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.
643. 577
644. Fragmented Datagrams/sec is the rate, in incidents per second, at which datagrams are successfully fragmented.
645. 579
646. 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).
647. 581
648. Fragments Created/sec is the rate, in incidents per second, at which IP datagram fragments were generated as a result of fragmentation.
649. 583
650. 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.
651. 585
652. 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.
653. 587
654. Messages Received/sec is the rate, in incidents per second at which ICMP messages were received. The rate includes messages received in error.
655. 589
656. Messages Received Errors is the number of ICMP messages that the entity received but had errors, such as bad ICMP checksums, bad length, etc.
657. 591
658. Received Destination Unreachable is the number of ICMP Destination Unreachable messages received.
659. 593
660. Received Time Exceeded is the number of ICMP Time Exceeded messages received.
661. 595
662. Received Parameter Problem is the number of ICMP Parameter Problem messages received.
663. 597
664. Received Source Quench is the number of ICMP Source Quench messages received.
665. 599
666. Received Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were received.
667. 601
668. Received Echo/sec is the rate, in incidents per second, at which ICMP Echo messages were received.
669. 603
670. Received Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were received.
671. 605
672. Received Timestamp/sec is the rate, in incidents per second at which ICMP Timestamp Request messages were received.
673. 607
674. Received Timestamp Reply/sec is the rate of ICMP Timestamp Reply messages received.
675. 609
676. Received Address Mask is the number of ICMP Address Mask Request messages received.
677. 611
678. Received Address Mask Reply is the number of ICMP Address Mask Reply messages received.
679. 613
680. 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.
681. 615
682. 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.
683. 617
684. Sent Destination Unreachable is the number of ICMP Destination Unreachable messages sent.
685. 619
686. Sent Time Exceeded is the number of ICMP Time Exceeded messages sent.
687. 621
688. Sent Parameter Problem is the number of ICMP Parameter Problem messages sent.
689. 623
690. Sent Source Quench is the number of ICMP Source Quench messages sent.
691. 625
692. Sent Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were sent.
693. 627
694. Sent Echo/sec is the rate of ICMP Echo messages sent.
695. 629
696. Sent Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were sent.
697. 631
698. Sent Timestamp/sec is the rate, in incidents per second, at which ICMP Timestamp Request messages were sent.
699. 633
700. Sent Timestamp Reply/sec is the rate, in incidents per second, at which ICMP Timestamp Reply messages were sent.
701. 635
702. Sent Address Mask is the number of ICMP Address Mask Request messages sent.
703. 637
704. Sent Address Mask Reply is the number of ICMP Address Mask Reply messages sent.
705. 639
706. 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.
707. 641
708. Segments/sec is the rate at which TCP segments are sent or received using the TCP protocol.
709. 643
710. Connections Established is the number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
711. 645
712. 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.
713. 647
714. 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.
715. 649
716. 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.
717. 651
718. 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.
719. 653
720. 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.
721. 655
722. Segments Sent/sec is the rate at which segments are sent, including those on current connections, but excluding those containing only retransmitted bytes.
723. 657
724. Segments Retransmitted/sec is the rate at which segments are retransmitted, that is, segments transmitted containing one or more previously transmitted bytes.
725. 659
726. 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.
727. 661
728. Datagrams/sec is the rate at which UDP datagrams are sent or received by the entity.
729. 663
730. Datagrams Received/sec is the rate at which UDP datagrams are delivered to UDP users.
731. 665
732. Datagrams No Port/sec is the rate of received UDP datagrams for which there was no application at the destination port.
733. 667
734. 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.
735. 669
736. Datagrams Sent/sec is the rate at which UDP datagrams are sent from the entity.
737. 671
738. Disk Storage device statistics from the foreign computer
739. 673
740. The number of allocation failures reported by the disk storage device
741. 675
742. 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.
743. 677
744. The current number of system handles in use.
745. 679
746. 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.
747. 681
748. 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.
749. 683
750. 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.
751. 685
752. The total elapsed time, in seconds, that this process has been running.
753. 687
754. Alignment Fixups/sec is the rate, in incidents per seconds, at alignment faults were fixed by the system.
755. 689
756. Exception Dispatches/sec is the rate, in incidents per second, at which exceptions were dispatched by the system.
757. 691
758. 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.
759. 693
760. Logon/sec is the rate of all server logons.
761. 695
762. 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.
763. 697
764. 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.
765. 699
766. The total elapsed time (in seconds) this thread has been running.
767. 701
768. 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.
769. 703
770. The amount of the Page File instance in use in percent. See also Process\\Page File Bytes.
771. 705
772. The peak usage of the Page File instance in percent. See also Process\\Page File Bytes Peak.
773. 707
774. Starting virtual address for this thread.
775. 709
776. Current User Program Counter for this thread.
777. 711
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. No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
779. 713
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. 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.
781. 715
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. Read/Write protection allows a process to read, modify and write to these pages.
783. 717
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. 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.
785. 719
786. 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.
787. 721
788. 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.
789. 723
790. 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.
791. 725
792. 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.
793. 727
794. 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.
795. 729
796. 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.
797. 731
798. 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.
799. 733
800. 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.
801. 735
802. 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.
803. 737
804. 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.
805. 739
806. 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.
807. 741
808. The Image performance object consists of counters that monitor the virtual address usage of images executed by processes on the computer.
809. 743
810. 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.
811. 745
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. No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
813. 747
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. 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.
815. 749
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. Read/Write protection allows a process to read, modify and write to these pages.
817. 751
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. 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.
819. 753
820. 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.
821. 755
822. 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.
823. 757
824. 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.
825. 759
826. 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.
827. 761
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 No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
829. 763
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 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.
831. 765
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 Read/Write protection allows a process to read, modify and write to these pages.
833. 767
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 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.
835. 769
836. 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.
837. 771
838. 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.
839. 773
840. 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.
841. 775
842. 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.
843. 777
844. Bytes Image Reserved is the sum of all virtual memory reserved by images within this process.
845. 779
846. Bytes Image Free is the amount of virtual address space that is not in use or reserved by images within this process.
847. 781
848. Bytes Reserved is the total amount of virtual memory reserved for future use by this process.
849. 783
850. Bytes Free is the total unused virtual address space of this process.
851. 785
852. 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.
853. 787
854. The Process Address Space performance object consists of counters that monitor memory allocation and use for a selected process.
855. 789
856. 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.
857. 791
858. 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.
859. 793
860. 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.
861. 795
862. 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.
863. 797
864. 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.
865. 799
866. 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.
867. 801
868. 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.
869. 803
870. 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.
871. 805
872. 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.
873. 807
874. 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.
875. 809
876. Duplicate Master Announcements indicates the number of times that the master browser has detected another master browser on the same domain.
877. 811
878. Illegal Datagrams/sec is the rate at which incorrectly formatted datagrams have been received by the workstation.
879. 813
880. Announcements Total/sec is the sum of Announcements Server/sec and Announcements Domain/sec.
881. 815
882. 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.
883. 817
884. 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.
885. 819
886. 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.
887. 821
888. 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.
889. 823
890. 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.
891. 825
892. 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.
893. 873
894. The number of bytes transmitted total for this connection.
895. 875
896. The number of bytes received total for this connection.
897. 877
898. The number of data frames transmitted total for this connection.
899. 879
900. The number of data frames received total for this connection.
901. 881
902. The compression ratio for bytes being transmitted.
903. 883
904. The compression ratio for bytes being received.
905. 885
906. The total number of CRC Errors for this connection. CRC Errors occur when the frame received contains erroneous data.
907. 887
908. The total number of Timeout Errors for this connection. Timeout Errors occur when an expected is not received in time.
909. 889
910. 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.
911. 891
912. The total number of Alignment Errors for this connection. Alignment Errors occur when a byte received is different from the byte expected.
913. 893
914. 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.
915. 895
916. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.
917. 897
918. The number of bytes transmitted per second.
919. 899
920. The number of bytes received per second.
921. 901
922. The number of frames transmitted per second.
923. 903
924. The number of frames received per second.
925. 905
926. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.
927. 909
928. The total number of Remote Access connections.
929. 921
930. The WINS Server performance object consists of counters that monitor communications using the WINS Server service.
931. 923
932. Unique Registrations/sec is the rate at which unique registration are received by the WINS server.
933. 925
934. Group Registrations/sec is the rate at which group registration are received by the WINS server.
935. 927
936. 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.
937. 929
938. Unique Renewals/sec is the rate at which unique renewals are received by the WINS server.
939. 931
940. Group Renewals/sec is the rate at which group renewals are received by the WINS server.
941. 933
942. 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.
943. 935
944. Total Number of Releases/sec is the rate at which releases are received by the WINS server.
945. 937
946. Total Number of Queries/sec is the rate at which queries are received by the WINS server.
947. 939
948. Unique Conflicts/sec is the rate at which unique registrations/renewals received by the WINS server resulted in conflicts with records in the database.
949. 941
950. Group Conflicts/sec is the rate at which group registration received by the WINS server resulted in conflicts with records in the database.
951. 943
952. 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.
953. 945
954. Total Number of Successful Releases/sec
955. 947
956. Total Number of Failed Releases/sec
957. 949
958. Total Number of Successful Queries/sec
959. 951
960. Total Number of Failed Queries/sec
961. 953
962. 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.
963. 1001
964. Services for Macintosh AFP File Server.
965. 1003
966. The maximum amount of paged memory resources used by the MacFile Server.
967. 1005
968. The current amount of paged memory resources used by the MacFile Server.
969. 1007
970. The maximum amount of nonpaged memory resources use by the MacFile Server.
971. 1009
972. The current amount of nonpaged memory resources used by the MacFile Server.
973. 1011
974. The number of sessions currently connected to the MacFile server. Indicates current server activity.
975. 1013
976. The maximum number of sessions connected at one time to the MacFile server. Indicates usage level of server.
977. 1015
978. The number of internal files currently open in the MacFile server. This count does not include files opened on behalf of Macintosh clients.
979. 1017
980. 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.
981. 1019
982. 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.
983. 1021
984. The number of bytes read from disk per second.
985. 1023
986. The number of bytes written to disk per second.
987. 1025
988. The number of bytes received from the network per second. Indicates how busy the server is.
989. 1027
990. The number of bytes sent on the network per second. Indicates how busy the server is.
991. 1029
992. The number of outstanding work items waiting to be processed.
993. 1031
994. The maximum number of outstanding work items waiting at one time.
995. 1033
996. The current number of threads used by MacFile server. Indicates how busy the server is.
997. 1035
998. The maximum number of threads used by MacFile server. Indicates peak usage level of server.
999. 1051
1000. AppleTalk Protocol
1001. 1053
1002. Number of packets received per second by Appletalk on this port.
1003. 1055
1004. Number of packets sent per second by Appletalk on this port.
1005. 1057
1006. Number of bytes received per second by Appletalk on this port.
1007. 1059
1008. Number of bytes sent per second by Appletalk on this port.
1009. 1061
1010. Average time in milliseconds to process a DDP packet on this port.
1011. 1063
1012. Number of DDP packets per second received by Appletalk on this port.
1013. 1065
1014. Average time in milliseconds to process an AARP packet on this port.
1015. 1067
1016. Number of AARP packets per second received by Appletalk on this port.
1017. 1069
1018. Average time in milliseconds to process an ATP packet on this port.
1019. 1071
1020. Number of ATP packets per second received by Appletalk on this port.
1021. 1073
1022. Average time in milliseconds to process an NBP packet on this port.
1023. 1075
1024. Number of NBP packets per second received by Appletalk on this port.
1025. 1077
1026. Average time in milliseconds to process a ZIP packet on this port.
1027. 1079
1028. Number of ZIP packets per second received by Appletalk on this port.
1029. 1081
1030. Average time in milliseconds to process an RTMP packet on this port.
1031. 1083
1032. Number of RTMP packets per second received by Appletalk on this port.
1033. 1085
1034. Number of ATP requests retransmitted on this port.
1035. 1087
1036. Number of ATP release timers that have expired on this port.
1037. 1089
1038. Number of ATP Exactly-once transaction responses per second on this port.
1039. 1091
1040. Number of ATP At-least-once transaction responses per second on this port.
1041. 1093
1042. Number of ATP transaction release packets per second received on this port.
1043. 1095
1044. The current amount of nonpaged memory resources used by AppleTalk.
1045. 1097
1046. Number of packets routed in on this port.
1047. 1099
1048. Number of packets dropped due to resource limitations on this port.
1049. 1101
1050. Number of ATP requests retransmitted to this port.
1051. 1103
1052. Number of packets routed out on this port.
1053. 1111
1054. Provides Network Statistics for the local network segment via the Network Monitor Service.
1055. 1113
1056. The total number of frames received per second on this network segment.
1057. 1115
1058. The number of bytes received per second on this network segment.
1059. 1117
1060. The number of Broadcast frames received per second on this network segment.
1061. 1119
1062. The number of Multicast frames received per second on this network segment.
1063. 1121
1064. Percentage of network bandwidth in use on this network segment.
1065. 1125
1066. Percentage of network bandwidth which is made up of broadcast traffic on this network segment.
1067. 1127
1068. Percentage of network bandwidth which is made up of multicast traffic on this network segment.
1069. 1151
1070. The Telephony System
1071. 1153
1072. The number of telephone lines serviced by this computer.
1073. 1155
1074. The number of telephone devices serviced by this computer.
1075. 1157
1076. The number of telephone lines serviced by this computer that are currently active.
1077. 1159
1078. The number of telephone devices that are currently being monitored.
1079. 1161
1080. The rate of outgoing calls made by this computer.
1081. 1163
1082. The rate of incoming calls answered by this computer.
1083. 1165
1084. The number of applications that are currently using telephony services.
1085. 1167
1086. Current outgoing calls being serviced by this computer.
1087. 1169
1088. Current incoming calls being serviced by this computer.
1089. 1233
1090. 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.
1091. 1235
1092. 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.
1093. 1237
1094. 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.
1095. 1239
1096. 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.
1097. 1241
1098. Packet Burst IO/sec is the sum of Packet Burst Read NCPs/sec and Packet Burst Write NCPs/sec.
1099. 1261
1100. Logon Total includes all interactive logons, network logons, service logons, successful logon, and failed logons since the machine is last rebooted.
1101. 1301
1102. The Server Work Queues performance object consists of counters that monitor the length of the queues and objects in the queues.
1103. 1303
1104. 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.
1105. 1305
1106. 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.
1107. 1307
1108. 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.
1109. 1309
1110. 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.
1111. 1311
1112. 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.
1113. 1313
1114. 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.
1115. 1315
1116. 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.
1117. 1317
1118. 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.
1119. 1319
1120. 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.
1121. 1321
1122. 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.
1123. 1323
1124. 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.
1125. 1325
1126. 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.
1127. 1327
1128. 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.
1129. 1329
1130. 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.
1131. 1331
1132. 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.
1133. 1333
1134. 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.
1135. 1335
1136. 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.
1137. 1337
1138. 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.
1139. 1343
1140. 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.
1141. 1345
1142. 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.
1143. 1351
1144. % 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.
1145. 1361
1146. Counters that indicate the status of local and system Very Large memory allocations.
1147. 1363
1148. VLM % Virtual Size In Use
1149. 1365
1150. Current size of the process VLM Virtual memory space in bytes.
1151. 1367
1152. 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.
1153. 1369
1154. 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.
1155. 1371
1156. The current size of committed VLM memory space for the current process in bytes.
1157. 1373
1158. The peak size of the committed VLM memory space in bytes for the current process since the process started.
1159. 1375
1160. The current size of all committed VLM memory space in bytes for the system.
1161. 1377
1162. The peak size of all committed VLM memory space in bytes since the system was started.
1163. 1379
1164. The current size of all committed shared VLM memory space in bytes for the system.
1165. 1381
1166. 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.
1167. 1383
1168. 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.
1169. 1401
1170. 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.
1171. 1403
1172. Avg. Disk Read Queue Length is the average number of read requests that were queued for the selected disk during the sample interval.
1173. 1405
1174. Avg. Disk Write Queue Length is the average number of write requests that were queued for the selected disk during the sample interval.
1175. 1407
1176. % 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.
1177. 1409
1178. 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.
1179. 1411
1180. 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.
1181. 1413
1182. 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.
1183. 1415
1184. 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.
1185. 1417
1186. 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.
1187. 1419
1188. 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.
1189. 1421
1190. 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.
1191. 1423
1192. 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.
1193. 1425
1194. 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.
1195. 1427
1196. 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.
1197. 1451
1198. Displays performance statistics about a Print Queue.
1199. 1453
1200. Total number of jobs printed on a print queue since the last restart.
1201. 1455
1202. Number of bytes per second printed on a print queue.
1203. 1457
1204. Total number of pages printed through GDI on a print queue since the last restart.
1205. 1459
1206. Current number of jobs in a print queue.
1207. 1461
1208. Current number of references (open handles) to this printer.
1209. 1463
1210. Peak number of references (open handles) to this printer.
1211. 1465
1212. Current number of spooling jobs in a print queue.
1213. 1467
1214. Maximum number of spooling jobs in a print queue since last restart.
1215. 1469
1216. Total number of out of paper errors in a print queue since the last restart.
1217. 1471
1218. Total number of printer not ready errors in a print queue since the last restart.
1219. 1473
1220. Total number of job errors in a print queue since last restart.
1221. 1475
1222. Total number of calls from browse clients to this print server to request network browse lists since last restart.
1223. 1477
1224. Total number of calls from other print servers to add shared network printers to this server since last restart.
1225. 1479
1226. 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.
1227. 1481
1228. 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.
1229. 1483
1230. % Idle Time reports the percentage of time during the sample interval that the disk was idle.
1231. 1485
1232. 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.
1233. 1501
1234. Reports the accounting and processor usage data collected by each active named Job object.
1235. 1503
1236. Current % Processor Time shows the percentage of the sample interval that the processes in the Job object spent executing code.
1237. 1505
1238. Current % User mode Time shows the percentage of the sample interval that the processes in the Job object spent executing code in user mode.
1239. 1507
1240. 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.
1241. 1509
1242. 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.
1243. 1511
1244. 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.
1245. 1513
1246. 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.
1247. 1515
1248. Pages/Sec shows the page fault rate of all the processes in the Job object.
1249. 1517
1250. Process Count - Total shows the number of processes, both active and terminated, that are or have been associated with the Job object.
1251. 1519
1252. Process Count - Active shows the number of processes that are currently associated with the Job object.
1253. 1521
1254. Process Count - Terminated shows the number of processes that have been terminated because of a limit violation.
1255. 1523
1256. 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.
1257. 1525
1258. 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.
1259. 1527
1260. 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.
1261. 1537
1262. Received Packet Too Big is the number of received packets thatare larger than anticipated.
1263. 1539
1264. Received Membership Query is the number of packets received thatquery their membership to a group.
1265. 1541
1266. Received Membership Report is the number of packets received thatreport their membership to a group.
1267. 1543
1268. Received Membership Reduction is the number of packets received thatcancelled their membership to a group.
1269. 1545
1270. Received Router Solicit is the number of packets received thatsolicit the router.
1271. 1547
1272. Received Router Advert is the number of packets received thatadvert the router.
1273. 1549
1274. % Job object Details shows detailed performance information about the active processes that make up a Job object.
1275. 1551
1276. Received Neighbor Solicit is the number of packets received thatsolicit a neighbor.
1277. 1553
1278. Received Neighbor Advert is the number of packets received thatadvert a neighbor.
1279. 1555
1280. Sent Packet Too Big is the number of sent packets thatare larger than anticipated.
1281. 1557
1282. Sent Membership Query is the number of packets sent thatquery their membership to a group.
1283. 1559
1284. Sent Membership Report is the number of packets sent thatreport their membership to a group.
1285. 1561
1286. Sent Membership Reduction is the number of packets sent thatcancelled their membership to a group.
1287. 1563
1288. Sent Router Solicit is the number of packets sent thatsolicit the router.
1289. 1565
1290. Sent Router Advert is the number of packets sent thatadvert the router.
1291. 1567
1292. Sent Neighbor Solicit is the number of packets sent thatsolicit a neighbor.
1293. 1569
1294. Sent Neighbor Advert is the number of packets sent thatadvert a neighbor.
1295. 1571
1296. These counters track authentication performance on a per second basis.
1297. 1573
1298. This counter tracks the number of NTLM authentications processed by this computer per second.
1299. 1575
1300. This counter tracks the number of times that clients use a ticket to authenticate to this computer per second.
1301. 1577
1302. This counter tracks the number of Autonomous System (AS) requests that are being processed by the Key Distribution Center (KDC) per second. Clients use AS requests to obtain a ticket-granting ticket.
1303. 1579
1304. 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.
1305. 1581
1306. 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.
1307. 1583
1308. 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.
1309. 1585
1310. 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.
1311. 1587
1312. 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.
1313. 1589
1314. 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.
1315. 1591
1316. 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.
1317. 1593
1318. This counter tracks the number of Digest authentications that are being processed per second.
1319. 1671
1320. These counters track the number of security resources and handles used per process.
1321. 1673
1322. 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.
1323. 1675
1324. 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.
1325. 1677
1326. 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.
1327. 1679
1328. 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.
1329. 1681
1330. 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.
1331. 1683
1332. 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.
1333. 1685
1334. 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.
1335. 1747
1336. % Idle Time is the percentage of time the processor is idle during the sample interval
1337. 1749
1338. % 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.
1339. 1751
1340. % 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.
1341. 1753
1342. % 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.
1343. 1755
1344. 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.
1345. 1757
1346. 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.
1347. 1759
1348. 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.
1349. 1761
1350. Heap performance counters for must used heaps
1351. 1763
1352. Memory actively used by this heap (FreeBytes + AllocatedBytes)
1353. 1765
1354. Total virtual address space reserved for this heap (includes uncommitted ranges)
1355. 1767
1356. ReservedBytes minus last uncommitted range in each segment
1357. 1769
1358. Memory on freelists in this heap (does not include uncommitted ranges or blocks in heap cache)
1359. 1771
1360. Number of blocks on the list of free blocks >1k in size
1361. 1773
1362. 1/Average time per allocation (excluding allocs from heap cache)
1363. 1775
1364. 1/Average time per free (excluding frees to heap cache)
1365. 1777
1366. Number of uncommitted ranges in the reserved virtual address
1367. 1779
1368. Difference between number of allocations and frees (for leak detection)
1369. 1781
1370. Allocations/sec from heap cache
1371. 1783
1372. Frees/sec from heap cache
1373. 1785
1374. Allocations/sec of size <1k bytes (including heap cache)
1375. 1787
1376. Frees/sec of size <1k bytes (including heap cache)
1377. 1789
1378. Allocations/sec of size 1-8k bytes
1379. 1791
1380. Frees/sec of size 1-8k bytes
1381. 1793
1382. Allocations/sec of size over 8k bytes
1383. 1795
1384. Frees/sec of size over 8k bytes
1385. 1797
1386. Allocations/sec (including from heap cache)
1387. 1799
1388. Frees/sec (including to heap cache)
1389. 1801
1390. Total number of blocks in the heap cache
1391. 1803
1392. Largest number of blocks of any one size in the heap cache
1393. 1805
1394. (FreeBytes / CommittedBytes) *100
1395. 1807
1396. (VirtualBytes / ReservedBytes) * 100
1397. 1809
1398. Collisions/sec on the heap lock
1399. 1847
1400. End Marker
1401. 1849
1402. The Telphony System
1403. 1851
1404. The number of telephone lines serviced by this computer.
1405. 1853
1406. The number of telephone devices serviced by this computer.
1407. 1855
1408. the number of telephone lines serviced by this computer that are currently active.
1409. 1857
1410. The number of telephone devices that are currently being monitored.
1411. 1859
1412. The rate of outgoing calls made by this computer.
1413. 1861
1414. The rate of incoming calls answered by this computer.
1415. 1863
1416. The number of applications that are currently using telephony services.
1417. 1865
1418. Current outgoing calls being serviced by this computer.
1419. 1867
1420. Current incoming calls being serviced by this computer.
1421. 1869
1422. The RAS Object Type handles individual ports of the RAS device on your system.
1423. 1871
1424. The number of bytes transmitted total for this connection.
1425. 1873
1426. The number of bytes received total for this connection.
1427. 1875
1428. The number of data frames transmitted total for this connection.
1429. 1877
1430. The number of data frames received total for this connection.
1431. 1879
1432. The compression ratio for bytes being transmitted.
1433. 1881
1434. The compression ratio for bytes being received.
1435. 1883
1436. The total number of CRC Errors for this connection. CRC Errors occur when the frame received contains erroneous data.
1437. 1885
1438. The total number of Timeout Errors for this connection. Timeout Errors occur when an expected is not received in time.
1439. 1887
1440. 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.
1441. 1889
1442. The total number of Alignment Errors for this connection. Alignment Errors occur when a byte received is different from the byte expected.
1443. 1891
1444. 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.
1445. 1893
1446. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.
1447. 1895
1448. The number of bytes transmitted per second.
1449. 1897
1450. The number of bytes received per second.
1451. 1899
1452. The number of frames transmitted per second.
1453. 1901
1454. The number of frames received per second.
1455. 1903
1456. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.
1457. 1905
1458. The RAS Object Type handles all combined ports of the RAS device on your system.
1459. 1907
1460. The total number of Remote Access connections.
1461. 1909
1462. BITS Per Job Network Utilization
1463. 1911
1464. Estimate of Remote Server Speed (Bits/Sec)
1465. 1913
1466. Estimate of the local netcard's speed (Bits/Sec)
1467. 1915
1468. Estimate of most recent percent network interface utilization
1469. 1917
1470. Estimate of the IGD's Internet connection speed (Bits/Sec)
1471. 1919
1472. Estimate of most recent percent IGD Internet connection utilization
1473. 1921
1474. Size of the next download block for BITS
1475. 1923
1476. BITS download response interval (msec)
1477. 1925
1478. Estimated bandwidth available to the remote system (Bits/sec)
1479. 2247
1480. Database provides performance statistics for each process using the ESE high performance embedded database management system.
1481. 2249
1482. Pages Converted/sec is the count of times per second a database page is converted from an older database format
1483. 2251
1484. Pages Converted is the count of database pages that have been converted from an older format
1485. 2253
1486. Records Converted/sec is the count of times per second a database record is converted from an older database format
1487. 2255
1488. Records Converted is the count of database records that have been converted from an older format
1489. 2257
1490. Heap Allocs/sec is the number of memory allocations from the MP Heaps per second. [Dev Only]
1491. 2259
1492. Heap Frees/sec is the number of memory frees to the MP Heaps per second. [Dev Only]
1493. 2261
1494. Heap Allocations is the current number of memory allocations in the MP Heaps. [Dev Only]
1495. 2263
1496. Heap Bytes Allocated is the size of all memory allocations in the MP Heaps discounting heap managemnt overhead. [Dev Only]
1497. 2265
1498. Page Bytes Reserved is the size of all explicitly reserved virtual address space. [Dev Only]
1499. 2267
1500. Page Bytes Committed is the size of all explicitly committed virtual memory backing store (page file and physical memory). [Dev Only]
1501. 2269
1502. 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]
1503. 2271
1504. 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]
1505. 2273
1506. 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]
1507. 2275
1508. 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]
1509. 2277
1510. 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]
1511. 2279
1512. FCB Synchronous Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second. [Dev Only]
1513. 2281
1514. 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]
1515. 2283
1516. 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]
1517. 2285
1518. 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]
1519. 2287
1520. FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache. No file operations were required. [Dev Only]
1521. 2289
1522. No text
1523. 2291
1524. 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]
1525. 2293
1526. FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache. [Dev Only]
1527. 2295
1528. FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache. [Dev Only]
1529. 2297
1530. FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated and in use. [Dev Only]
1531. 2299
1532. 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]
1533. 2301
1534. Sessions In Use is the number of database sessions currently open for use by client threads. [Dev Only]
1535. 2303
1536. Sessions % Used is the percentage of database sessions currently open for use by client threads. [Dev Only]
1537. 2305
1538. No text
1539. 2307
1540. 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.
1541. 2309
1542. No text
1543. 2311
1544. 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.
1545. 2313
1546. 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.
1547. 2315
1548. Table Opens/sec is the number of database tables opened per second.
1549. 2317
1550. Log Bytes Write per second is the rate bytes are written to the log.
1551. 2319
1552. Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs. [Dev only]
1553. 2321
1554. Log Buffer Bytes Free is the amount of free space available in the log buffers. [Dev only]
1555. 2323
1556. 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.
1557. 2325
1558. 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]
1559. 2327
1560. 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]
1561. 2329
1562. 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]
1563. 2331
1564. 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]
1565. 2333
1566. 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]
1567. 2335
1568. 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]
1569. 2337
1570. 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]
1571. 2339
1572. 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]
1573. 2341
1574. 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]
1575. 2343
1576. 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]
1577. 2345
1578. 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]
1579. 2347
1580. 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]
1581. 2349
1582. 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]
1583. 2351
1584. 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]
1585. 2353
1586. 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]
1587. 2355
1588. 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]
1589. 2357
1590. Log Records/sec is the count of records written to the database log buffers per second. [Dev Only]
1591. 2359
1592. 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]
1593. 2361
1594. 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]
1595. 2363
1596. Log Buffer Flushes/sec is the count of times the database log buffers must be flushed per second.
1597. 2365
1598. 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.
1599. 2367
1600. 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.
1601. 2369
1602. Total number of version buckets allocated
1603. 2371
1604. Total number of version buckets allocated for FlagDelete RCEs [Dev Only]
1605. 2373
1606. 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]
1607. 2375
1608. Average length of bookmark in RCE [Dev Only]
1609. 2377
1610. 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]
1611. 2379
1612. Number of times per second a version store clean task is dispatched asynchronously to be performed [Dev Only]
1613. 2381
1614. Number of times per second a version store clean task is performed synchronously [Dev Only]
1615. 2383
1616. Number of times per second a version store clean task was discarded due to load concerns [Dev Only]
1617. 2385
1618. Number of times per second a dispatched version store cleanup task fails [Dev Only]
1619. 2387
1620. Record Inserts/sec is the rate at which records are being inserted into database tables. [Dev Only]
1621. 2389
1622. Record Deletes/sec is the rate at which records in database tables are being flagged for deletion. [Dev Only]
1623. 2391
1624. Record Deletes/sec is the rate at which records in database tables are being updated. [Dev Only]
1625. 2393
1626. 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]
1627. 2395
1628. 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]
1629. 2397
1630. Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated. [Dev Only]
1631. 2399
1632. Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables. [Dev Only]
1633. 2401
1634. Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion. [Dev Only]
1635. 2403
1636. 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]
1637. 2405
1638. 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]
1639. 2407
1640. 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]
1641. 2409
1642. Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables. [Dev Only]
1643. 2411
1644. 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]
1645. 2413
1646. 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]
1647. 2415
1648. 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]
1649. 2417
1650. 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]
1651. 2419
1652. Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed. [Dev Only]
1653. 2421
1654. Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed. [Dev Only]
1655. 2423
1656. Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table. [Dev Only]
1657. 2425
1658. Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified. [Dev Only]
1659. 2427
1660. Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion. [Dev Only]
1661. 2429
1662. Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied. [Dev Only]
1663. 2431
1664. 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]
1665. 2433
1666. 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]
1667. 2435
1668. Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables. [Dev Only]
1669. 2437
1670. Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced. [Dev Only]
1671. 2439
1672. 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]
1673. 2441
1674. Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied. [Dev Only]
1675. 2443
1676. B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second. [Dev Only]
1677. 2445
1678. B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second. [Dev Only]
1679. 2447
1680. 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]
1681. 2449
1682. B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second. [Dev Only]
1683. 2451
1684. 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]
1685. 2453
1686. B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second. [Dev Only]
1687. 2455
1688. 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]
1689. 2457
1690. 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]
1691. 2459
1692. B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second. [Dev Only]
1693. 2461
1694. 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]
1695. 2463
1696. 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]
1697. 2465
1698. 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]
1699. 2467
1700. 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]
1701. 2469
1702. 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]
1703. 2471
1704. 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]
1705. 2473
1706. 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]
1707. 2475
1708. 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]
1709. 2477
1710. B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second. [Dev Only]
1711. 2479
1712. B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second. [Dev Only]
1713. 2481
1714. B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second. [Dev Only]
1715. 2483
1716. B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second. [Dev Only]
1717. 2485
1718. B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second. [Dev Only]
1719. 2487
1720. 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]
1721. 2489
1722. 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]
1723. 2491
1724. 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]
1725. 2493
1726. 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]
1727. 2495
1728. 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.
1729. 2497
1730. No text
1731. 2499
1732. Database Cache % Clean is the percentage of the database cache that does not contain modified data. [Dev Only]
1733. 2501
1734. No text
1735. 2503
1736. Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache. [Dev Only]
1737. 2505
1738. Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache. [Dev Only]
1739. 2507
1740. Database Pages Written/sec is the rate that pages are written to the database file (s) from the database cache. [Dev Only]
1741. 2509
1742. 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]
1743. 2511
1744. Database Page Latches/sec is the rate that database pages are latched for access to their data. [Dev Only]
1745. 2513
1746. 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]
1747. 2515
1748. 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]
1749. 2517
1750. 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]
1751. 2519
1752. No text
1753. 2521
1754. 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]
1755. 2523
1756. 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]
1757. 2525
1758. 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]
1759. 2527
1760. No text
1761. 2529
1762. 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.
1763. 2531
1764. 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.
1765. 2533
1766. 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.
1767. 2535
1768. 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.
1769. 2537
1770. 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.
1771. 2539
1772. 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]
1773. 2541
1774. 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]
1775. 2543
1776. 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]
1777. 2545
1778. No text
1779. 2547
1780. 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]
1781. 2549
1782. No text
1783. 2551
1784. 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]
1785. 2553
1786. 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]
1787. 2555
1788. 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]
1789. 2557
1790. 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]
1791. 2559
1792. 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]
1793. 2561
1794. No text
1795. 2563
1796. 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]
1797. 2565
1798. 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]
1799. 2567
1800. 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]
1801. 2569
1802. 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]
1803. 2571
1804. 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]
1805. 2573
1806. 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]
1807. 2575
1808. 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]
1809. 2577
1810. 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]
1811. 2579
1812. Database Page History % Hit is the percentage of database page access history record lookups that were successful. [Dev Only]
1813. 2581
1814. No text
1815. 2583
1816. Database Page Scans/sec is the rate at which database pages are considered for eviction from the database page cache. [Dev Only]
1817. 2585
1818. 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]
1819. 2587
1820. No text
1821. 2589
1822. Streaming Backup Pages Read/sec is the rate of database read operations performed for the purpose of streaming backups. [Dev Only]
1823. 2591
1824. Online Defrag Pages Referenced/sec is the rate at which online defragmentation is touching database pages. [Dev Only]
1825. 2593
1826. Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]
1827. 2595
1828. Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation. [Dev Only]
1829. 2597
1830. Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]
1831. 2599
1832. Online Defrag Pages Re-Dirtied/sec is the rate at which online defragmentation is modifying database pages that already contained modifications. [Dev Only]
1833. 2601
1834. Online Defrag Log Records/sec is the rate at which online defragmentation is generating log records. [Dev Only]
1835. 2603
1836. Online Defrag Average Log Bytes is the average size of the log records being generated by online defragmentation. [Dev only]
1837. 2605
1838. No text
1839. 2607
1840. Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]
1841. 2609
1842. Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]
1843. 2611
1844. 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]
1845. 2613
1846. Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]
1847. 2615
1848. Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications. [Dev Only]
1849. 2617
1850. Database Tasks Log Records/sec is the rate at which background database tasks are generating log records. [Dev Only]
1851. 2619
1852. Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks. [Dev only]
1853. 2621
1854. No text
1855. 2623
1856. I/O Database Reads/sec is the rate of database read operations completed.
1857. 2625
1858. I/O Database Reads Average Latency is the average length of time, in milliseconds, per database read operation.
1859. 2627
1860. No text
1861. 2629
1862. I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation. [Dev Only]
1863. 2631
1864. No text
1865. 2633
1866. 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]
1867. 2635
1868. I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion. [Dev Only]
1869. 2637
1870. 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]
1871. 2639
1872. I/O Log Reads/sec is the rate of logfile read operations completed.
1873. 2641
1874. I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation. [Dev Only]
1875. 2643
1876. No text
1877. 2645
1878. I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation. [Dev Only]
1879. 2647
1880. No text
1881. 2649
1882. 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]
1883. 2651
1884. I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion. [Dev Only]
1885. 2653
1886. 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]
1887. 2655
1888. I/O Database Writes/sec is the rate of database write operations completed.
1889. 2657
1890. I/O Database Writes Average Latency is the average length of time, in milliseconds, per database write operation.
1891. 2659
1892. No text
1893. 2661
1894. I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation. [Dev Only]
1895. 2663
1896. No text
1897. 2665
1898. 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]
1899. 2667
1900. I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion. [Dev Only]
1901. 2669
1902. 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]
1903. 2671
1904. I/O Log Writes/sec is the rate of logfile write operations completed.
1905. 2673
1906. I/O Log Writes Average Latency is the average length of time, in milliseconds, per logfile write operation.
1907. 2675
1908. No text
1909. 2677
1910. I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation. [Dev Only]
1911. 2679
1912. No text
1913. 2681
1914. 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]
1915. 2683
1916. I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion. [Dev Only]
1917. 2685
1918. 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]
1919. 2687
1920. SLV File Table Inserts/sec is the rate at which entries are inserted into an SLV File Table in the system. [Dev Only]
1921. 2689
1922. SLV File Table Cleans/sec is the rate at which attempta are made to delete an entry from an SLV File Table in the system. [Dev Only]
1923. 2691
1924. SLV File Table Deletes/sec is the rate at which entries are deleted from an SLV File Table in the system. [Dev Only]
1925. 2693
1926. SLV File Table Entries is the total number of entries contained in all SLV File Tables in the system. [Dev Only]
1927. 2695
1928. 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]
1929. 2697
1930. 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]
1931. 2699
1932. Statistics for the ESE high performance embedded database management system by Table Class
1933. 2701
1934. Record Inserts/sec is the rate at which records are being inserted into database tables. [Dev Only]
1935. 2703
1936. Record Deletes/sec is the rate at which records in database tables are being flagged for deletion. [Dev Only]
1937. 2705
1938. Record Deletes/sec is the rate at which records in database tables are being updated. [Dev Only]
1939. 2707
1940. 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]
1941. 2709
1942. 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]
1943. 2711
1944. Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated. [Dev Only]
1945. 2713
1946. Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables. [Dev Only]
1947. 2715
1948. Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion. [Dev Only]
1949. 2717
1950. 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]
1951. 2719
1952. 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]
1953. 2721
1954. 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]
1955. 2723
1956. Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables. [Dev Only]
1957. 2725
1958. 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]
1959. 2727
1960. 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]
1961. 2729
1962. 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]
1963. 2731
1964. 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]
1965. 2733
1966. Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed. [Dev Only]
1967. 2735
1968. Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed. [Dev Only]
1969. 2737
1970. Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table. [Dev Only]
1971. 2739
1972. Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified. [Dev Only]
1973. 2741
1974. Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion. [Dev Only]
1975. 2743
1976. Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied. [Dev Only]
1977. 2745
1978. 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]
1979. 2747
1980. 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]
1981. 2749
1982. Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables. [Dev Only]
1983. 2751
1984. Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced. [Dev Only]
1985. 2753
1986. 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]
1987. 2755
1988. Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied. [Dev Only]
1989. 2757
1990. B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second. [Dev Only]
1991. 2759
1992. B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second. [Dev Only]
1993. 2761
1994. 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]
1995. 2763
1996. B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second. [Dev Only]
1997. 2765
1998. 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]
1999. 2767
2000. B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second. [Dev Only]
2001. 2769
2002. 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]
2003. 2771
2004. 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]
2005. 2773
2006. B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second. [Dev Only]
2007. 2775
2008. 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]
2009. 2777
2010. 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]
2011. 2779
2012. 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]
2013. 2781
2014. 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]
2015. 2783
2016. 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]
2017. 2785
2018. 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]
2019. 2787
2020. 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]
2021. 2789
2022. 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]
2023. 2791
2024. B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second. [Dev Only]
2025. 2793
2026. B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second. [Dev Only]
2027. 2795
2028. B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second. [Dev Only]
2029. 2797
2030. B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second. [Dev Only]
2031. 2799
2032. B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second. [Dev Only]
2033. 2801
2034. 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]
2035. 2803
2036. 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]
2037. 2805
2038. 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]
2039. 2807
2040. 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]
2041. 2809
2042. 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.
2043. 2811
2044. Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache. [Dev Only]
2045. 2813
2046. Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache. [Dev Only]
2047. 2815
2048. Database Pages Written/sec is the rate that pages are written to the database file (s) from the database cache. [Dev Only]
2049. 2817
2050. 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]
2051. 2819
2052. 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]
2053. 2821
2054. 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]
2055. 2823
2056. 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]
2057. 2825
2058. 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]
2059. 2827
2060. 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]
2061. 2829
2062. 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]
2063. 2831
2064. 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]
2065. 2833
2066. 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]
2067. 2835
2068. 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]
2069. 2837
2070. 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]
2071. 2839
2072. 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]
2073. 2841
2074. Instances in this process
2075. 2843
2076. Pages Converted/sec is the count of times per second a database page is converted from an older database format
2077. 2845
2078. Pages Converted is the count of database pages that have been converted from an older format
2079. 2847
2080. Records Converted/sec is the count of times per second a database record is converted from an older database format
2081. 2849
2082. Records Converted is the count of database records that have been converted from an older format
2083. 2851
2084. 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]
2085. 2853
2086. 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]
2087. 2855
2088. 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]
2089. 2857
2090. 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]
2091. 2859
2092. 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]
2093. 2861
2094. FCB Synchronous Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second. [Dev Only]
2095. 2863
2096. 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]
2097. 2865
2098. 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]
2099. 2867
2100. 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]
2101. 2869
2102. FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache. No file operations were required. [Dev Only]
2103. 2871
2104. No text
2105. 2873
2106. 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]
2107. 2875
2108. FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache. [Dev Only]
2109. 2877
2110. FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache. [Dev Only]
2111. 2879
2112. FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated and in use. [Dev Only]
2113. 2881
2114. 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]
2115. 2883
2116. Sessions In Use is the number of database sessions currently open for use by client threads. [Dev Only]
2117. 2885
2118. Sessions % Used is the percentage of database sessions currently open for use by client threads. [Dev Only]
2119. 2887
2120. No text
2121. 2889
2122. 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.
2123. 2891
2124. No text
2125. 2893
2126. 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.
2127. 2895
2128. 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.
2129. 2897
2130. Table Opens/sec is the number of database tables opened per second.
2131. 2899
2132. Log Bytes Write per second is the rate bytes are written to the log.
2133. 2901
2134. Log Buffer Size is the amount of memory, in bytes, allocated for the database log buffers. [Dev Only]
2135. 2903
2136. Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs. [Dev only]
2137. 2905
2138. Log Buffer Bytes Free is the amount of free space available in the log buffers. [Dev only]
2139. 2907
2140. 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.
2141. 2909
2142. Log File Size is the size, in bytes, of the database log files. [Dev Only]
2143. 2911
2144. 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]
2145. 2913
2146. 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.
2147. 2915
2148. 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]
2149. 2917
2150. 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]
2151. 2919
2152. 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]
2153. 2921
2154. 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]
2155. 2923
2156. 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]
2157. 2925
2158. 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]
2159. 2927
2160. 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]
2161. 2929
2162. 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]
2163. 2931
2164. 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]
2165. 2933
2166. 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]
2167. 2935
2168. 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]
2169. 2937
2170. 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]
2171. 2939
2172. 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]
2173. 2941
2174. 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]
2175. 2943
2176. Log Records/sec is the count of records written to the database log buffers per second. [Dev Only]
2177. 2945
2178. 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]
2179. 2947
2180. 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]
2181. 2949
2182. Log Buffer Flushes/sec is the count of times the database log buffers must be flushed per second.
2183. 2951
2184. 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.
2185. 2953
2186. 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.
2187. 2955
2188. Total number of version buckets allocated
2189. 2957
2190. Total number of version buckets allocated for FlagDelete RCEs [Dev Only]
2191. 2959
2192. 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]
2193. 2961
2194. Average length of bookmark in RCE [Dev Only]
2195. 2963
2196. 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]
2197. 2965
2198. Number of times per second a version store clean task is dispatched asynchronously to be performed [Dev Only]
2199. 2967
2200. Number of times per second a version store clean task is performed synchronously [Dev Only]
2201. 2969
2202. Number of times per second a version store clean task was discarded due to load concerns [Dev Only]
2203. 2971
2204. Number of times per second a dispatched version store cleanup task fails [Dev Only]
2205. 2973
2206. Record Inserts/sec is the rate at which records are being inserted into database tables. [Dev Only]
2207. 2975
2208. Record Deletes/sec is the rate at which records in database tables are being flagged for deletion. [Dev Only]
2209. 2977
2210. Record Deletes/sec is the rate at which records in database tables are being updated. [Dev Only]
2211. 2979
2212. 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]
2213. 2981
2214. 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]
2215. 2983
2216. Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated. [Dev Only]
2217. 2985
2218. Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables. [Dev Only]
2219. 2987
2220. Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion. [Dev Only]
2221. 2989
2222. 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]
2223. 2991
2224. 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]
2225. 2993
2226. 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]
2227. 2995
2228. Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables. [Dev Only]
2229. 2997
2230. 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]
2231. 2999
2232. 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]
2233. 3001
2234. 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]
2235. 3003
2236. 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]
2237. 3005
2238. Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed. [Dev Only]
2239. 3007
2240. Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed. [Dev Only]
2241. 3009
2242. Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table. [Dev Only]
2243. 3011
2244. Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified. [Dev Only]
2245. 3013
2246. Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion. [Dev Only]
2247. 3015
2248. Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied. [Dev Only]
2249. 3017
2250. 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]
2251. 3019
2252. 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]
2253. 3021
2254. Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables. [Dev Only]
2255. 3023
2256. Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced. [Dev Only]
2257. 3025
2258. 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]
2259. 3027
2260. Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied. [Dev Only]
2261. 3029
2262. B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second. [Dev Only]
2263. 3031
2264. B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second. [Dev Only]
2265. 3033
2266. 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]
2267. 3035
2268. B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second. [Dev Only]
2269. 3037
2270. 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]
2271. 3039
2272. B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second. [Dev Only]
2273. 3041
2274. 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]
2275. 3043
2276. 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]
2277. 3045
2278. B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second. [Dev Only]
2279. 3047
2280. 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]
2281. 3049
2282. 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]
2283. 3051
2284. 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]
2285. 3053
2286. 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]
2287. 3055
2288. 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]
2289. 3057
2290. 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]
2291. 3059
2292. 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]
2293. 3061
2294. 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]
2295. 3063
2296. B+ Tree Inserts/sec is the count of times a record is inserted in a database B+ Tree per second. [Dev Only]
2297. 3065
2298. B+ Tree Replaces/sec is the count of times a record is replaced in a database B+ Tree per second. [Dev Only]
2299. 3067
2300. B+ Tree Flag Deletes/sec is the count of times a record is flag deleted in a database B+ Tree per second. [Dev Only]
2301. 3069
2302. B+ Tree Deletes/sec is the count of times a record is deleted in a database B+ Tree per second. [Dev Only]
2303. 3071
2304. B+ Tree Appends/sec is the count of times a record is appended to a database B+ Tree per second. [Dev Only]
2305. 3073
2306. 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]
2307. 3075
2308. 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]
2309. 3077
2310. 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]
2311. 3079
2312. 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]
2313. 3081
2314. Database Pages Read Async/sec is the rate that pages are asynchronously read from the database file(s) into the database cache. [Dev Only]
2315. 3083
2316. Database Pages Read Sync/sec is the rate that pages are synchronously read from the database file(s) into the database cache. [Dev Only]
2317. 3085
2318. Database Pages Written/sec is the rate that pages are written to the database file (s) from the database cache. [Dev Only]
2319. 3087
2320. 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]
2321. 3089
2322. 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]
2323. 3091
2324. 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]
2325. 3093
2326. 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]
2327. 3095
2328. 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]
2329. 3097
2330. 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]
2331. 3099
2332. 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]
2333. 3101
2334. 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]
2335. 3103
2336. 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]
2337. 3105
2338. 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]
2339. 3107
2340. 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]
2341. 3109
2342. 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]
2343. 3111
2344. Streaming Backup Pages Read/sec is the rate of database read operationsperformed for the purpose of streaming backups.
2345. 3113
2346. Online Defrag Pages Referenced/sec is the rate at which online defragmentation is touching database pages. [Dev Only]
2347. 3115
2348. Online Defrag Pages Read/sec is the rate of database read operations being performed by online defragmentation. [Dev Only]
2349. 3117
2350. Online Defrag Pages Preread/sec is the rate at which database pages are read in anticipation of future use by online defragmentation. [Dev Only]
2351. 3119
2352. Online Defrag Pages Dirtied/sec is the rate at which online defragmentation is modifying clean database pages. [Dev Only]
2353. 3121
2354. Online Defrag Pages Re-Dirtied/sec is the rate at which online defragmentation is modifying database pages that already contained modifications. [Dev Only]
2355. 3123
2356. Online Defrag Log Records/sec is the rate at which online defragmentation is generating log records. [Dev Only]
2357. 3125
2358. Online Defrag Average Log Bytes is the average size of the log records being generated by online defragmentation. [Dev only]
2359. 3127
2360. No text
2361. 3129
2362. Database Tasks Pages Referenced/sec is the rate at which background database tasks are touching database pages. [Dev Only]
2363. 3131
2364. Database Tasks Pages Read/sec is the rate of database read operations being performed by background database tasks. [Dev Only]
2365. 3133
2366. 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]
2367. 3135
2368. Database Tasks Pages Dirtied/sec is the rate at which background database tasks are modifying clean database pages. [Dev Only]
2369. 3137
2370. Database Tasks Pages Re-Dirtied/sec is the rate at which background databases tasks are modifying database pages that already contained modifications. [Dev Only]
2371. 3139
2372. Database Tasks Log Records/sec is the rate at which background database tasks are generating log records. [Dev Only]
2373. 3141
2374. Database Tasks Average Log Bytes is the average size of the log records being generated by background database tasks. [Dev only]
2375. 3143
2376. No text
2377. 3145
2378. I/O Database Reads/sec is the rate of database read operations completed.
2379. 3147
2380. I/O Database Reads Average Latency is the average length of time, in milliseconds, per database read operation.
2381. 3149
2382. No text
2383. 3151
2384. I/O Database Reads Average Bytes is the average number of bytes transferred per database read operation. [Dev Only]
2385. 3153
2386. No text
2387. 3155
2388. 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]
2389. 3157
2390. I/O Database Reads Async Pending is the number of database read operations asynchronously pending completion. [Dev Only]
2391. 3159
2392. 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]
2393. 3161
2394. I/O Log Reads/sec is the rate of logfile read operations completed.
2395. 3163
2396. I/O Log Reads Average Latency is the average length of time, in milliseconds, per logfile read operation. [Dev Only]
2397. 3165
2398. No text
2399. 3167
2400. I/O Log Reads Average Bytes is the average number of bytes transferred per logfile read operation. [Dev Only]
2401. 3169
2402. No text
2403. 3171
2404. 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]
2405. 3173
2406. I/O Log Reads Async Pending is the number of logfile read operations asynchronously pending completion. [Dev Only]
2407. 3175
2408. 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]
2409. 3177
2410. I/O Database Writes/sec is the rate of database write operations completed.
2411. 3179
2412. I/O Database Writes Average Latency is the average length of time, in milliseconds, per database write operation.
2413. 3181
2414. No text
2415. 3183
2416. I/O Database Writes Average Bytes is the average number of bytes transferred per database write operation. [Dev Only]
2417. 3185
2418. No text
2419. 3187
2420. 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]
2421. 3189
2422. I/O Database Writes Async Pending is the number of database write operations asynchronously pending completion. [Dev Only]
2423. 3191
2424. 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]
2425. 3193
2426. I/O Log Writes/sec is the rate of logfile write operations completed.
2427. 3195
2428. I/O Log Writes Average Latency is the average length of time, in milliseconds, per logfile write operation.
2429. 3197
2430. No text
2431. 3199
2432. I/O Log Writes Average Bytes is the average number of bytes transferred per logfile write operation. [Dev Only]
2433. 3201
2434. No text
2435. 3203
2436. 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]
2437. 3205
2438. I/O Log Writes Async Pending is the number of logfile write operations asynchronously pending completion. [Dev Only]
2439. 3207
2440. 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]
2441. 3209
2442. Microsoft Distributed Transaction Coordinator performance counters
2443. 3211
2444. Number of currently active transactions
2445. 3213
2446. Number of committed transactions
2447. 3215
2448. Number of aborted transactions
2449. 3217
2450. Number of in doubt transactions
2451. 3219
2452. Maximum number of transactions ever concurrently active
2453. 3221
2454. Number of transactions committed by the system administrator
2455. 3223
2456. Number of transactions aborted by the system administrator
2457. 3225
2458. Minimum time delta between transaction begin and commit
2459. 3227
2460. Average time delta between transaction begin and commit
2461. 3229
2462. Maximum time delta between transaction begin and commit
2463. 3231
2464. Transactions performed per second
2465. 3233
2466. Transactions committed per second
2467. 3235
2468. Transactions aborted per second
2469. 3425
2470. Displays the current bulk transfer rate in bytes/sec.
2471. 3427
2472. Displays the current isochronous transfer rate in bytes/sec.
2473. 3429
2474. Displays the current interrupt transfer rate in bytes/sec.
2475. 3431
2476. Displays the current control transfer rate in bytes/sec.
2477. 3433
2478. Displays the rate of PCI interrupt generation by the USB controller. For controller instances only.
2479. 3435
2480. Displays the current rate Work Signals generated per second by the usbport driver. For controller instances only.
2481. 3437
2482. Displays the percentage of BW reserved for interrupt transfers
2483. 3439
2484. Displays the percentage of BW reserved for ISO transfers
2485. 3441
2486. USB I/O Counters
2487. 3443
2488. Displays the average size of all transfer URBs. For device instances only.
2489. 3445
2490. Number of ISO packets that are NOT late, but complete with an error. For device instances only.
2491. 3447
2492. Avg number of ms between the current frame and the start frame of an ISO transfer when scheduled. For device instances only.
2493. 3449
2494. Number of Transfer URBs completing with an error status. For device instances only.
2495. 3451
2496. Non-zero value if the host controller is not running(idle).
2497. 3453
2498. Non-Zero value if the host controller async schedule is not running(idle).
2499. 3455
2500. Incremented each time the controller async cache is flushed.
2501. 3457
2502. Non-Zero if the periodic schedule is not running(idle).
2503. 3459
2504. Incremented each time the controller periodic cache is flushed.
2505. 3461
2506. Help not available.
2507. 3463
2508. The cumulative total number of socket connections established for this process since the process was started.
2509. 3465
2510. 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.
2511. 3467
2512. 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.
2513. 3469
2514. The cumulative total number of datagram packets received since the process was started.
2515. 3471
2516. The cumulative total number of datagram packets sent since the process was started.
2517. 3473
2518. Counters for System.Data.SqlClient
2519. 3475
2520. The number of actual connections per second that are being made to servers
2521. 3477
2522. The number of actual disconnects per second that are being made to servers
2523. 3479
2524. The number of connections we get from the pool per second
2525. 3481
2526. The number of connections we return to the pool per second
2527. 3483
2528. The number of connections that are not using connection pooling
2529. 3485
2530. The number of connections that are managed by the connection pooler
2531. 3487
2532. The number of unique connection strings
2533. 3489
2534. The number of unique connection strings waiting for pruning
2535. 3491
2536. The number of active connection pools
2537. 3493
2538. The number of inactive connection pools
2539. 3495
2540. The number of connections currently in-use
2541. 3497
2542. The number of connections currently available for use
2543. 3499
2544. The number of connections currently waiting to be made ready for use
2545. 3501
2546. The number of connections we reclaim from GCed external connections
2547. 3503
2548. .Net CLR Data
2549. 3505
2550. Current number of connections, pooled or not.
2551. 3507
2552. Current number of connections in all pools associated with the process.
2553. 3509
2554. Current number of pools associated with the process.
2555. 3511
2556. The highest number of connections in all pools since the process started.
2557. 3513
2558. The total number of connection open attempts that have failed for any reason.
2559. 3515
2560. The total number of command executes that have failed for any reason.
2561. 3517
2562. Counters for CLR Garbage Collected heap.
2563. 3519
2564. 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.
2565. 3521
2566. 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.
2567. 3523
2568. 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.
2569. 3525
2570. 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.
2571. 3527
2572. 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.
2573. 3529
2574. 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.
2575. 3531
2576. 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.
2577. 3533
2578. 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.
2579. 3535
2580. This counter displays the process ID of the CLR process instance being monitored.
2581. 3537
2582. 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.
2583. 3539
2584. 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.
2585. 3541
2586. 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.
2587. 3543
2588. 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.
2589. 3545
2590. 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.
2591. 3547
2592. 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.
2593. 3549
2594. 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.
2595. 3551
2596. 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.
2597. 3553
2598. % 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.
2599. 3555
2600. Not Displayed.
2601. 3557
2602. 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.
2603. 3559
2604. 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).
2605. 3561
2606. 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.)
2607. 3563
2608. 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.
2609. 3565
2610. 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.
2611. 3567
2612. Statistics for CLR Class Loader.
2613. 3569
2614. This counter displays the cumulative number of classes loaded in all Assemblies since the start of this application.
2615. 3571
2616. Reserved for future use.
2617. 3573
2618. Reserved for future use.
2619. 3575
2620. 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.
2621. 3577
2622. 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.
2623. 3579
2624. 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.)
2625. 3581
2626. 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.
2627. 3583
2628. 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.
2629. 3585
2630. This counter displays the current number of classes loaded in all Assemblies.
2631. 3587
2632. 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.
2633. 3589
2634. 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.
2635. 3591
2636. 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.
2637. 3593
2638. 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.
2639. 3595
2640. 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.
2641. 3597
2642. 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.
2643. 3599
2644. 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.
2645. 3601
2646. Stats for CLR Jit.
2647. 3603
2648. 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.
2649. 3605
2650. 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.
2651. 3607
2652. 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.
2653. 3609
2654. 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.
2655. 3611
2656. 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.
2657. 3613
2658. 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.
2659. 3615
2660. Not Displayed.
2661. 3617
2662. Stats for CLR interop.
2663. 3619
2664. 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.
2665. 3621
2666. 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.
2667. 3623
2668. 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.
2669. 3625
2670. Reserved for future use.
2671. 3627
2672. Reserved for future use.
2673. 3629
2674. Stats for CLR Locks and Threads.
2675. 3631
2676. 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.
2677. 3633
2678. 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.
2679. 3635
2680. 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.
2681. 3637
2682. This counter displays the total number of threads that waited to acquire some managed lock since the start of the application.
2683. 3639
2684. 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.
2685. 3641
2686. 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.
2687. 3643
2688. 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.
2689. 3645
2690. 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.
2691. 3647
2692. 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.
2693. 3649
2694. 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.
2695. 3651
2696. Stats for CLR Security.
2697. 3653
2698. 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.
2699. 3655
2700. Reserved for future use.
2701. 3657
2702. 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.
2703. 3659
2704. 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.
2705. 3661
2706. Not Displayed.
2707. 3663
2708. 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.
2709. 3665
2710. Stats for CLR Remoting.
2711. 3667
2712. 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.
2713. 3669
2714. 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.
2715. 3671
2716. 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.
2717. 3673
2718. 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.
2719. 3675
2720. 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.
2721. 3677
2722. 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.
2723. 3679
2724. 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.
2725. 3681
2726. Runtime statistics on CLR exception handling.
2727. 3683
2728. 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.
2729. 3685
2730. 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.
2731. 3687
2732. 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.
2733. 3689
2734. 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.
2735. 3691
2736. 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.
2737. 3693
2738. Counters for System.Data.OracleClient
2739. 3695
2740. The number of actual connections per second that are being made to servers
2741. 3697
2742. The number of actual disconnects per second that are being made to servers
2743. 3699
2744. The number of connections we get from the pool per second
2745. 3701
2746. The number of connections we return to the pool per second
2747. 3703
2748. The number of connections that are not using connection pooling
2749. 3705
2750. The number of connections that are managed by the connection pooler
2751. 3707
2752. The number of unique connection strings
2753. 3709
2754. The number of unique connection strings waiting for pruning
2755. 3711
2756. The number of active connection pools
2757. 3713
2758. The number of inactive connection pools
2759. 3715
2760. The number of connections currently in-use
2761. 3717
2762. The number of connections currently available for use
2763. 3719
2764. The number of connections currently waiting to be made ready for use
2765. 3721
2766. The number of connections we reclaim from GCed external connections
2767. 3723
2768. Counters for the Windows Search Service Gatherer Project object
2769. 3725
2770. The number of add notifications.
2771. 3727
2772. The number of document additions per second.
2773. 3729
2774. The number of delete notifications.
2775. 3731
2776. The number of document deletes per second.
2777. 3733
2778. The number of modify notifications.
2779. 3735
2780. The number of modify notifications per second.
2781. 3737
2782. 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.
2783. 3739
2784. The number of documents in progress.
2785. 3741
2786. The number of documents on hold because a document with the same URL is currently in process.
2787. 3743
2788. The number of documents delayed due to site hit frequency rules.
2789. 3745
2790. The number of files (URLs) in the history list. This indicates the total size of your document corpus that was indexed.
2791. 3747
2792. The number of documents processed since the history has been reset.
2793. 3749
2794. The number of documents processed per second.
2795. 3751
2796. The number of successfully filtered documents.
2797. 3753
2798. The number of successfully filtered documents per second.
2799. 3755
2800. The number of filtered documents which returned an error.
2801. 3757
2802. The number of filtered documents which returned an error per second.
2803. 3763
2804. The number of file protocol errors received while getting documents.
2805. 3765
2806. The number of file protocol errors received per second.
2807. 3771
2808. The number of documents accessed via file system.
2809. 3773
2810. The number of documents accessed via file system per second.
2811. 3779
2812. The number of office documents filtered.
2813. 3781
2814. The number of office documents filtered per second.
2815. 3783
2816. The number of text documents filtered.
2817. 3785
2818. The number of text documents filtered per second.
2819. 3787
2820. Number of crawls in progress.
2821. 3789
2822. The Gatherer paused flag indicates if the Gatherer has been paused.
2823. 3791
2824. The recovery in progress flag indicates if recovery is currently in progress. Indexing will not be resumed until this flag is off.
2825. 3793
2826. The number of documents which were not filtered because no modification was detected since the last crawl.
2827. 3795
2828. The Iterating history in progress flag indicates if the Gatherer is currently iterating over the URL history.
2829. 3797
2830. Number of incremental crawls in progress.
2831. 3799
2832. The number of documents currently being filtered.
2833. 3801
2834. 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.
2835. 3803
2836. The total number of times a document access has been retried. Having this number high may indicate a problem with accessing the data.
2837. 3805
2838. The number of retries per second.
2839. 3813
2840. Documents incorrectly rejected by adaptive crawl
2841. 3819
2842. Documents which have changed since the last crawl
2843. 3821
2844. The number of Move/Rename notifications.
2845. 3823
2846. The number of document Moves and Renames per second.
2847. 3825
2848. Number of unique documents in the system. Documents are considered not unique if their contents is the same.
2849. 3827
2850. Percentage of the history recovery completed
2851. 3829
2852. Counters for the Windows Search Service Gathering service object
2853. 3831
2854. Currently connected external notification sources.
2855. 3833
2856. The total number of notifications received from all notification sources excluding file system.
2857. 3835
2858. The rate of external notifications received per second.
2859. 3837
2860. The number of currently connected administrative clients.
2861. 3839
2862. 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.
2863. 3841
2864. Displays one heartbeat every 10 seconds.
2865. 3843
2866. The total number of filtering threads in the system. This number is calculated based on your system resources.
2867. 3845
2868. The number of threads waiting for documents.
2869. 3847
2870. The number of document entries currently in memory. Zero means no indexing activity is going on.
2871. 3849
2872. Indicates the level of the amount of system resources that the Gatherer service is allowed to use.
2873. 3851
2874. The number of documents waiting for robot threads. If this number is not 0, all threads should be filtering.
2875. 3853
2876. The number of filtering processes in the system.
2877. 3855
2878. The maximum number of filtering processes that have existed in the system since startup.
2879. 3857
2880. 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.
2881. 3859
2882. The number of documents delayed due to site hit frequency rules.
2883. 3861
2884. The number of servers recently accessed by the system.
2885. 3863
2886. The number of times a new server object had to be created.
2887. 3865
2888. The number of filter objects in the system. Each filter object corresponds to a URL currently being filtered.
2889. 3867
2890. The number of times a filter object was created. This corresponds to the total number of documents filtered in the system since startup.
2891. 3869
2892. The number of documents filtered per second.
2893. 3871
2894. The total number of timeouts detected by the system since startup.
2895. 3873
2896. A server becomes unavailable when a number of requests to that server time out.
2897. 3875
2898. A server becomes unavailable when a number of requests to that server time out.
2899. 3877
2900. 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.
2901. 3879
2902. The number of threads waiting for plug-ins to complete an operation.
2903. 3881
2904. The number of documents successfully filtered.
2905. 3883
2906. The number of successfully filtered documents per second.
2907. 3885
2908. 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.
2909. 3887
2910. Number of available cached word breakers instances
2911. 3889
2912. Number of available cached stemmer instances. Too many may indicate a resource usage problem.
2913. 3891
2914. The total number of notifications received from all notification sources including file system.
2915. 3893
2916. The rate of external notifications received per second.
2917. 3895
2918. System IO (disk) traffic rate in KB/s detected by back off logic
2919. 3897
2920. 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.
2921. 3899
2922. The number of threads blocked due to back off event
2923. 3901
2924. Indexer PlugIn statistics
2925. 3903
2926. The level of the master index.
2927. 3905
2928. Number of Master Merges to Date
2929. 3907
2930. Master Merge Progress
2931. 3909
2932. Shadow Merge Levels
2933. 3911
2934. Shadow Merge Levels Threshold
2935. 3913
2936. Number of Persistent Indexes
2937. 3915
2938. Size of Index
2939. 3917
2940. Number of Unique Keys
2941. 3919
2942. Number of Documents Filtered
2943. 3921
2944. Number of invalidator work items that were created
2945. 3923
2946. Number of invalidator work items that were deleted
2947. 3925
2948. Number of clean WidSets
2949. 3927
2950. Number of dirty WidSets
2951. 3929
2952. Indicator if a master merge is going on.
2953. 3931
2954. Active Connections
2955. 3933
2956. Number of Queries
2957. 3935
2958. Number of Queries Failed
2959. 3937
2960. Number of Queries Succeeded
2961. 3939
2962. The number of L0 Indexes (Wordlists)
2963. 3941
2964. The number of L0 merges (flushes) in progress at any one moment.
2965. 3943
2966. The average value [documents/hour] computed for the speed of L0 merges (flushes) since the catalog has been loaded
2967. 3945
2968. The number of L0 merges (flushes) since the catalog was loaded
2969. 3947
2970. The last value [documents/hour] computed for the speed of L0 merges (flushes).
2971. 3949
2972. The number of L1 Indexes
2973. 3951
2974. The number of L1 merges in progress at any one moment.
2975. 3953
2976. The average value [documents/hour] computed for the speed of L1 merges since the catalog has been loaded
2977. 3955
2978. The number of L1 merges since the catalog was loaded
2979. 3957
2980. The last value [documents/hour] computed for the speed of L1 merges.
2981. 3959
2982. The number of L2 Indexes
2983. 3961
2984. The number of L2 merges in progress at any one moment.
2985. 3963
2986. The average value [documents/hour] computed for the speed of L2 merges since the catalog has been loaded
2987. 3965
2988. The number of L2 merges since the catalog was loaded
2989. 3967
2990. The last value [documents/hour] computed for the speed of L2 merges.
2991. 3969
2992. The number of L3 Indexes
2993. 3971
2994. The number of L3 merges in progress at any one moment.
2995. 3973
2996. The average value [documents/hour] computed for the speed of L3 merges since the catalog has been loaded
2997. 3975
2998. The number of L3 merges since the catalog was loaded
2999. 3977
3000. The last value [documents/hour] computed for the speed of L3 merges.
3001. 3979
3002. The number of L4 Indexes
3003. 3981
3004. The number of L4 merges in progress at any one moment.
3005. 3983
3006. The average value [documents/hour] computed for the speed of L4 merges since the catalog has been loaded
3007. 3985
3008. The number of L4 merges since the catalog was loaded
3009. 3987
3010. The last value [documents/hour] computed for the speed of L4 merges.
3011. 3989
3012. The number of L5 Indexes
3013. 3991
3014. The number of L5 merges in progress at any one moment.
3015. 3993
3016. The average value [documents/hour] computed for the speed of L5 merges since the catalog has been loaded
3017. 3995
3018. The number of L5 merges since the catalog was loaded
3019. 3997
3020. The last value [documents/hour] computed for the speed of L5 merges.
3021. 3999
3022. The number of L6 Indexes
3023. 4001
3024. The number of L6 merges in progress at any one moment.
3025. 4003
3026. The average value [documents/hour] computed for the speed of L6 merges since the catalog has been loaded
3027. 4005
3028. The number of L6 merges since the catalog was loaded
3029. 4007
3030. The last value [documents/hour] computed for the speed of L6 merges.
3031. 4009
3032. The number of L7 Indexes
3033. 4011
3034. The number of L7 merges in progress at any one moment.
3035. 4013
3036. The average value [documents/hour] computed for the speed of L7 merges since the catalog has been loaded
3037. 4015
3038. The number of L7 merges since the catalog was loaded
3039. 4017
3040. The last value [documents/hour] computed for the speed of L7 merges.
3041. 4019
3042. The number of L8 Indexes
3043. 4021
3044. The number of L8 merges in progress at any one moment.
3045. 4023
3046. The average value [documents/hour] computed for the speed of L8 merges since the catalog has been loaded
3047. 4025
3048. The number of L8 merges since the catalog was loaded
3049. 4027
3050. The last value [documents/hour] computed for the speed of L8 merges.
3051. 4029
3052. Performance Counters for the Peer Networking Resolution Protocol
3053. 4031
3054. Number of IDs registered in the Peer Networking Resolution Protocol
3055. 4033
3056. Number of resolves made in the Peer Networking Resolution Protocol
3057. 4035
3058. Average outbound bandwidth utilization of the Peer Networking Resolution Protocol, in terms of bytes sent per second
3059. 4037
3060. Average inbound bandwidth utilization of the Peer Networking Resolution Protocol, in terms of bytes received per second
3061. 4039
3062. Stale cache entry hits in the Peer Networking Resolution Protocol
3063. 4041
3064. ServiceModelOperation 3.0.0.0 performance counters
3065. 4043
3066. The number of calls to this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.Calls.aspx
3067. 4045
3068. The number of calls to this operation per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsPerSecond.aspx
3069. 4047
3070. 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
3071. 4049
3072. The number of calls with unhandled exceptions in this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFailed.aspx
3073. 4051
3074. 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
3075. 4053
3076. The number of calls to this operation that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallsFaulted.aspx
3077. 4055
3078. 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
3079. 4057
3080. The average duration of calls to this operation. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.CallDuration.aspx
3081. 4059
3082. Base counter for the 'Calls Duration' counter.
3083. 4061
3084. 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
3085. 4063
3086. 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
3087. 4065
3088. 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
3089. 4067
3090. 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
3091. 4069
3092. The number of calls to this operation that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Operation.SecurityCallsNotAuthorized.aspx
3093. 4071
3094. 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
3095. 4073
3096. Displays performance statistics about the ReadyBoost Cache
3097. 4075
3098. The number of bytes read from the cache per second.
3099. 4077
3100. The number of bytes read from the volume per second.
3101. 4079
3102. The number of bytes written to the volume per second.
3103. 4081
3104. The number of read bytes serviced from the update buffers per second.
3105. 4083
3106. The total (uncompressed) amount of data currently stored in the cache.
3107. 4085
3108. The number of bytes invalidated in update buffers per second.
3109. 4087
3110. The number of reads from the cache per second.
3111. 4089
3112. (Actual size of data in cache) / (Uncompressed size of data in cache)
3113. 4091
3114. The number of I/Os not serviced by the cache due to sequentiality per second.
3115. 4093
3116. The number of I/Os not serviced by the cache because the size is bigger than the maximum read size per second.
3117. 4095
3118. Writes rescheduled due to the lack of regions per second.
3119. 4097
3120. Writes rescheduled due to the lack of update buffers per second.
3121. 4099
3122. The number of blocks in update buffers invalidated per second.
3123. 4101
3124. ServiceModelService 3.0.0.0 performance counters
3125. 4103
3126. The number of calls to this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.Calls.aspx
3127. 4105
3128. The number of calls to this service per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsPerSecond.aspx
3129. 4107
3130. 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
3131. 4109
3132. The number of calls with unhandled exceptions in this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFailed.aspx
3133. 4111
3134. 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
3135. 4113
3136. The number of calls to this service that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallsFaulted.aspx
3137. 4115
3138. 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
3139. 4117
3140. The average duration of calls to this service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.CallDuration.aspx
3141. 4119
3142. Base counter for the 'Calls Duration' counter.
3143. 4121
3144. 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
3145. 4123
3146. 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
3147. 4125
3148. 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
3149. 4127
3150. 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
3151. 4129
3152. 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
3153. 4131
3154. 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
3155. 4133
3156. 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
3157. 4135
3158. 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
3159. 4137
3160. 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
3161. 4139
3162. 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
3163. 4141
3164. The number of calls to this service that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.SecurityCallsNotAuthorized.aspx
3165. 4143
3166. 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
3167. 4145
3168. The total number of instances of the service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.Instances.aspx
3169. 4147
3170. The creation rate of service instances per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Service.InstancesPerSecond.aspx
3171. 4149
3172. 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
3173. 4151
3174. 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
3175. 4153
3176. 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
3177. 4155
3178. 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
3179. 4157
3180. 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
3181. 4159
3182. 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
3183. 4161
3184. 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
3185. 4163
3186. 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
3187. 4165
3188. 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
3189. 4167
3190. 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
3191. 4169
3192. MSDTC Bridge 3.0.0.0 performance counters
3193. 4171
3194. The number of WS-AT protocol messages that the WS-AT service failed to send per second.
3195. 4173
3196. The number of Prepare retry messages that the WS-AT service has sent per second.
3197. 4175
3198. The number of Commit retry messages that the WS-AT service has sent per second.
3199. 4177
3200. The number of Prepared retry messages that the WS-AT service has sent per second.
3201. 4179
3202. The number of Replay retry messages that the WS-AT service has sent per second.
3203. 4181
3204. The number of Fault messages that the WS-AT service has received per second.
3205. 4183
3206. The number of Fault messages that the WS-AT service has sent per second.
3207. 4185
3208. Average time in milliseconds for the WS-AT service to receive a Prepare message response from a participant.
3209. 4187
3210. Base counter for the 'Average participant prepare response time' counter.
3211. 4189
3212. Average time in milliseconds for the WS-AT service to receive a Commit message response from a participant.
3213. 4191
3214. Base counter for the 'Average participant commit response time' counter.
3215. 4273
3216. SMSvcHost 3.0.0.0 performance counters
3217. 4275
3218. The total number of failures at the protocol layer of net.tcp.
3219. 4277
3220. The total number of failures at the protocol layer of net.pipe.
3221. 4279
3222. The total number of failures dispatching messages received over net.tcp.
3223. 4281
3224. The total number of failures dispatching messages received over net.pipe.
3225. 4283
3226. The total number of connections dispatched over net.tcp.
3227. 4285
3228. The total number of connections dispatched over net.pipe.
3229. 4287
3230. The total number of TCP connections accepted over net.tcp.
3231. 4289
3232. The total number of named pipe connections accepted over net.pipe.
3233. 4291
3234. The number of uri registrations currently active for net.tcp.
3235. 4293
3236. The number of uri registrations currently active for net.pipe.
3237. 4295
3238. The total number of uris that were succesfully registered for net.tcp.
3239. 4297
3240. The total number of uris that were succesfully registered for net.pipe.
3241. 4299
3242. The total number of uris that were succesfully unregistered for net.tcp.
3243. 4301
3244. The total number of uris that were succesfully unregistered for net.pipe.
3245. 4303
3246. ServiceModelEndpoint 3.0.0.0 performance counters
3247. 4305
3248. The number of calls to this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.Calls.aspx
3249. 4307
3250. The number of calls to this endpoint per second. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsPerSecond.aspx
3251. 4309
3252. 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
3253. 4311
3254. The number of calls with unhandled exceptions at this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFailed.aspx
3255. 4313
3256. 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
3257. 4315
3258. The number of calls to this endpoint that returned faults. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallsFaulted.aspx
3259. 4317
3260. 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
3261. 4319
3262. The average duration of calls to this endpoint. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.CallDuration.aspx
3263. 4321
3264. Base counter for the 'Calls Duration' counter.
3265. 4323
3266. 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
3267. 4325
3268. 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
3269. 4327
3270. 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
3271. 4329
3272. 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
3273. 4331
3274. The number of calls to this endpoint that failed authorization. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.PerformanceCounters.Endpoint.SecurityCallsNotAuthorized.aspx
3275. 4333
3276. 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
3277. 4335
3278. 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
3279. 4337
3280. 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
3281. 4339
3282. 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
3283. 4341
3284. 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
3285. 4343
3286. Windows Workflow Foundation Performance Counters
3287. 4345
3288. Total number of workflows created.
3289. 4347
3290. Rate of workflows created per second.
3291. 4349
3292. Total number of workflows unloaded.
3293. 4351
3294. Rate of workflows unloaded per second.
3295. 4353
3296. Total number of workflows loaded.
3297. 4355
3298. Rate of workflows loaded per second.
3299. 4357
3300. Total number of workflows completed.
3301. 4359
3302. Rate of workflows completed per second.
3303. 4361
3304. Total number of workflows suspended.
3305. 4363
3306. Rate of workflows suspended per second.
3307. 4365
3308. Total number of workflows terminated.
3309. 4367
3310. Rate of workflows terminated per second.
3311. 4369
3312. Total number of workflows in memory.
3313. 4371
3314. Total number of workflows aborted.
3315. 4373
3316. Rate of workflows aborted per second.
3317. 4375
3318. Total number of workflows persisted.
3319. 4377
3320. Rate of workflows persisted per second.
3321. 4379
3322. Total number of workflow instances actively executing.
3323. 4381
3324. Rate of workflows becoming idle per second.
3325. 4383
3326. Total number of workflows ready to execute.
3327. 4385
3328. Total number of workflows waiting for a thread.
3329. 4387
3330. Flow statistics from the packet scheduler
3331. 4389
3332. Pipe statistics from the packet scheduler
3333. 4391
3334. The number of packets dropped by the packet scheduler
3335. 4393
3336. The number of packets which got scheduled in some way (rather than just being directly sent to the underlying miniport)
3337. 4395
3338. The number of packets from this flow which have been sent
3339. 4397
3340. The average number of packets in the shaper over the last sampling period
3341. 4399
3342. The maximum number of packets that have ever simultaneously been in the shaper
3343. 4401
3344. The average number of packets in the sequencer over the last sampling period
3345. 4403
3346. The maximum number of packets that have ever simultaneously been in the sequencer
3347. 4405
3348. The number of bytes which got scheduled in some way (rather than just being directly sent to the underlying miniport)
3349. 4407
3350. The number of bytes from this flow which have been sent
3351. 4409
3352. The number of bytes per second from this flow which have been sent
3353. 4411
3354. The number of bytes per second from this flow which have been scheduled
3355. 4413
3356. The number of packets per second from this flow which have been sent
3357. 4415
3358. The number of packets per second from this flow which have been scheduled
3359. 4417
3360. The number of packets dropped by the packet scheduler from this flow per second
3361. 4419
3362. The number of packets that have entered the packet scheduler at a rate which exceeded the flow parameters
3363. 4421
3364. The rate at which nonconforming packets have entered the packet scheduler
3365. 4423
3366. The number of packets that have been sent by the packet scheduler at a rate which exceeded the flow parameters
3367. 4425
3368. The rate at which nonconforming packets have been sent by the packet scheduler
3369. 4427
3370. The maximum number of packets that have been queued in the netcard by this flow.
3371. 4429
3372. The average number of packets that have been queued in the netcard by this flow.
3373. 4431
3374. The number of times Pacer has been unable to allocate a packet
3375. 4433
3376. The number of flows opened on this pipe (some of which may now be closed)
3377. 4435
3378. The number of flows that have been closed
3379. 4437
3380. The number of flow creations that were rejected
3381. 4439
3382. The of times a flow has been modified
3383. 4441
3384. The number of times a flow modification has been rejected
3385. 4443
3386. The maximum number of flows that have been simultaneously open on this pipe
3387. 4445
3388. The number of packets that have entered the packet scheduler at a rate which exceeded that packet's flow parameters
3389. 4447
3390. The rate at which nonconforming packets have entered the packet scheduler
3391. 4449
3392. The number of packets that have been sent by the packet scheduler at a rate which exceeded that packet's flow parameters
3393. 4451
3394. The rate at which nonconforming packets have been sent by the packet scheduler
3395. 4453
3396. The average number of packets in the shaper over the last sampling period
3397. 4455
3398. The maximum number of packets that have ever simultaneously been in the shaper
3399. 4457
3400. The average number of packets in the sequencer over the last sampling period
3401. 4459
3402. The maximum number of packets that have ever simultaneously been in the sequencer
3403. 4461
3404. The maximum number of packets ever simultaneously in the network card
3405. 4463
3406. The average number of packets in the network card over the last sampling period
3407. 4713
3408. Terminal Services per-session resource monitoring.
3409. 4715
3410. Number of bytes input on this session after all protocol overhead has been removed.
3411. 4717
3412. The number of frames input after any additional protocol added frames have been removed.
3413. 4719
3414. The number of times that a wait for an available send buffer was done by the protocols on the client side of the connection.
3415. 4721
3416. Number of frames (packets) input on this Session.
3417. 4723
3418. Number of bytes input on this session that includes all protocol overhead.
3419. 4725
3420. Number of bytes input after compression. This number compared with the Total Bytes input is the compression ratio.
3421. 4727
3422. 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.
3423. 4729
3424. Number of input errors of all types. Some example input errors are lost ACK's, badly formed packets, etc.
3425. 4731
3426. 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.
3427. 4733
3428. 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.
3429. 4735
3430. 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.
3431. 4737
3432. Number of input async overflow errors. These can be caused by a lack of buffer space available on the host.
3433. 4739
3434. Number of input async parity errors. These can be caused by a noisy transmission line
3435. 4741
3436. Number of Terminal Services transport-level errors on input.
3437. 4743
3438. Number of bytes output on this session after all protocol overhead has been removed.
3439. 4745
3440. The number of frames output before any additional protocol frames have been added.
3441. 4747
3442. 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.
3443. 4749
3444. Number of frames (packets) output on this session.
3445. 4751
3446. Number of bytes output on this Session that includes all protocol overhead.
3447. 4753
3448. Number of bytes output after compression. This number compared with the Total Bytes output is the compression ratio.
3449. 4755
3450. 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.
3451. 4757
3452. Number of output errors of all types. Some example output errors are lost ACK's, badly formed packets, etc.
3453. 4759
3454. 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.
3455. 4761
3456. Number of output async framing errors. This could be caused by a hardware or line problem.
3457. 4763
3458. Number of output async overrun errors.
3459. 4765
3460. Number of output async overflow errors.
3461. 4767
3462. Number of output async parity errors. These can be caused by a hardware or line problem.
3463. 4769
3464. Number of Terminal Services transport-level errors on output.
3465. 4771
3466. Total number of bytes on this Session after all protocol overhead has been removed.
3467. 4773
3468. The total number of frames input and output before any additional protocol frames have been added.
3469. 4775
3470. 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.
3471. 4777
3472. Total number of frames (packets) on this Session.
3473. 4779
3474. Total number of bytes on this Session that includes all protocol overhead.
3475. 4781
3476. Total number of bytes after compression. This number compared with the total bytes is the compression ratio.
3477. 4783
3478. 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.
3479. 4785
3480. Total number of errors of all types. Some example errors are lost ACK's, badly formed packets, etc.
3481. 4787
3482. 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.
3483. 4789
3484. 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.
3485. 4791
3486. 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.
3487. 4793
3488. Total number of async overflow errors. These can be caused by a lack of buffer space available on the host.
3489. 4795
3490. Total number of async parity errors. These can be caused by a noisy transmission line.
3491. 4797
3492. Total number of Terminal Services transport-level errors.
3493. 4799
3494. Total references to all protocol caches.
3495. 4801
3496. 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.
3497. 4803
3498. Overall hit ratio for all protocol caches.
3499. 4805
3500. Number of references to the protocol bitmap cache.
3501. 4807
3502. Number of hits in the protocol bitmap cache.
3503. 4809
3504. 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.
3505. 4811
3506. Number of references to the protocol glyph cache.
3507. 4813
3508. Number of hits in the protocol glyph cache.
3509. 4815
3510. 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.
3511. 4817
3512. Number of references to the protocol brush cache.
3513. 4819
3514. Number of hits in the protocol brush cache.
3515. 4821
3516. 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.
3517. 4823
3518. Number of references to the protocol save screen bitmap cache.
3519. 4825
3520. Number of hits in the protocol save screen bitmap cache.
3521. 4827
3522. 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.
3523. 4829
3524. Compression ratio of the server input data stream.
3525. 4831
3526. Compression ratio of the server output data stream.
3527. 4833
3528. Total compression ratio of the server data stream.
3529. 5111
3530. Statistics related to SQL Servers buffer manager
3531. 5113
3532. Percentage of pages that were found in the buffer pool without having to incur a read from disk.
3533. 5115
3534. Number of AWE unmap calls.
3535. 5117
3536. Number of requests that had to wait for a free page.
3537. 5119
3538. Number of physical database page writes issued.
3539. 5121
3540. Number of pages in the buffer pool with database content.
3541. 5123
3542. Number of seconds a page will stay in the buffer pool without references.
3543. 5125
3544. Number of AWE map calls made for pages stolen from the buffer pool.
3545. 5127
3546. Number of AWE map calls made for pages found in the buffer pool.
3547. 5129
3548. Number of pages used for miscellaneous server purposes (including procedure cache).
3549. 5131
3550. Base for prior entry
3551. 5133
3552. Total number of pages on all free lists.
3553. 5135
3554. Number of pages flushed by checkpoint or other operations that require all dirty pages to be flushed.
3555. 5137
3556. Number of pages in the buffer pool (includes database, free, and stolen).
3557. 5139
3558. Number of buffers written by buffer manager's lazy writer.
3559. 5141
3560. Number of physical database page reads issued.
3561. 5143
3562. Number of buffer pool reserved pages.
3563. 5145
3564. Number of pages read in anticipation of use.
3565. 5147
3566. Ideal number of pages in the buffer pool.
3567. 5149
3568. Number of requests to find a page in the buffer pool.
3569. 5151
3570. Number of AWE pages unmapped.
3571. 5153
3572. Number of AWE map calls made for pages to be written to disk.
3573. 5155
3574. Statistics related to SQL Server's buffer partitions
3575. 5157
3576. Number of times a free page was requested and none were available.
3577. 5159
3578. Number of times a free page was requested.
3579. 5161
3580. Number of pages on partition free list.
3581. 5163
3582. Statistics related to SQL Server's buffer pool by NUMA node
3583. 5165
3584. Number of seconds a page will stay in the buffer pool without references.
3585. 5167
3586. Target pages on node.
3587. 5169
3588. Stolen pages on node.
3589. 5171
3590. Committed pages on node.
3591. 5173
3592. Database pages on node.
3593. 5175
3594. Free pages on node.
3595. 5177
3596. Number of pages which are not from NUMA-local memory.
3597. 5179
3598. Server General Statistics
3599. 5181
3600. Number of Mars Deadlocks detected.
3601. 5183
3602. Number of SOAP Session initiate requests started per second.
3603. 5185
3604. Number of trace event notification instances waiting in the internal queue to be sent thru Service Broker
3605. 5187
3606. Number of SOAP Session terminate requests started per second.
3607. 5189
3608. Number of users connected to the system.
3609. 5191
3610. Number of currently blocked processes.
3611. 5193
3612. Number of authenticated HTTP requests started per second.
3613. 5195
3614. Number of temporary tables/table variables created/sec
3615. 5197
3616. Number of transaction enlistments (local, dtc, and bound).
3617. 5199
3618. Number of temporary tables/table variables in use
3619. 5201
3620. Number of temporary tables/table variables waiting to be destroyed by the cleanup system thread
3621. 5203
3622. Number of logical connections to the system.
3623. 5205
3624. Number of waits for the File IO Provider lock per second
3625. 5207
3626. Number of non-atomic yields per second.
3627. 5209
3628. Number of empty SOAP requests started per second.
3629. 5211
3630. Total number of logins started per second.
3631. 5213
3632. Number of SOAP Web Service Description Language requests started per second.
3633. 5215
3634. Number of SOAP SQL requests started per second.
3635. 5217
3636. Number of SOAP method invocations started per second.
3637. 5219
3638. Total number of logouts started per second.
3639. 5221
3640. Number of event notifications waiting to be dropped by a system thread
3641. 5223
3642. Describes statistics for individual lock server lock requests
3643. 5225
3644. Number of new locks and lock conversions requested from the lock manager.
3645. 5227
3646. Number of lock requests that timed out. This includes requests for NOWAIT locks.
3647. 5229
3648. Number of lock requests that timed out. This does not include requests for NOWAIT locks.
3649. 5231
3650. Total wait time (milliseconds) for locks in the last second.
3651. 5233
3652. Number of lock requests that resulted in a deadlock.
3653. 5235
3654. Base for Averate Wait Time.
3655. 5237
3656. Number of lock requests that could not be satisfied immediately and required the caller to wait before being granted the lock.
3657. 5239
3658. The average amount of wait time (milliseconds) for each lock request that resulted in a wait.
3659. 5241
3660. This defines a Database manager object for SQL Server
3661. 5243
3662. Number of active update transactions for the database.
3663. 5245
3664. Total wait time (milliseconds).
3665. 5247
3666. Percentage of log cache reads that were satisfied from the log cache.
3667. 5249
3668. Number of commits waiting on log flush.
3669. 5251
3670. The cumulative used size of all the log files in the database.
3671. 5253
3672. Reads performed through the log manager cache.
3673. 5255
3674. The rate data is being moved by Autoshrink, DBCC SHRINKDATABASE or SHRINKFILE.
3675. 5257
3676. Total number of log bytes flushed.
3677. 5259
3678. The percent of space in the log that is in use.
3679. 5261
3680. Number of rows bulk copied.
3681. 5263
3682. Number of log flushes.
3683. 5265
3684. Total number of log growths for this database.
3685. 5267
3686. Total number of log truncations for this database.
3687. 5269
3688. Logical read scan rate for DBCC commands
3689. 5271
3690. The cumulative size of all the log files in the database.
3691. 5273
3692. KiloBytes bulk copied.
3693. 5275
3694. Number of transactions started for the database.
3695. 5277
3696. The cumulative size of all the data files in the database.
3697. 5279
3698. Replication transaction rate (replicated transactions/sec.).
3699. 5281
3700. Total number of log shrinks for this database.
3701. 5283
3702. Number of pending replication transactions in the database.
3703. 5285
3704. Read/write throughput for backup/restore of a database.
3705. 5287
3706. Base for log cache calculations
3707. 5289
3708. This defines a Database Mirroring object for SQL Server
3709. 5291
3710. Number of bytes received per second
3711. 5293
3712. Number of sends initiated per second
3713. 5295
3714. Milliseconds packets waited in flow control per second.
3715. 5297
3716. Total number of kilobytes that redo on the mirror database is behind the hardened log
3717. 5299
3718. Average delay in transaction termination waiting for acknowledgement
3719. 5301
3720. Number of bytes of log received per second
3721. 5303
3722. Total number of kilobytes of log that have not been sent to the mirror server
3723. 5305
3724. Number of bytes sent per second
3725. 5307
3726. Number of bytes of log sent per second
3727. 5309
3728. Number of mirroring message receives per second
3729. 5311
3730. Number of pages sent per second
3731. 5313
3732. Number of bytes of log redone by the mirror database per second
3733. 5315
3734. Collects statistics associated with internal server latches
3735. 5317
3736. Number of latch requests that could not be granted immediately and had to wait before being granted.
3737. 5319
3738. Number of SuperLatches that have been demoted to regular latches
3739. 5321
3740. Total latch wait time (milliseconds) for latch requests that had to wait in the last second.
3741. 5323
3742. Base for Average Latch Wait Time.
3743. 5325
3744. Number of latches that have been promoted to SuperLatches
3745. 5327
3746. Number of latches that are currently SuperLatches.
3747. 5329
3748. Average latch wait time (milliseconds) for latch requests that had to wait.
3749. 5331
3750. Collects statistics associated with the database server access methods
3751. 5333
3752. The number of times that a leaf page cookie could not be used during an index search since changes happened on the leaf page. The cookie is used to speed up index search.
3753. 5335
3754. Number of ghosted records per second skipped during scans.
3755. 5337
3756. Number of times the scan point had to be revalidated to continue the scan.
3757. 5339
3758. The number of rowsets per second created as a result of aborted online index build operations that were successfully dropped by the background task that cleans up deferred dropped rowsets.
3759. 5341
3760. Count of temporary LOBs created.
3761. 5343
3762. Count of large object (LOB) values that were passed by reference. By-reference lobs are used in certain bulk operations to avoid the cost of passing them by value.
3763. 5345
3764. Number of probe scans per second that are used to find at most one single qualified row in an index or base table directly.
3765. 5347
3766. Count of lob pages on which readahead was issued.
3767. 5349
3768. Number of times a tree page cookie was used successfully during an index search since no change happened on the parent page of the tree page. The cookie is used to speed up index search.
3769. 5351
3770. Percent of worktables from cache base.
3771. 5353
3772. Number of extents allocated per second in all databases in this SQL Server instance.
3773. 5355
3774. Count of values that were pushed from in-row to off-row.
3775. 5357
3776. The number of batches that completed successfully per second by the background task that cleans up deferred dropped allocation units.
3777. 5359
3778. Percentage of work tables created where the initial two pages of the work table were not allocated but were immediately available from the work table cache.
3779. 5361
3780. Number of qualified range scans through indexes per second.
3781. 5363
3782. Count of values that were pulled in-row from off-row.
3783. 5365
3784. The number of batches per second that failed and required retry, by the background task that cleans up deferred dropped allocation units. Failure could be due to lack of memory or disk space, hardware failure and other reasons.
3785. 5367
3786. Number of scans per second that were initiated to search for free space within pages already allocated to an allocation unit to insert or modify record fragments. Each scan may find multiple pages.
3787. 5369
3788. The number of times that a tree page cookie could not be used during an index search since changes happened on the parent pages of those tree pages. The cookie is used to speed up index search.
3789. 5371
3790. Number of pages deallocated per second in all databases in this SQL Server instance. These include pages from mixed extents and uniform extents.
3791. 5373
3792. Number of unrestricted full scans. These can either be base table or full index scans.
3793. 5375
3794. The number of times locks on a table were escalated.
3795. 5377
3796. Number of records fetched through forwarded record pointers.
3797. 5379
3798. Count of by-reference lob values that were used. By-reference lobs are used in certain bulk operations to avoid the cost of passing them by value.
3799. 5381
3800. The number of rowsets created as a result of aborted online index build operations that are waiting to be dropped by the background task that cleans up deferred dropped rowsets.
3801. 5383
3802. Number of page splits per second that occur as a result of overflowing index pages.
3803. 5385
3804. Count of LOB Storage Service Providers truncated.
3805. 5387
3806. The number of rowsets per second created as a result of aborted online index build operations that were skipped by the background task that cleans up deferred dropped rowsets created.
3807. 5389
3808. Number of times a leaf page cookie was used successfully during an index search since no change happened on the leaf page. The cookie is used to speed up index search.
3809. 5391
3810. Number of pages fetched per second by free space scans. These scans search for free space within pages already allocated to an allocation unit, to satisfy requests to insert or modify record fragments.
3811. 5393
3812. The number of allocation units waiting to be dropped by the background task that cleans up deferred dropped allocation units.
3813. 5395
3814. Number of pages allocated per second in all databases in this SQL Server instance. These include pages allocations from both mixed extents and uniform extents.
3815. 5397
3816. Count of LOB Storage Service Providers created. One worktable created per LOB Storage Service Provider.
3817. 5399
3818. Number of work files created per second. For example, work files could be used to store temporary results for hash joins and hash aggregates.
3819. 5401
3820. Number of extents deallocated per second in all databases in this SQL Server instance.
3821. 5403
3822. Count of temporary LOBs destroyed.
3823. 5405
3824. Number of index searches. Index searches are used to start range scans, single index record fetches, and to reposition within an index.
3825. 5407
3826. The number of allocation units per second that were successfully dropped by the background task that cleans up deferred dropped allocation units. Each allocation unit drop requires multiple batches.
3827. 5409
3828. Number of pages allocated per second from mixed extents. These could be used for storing the IAM pages and the first eight pages that are allocated to an allocation unit.
3829. 5411
3830. Number of work tables created per second. For example, work tables could be used to store temporary results for query spool, LOB variables, XML variables, and cursors.
3831. 5413
3832. Count of LOB Storage Service Providers destroyed.
3833. 5415
3834. Statistics about errors in SQL Server
3835. 5417
3836. Number of errors/sec
3837. 5419
3838. Collects statistics associated with SQL requests
3839. 5421
3840. Number of failed auto-parameterizations.
3841. 5423
3842. Number of SQL batch requests received by server.
3843. 5425
3844. Number of unsafe auto-parameterizations.
3845. 5427
3846. Number of attentions per second.
3847. 5429
3848. Number of SQL re-compiles.
3849. 5431
3850. Number of statements parameterized by forced parameterization per second.
3851. 5433
3852. Number of SQL compilations.
3853. 5435
3854. Number of safe auto-parameterizations.
3855. 5437
3856. Number of auto-parameterization attempts.
3857. 5439
3858. This defines cache counters
3859. 5441
3860. Number of cache objects in the cache
3861. 5443
3862. Base for prior entry
3863. 5445
3864. Number of 8k pages used by cache objects
3865. 5447
3866. Ratio between cache hits and lookups
3867. 5449
3868. Number of cache objects in use
3869. 5451
3870. Counters for cursor properties grouped by type
3871. 5453
3872. Amount of memory consumed by cursors (KB).
3873. 5455
3874. Ratio between cache hits and lookups
3875. 5457
3876. Times each type of cached cursor has been used
3877. 5459
3878. Number of cursor plans.
3879. 5461
3880. Number of cursors of a given type in the cache
3881. 5463
3882. Number of SQL cursor requests received by server.
3883. 5465
3884. Base for prior entry
3885. 5467
3886. Number of worktables used by cursors.
3887. 5469
3888. Number of active cursors.
3889. 5471
3890. Counters for cursor properties not grouped by type
3891. 5473
3892. Number of cursor conversions/sec.
3893. 5475
3894. Total number of times a flush for a cursor xstmt occured.
3895. 5477
3896. Number of cursors being populated asynchronously.
3897. 5479
3898. This defines memory usage.
3899. 5481
3900. Total amount of dynamic memory the server is currently consuming
3901. 5483
3902. Total amount of dynamic memory the server is using for the dynamic SQL cache
3903. 5485
3904. Total amount of memory granted to executing processes. This memory is used primarily for hash, sort and create index operations.
3905. 5487
3906. The current number of lock blocks that are in use on the server. Refreshed periodically.
3907. 5489
3908. Current number of processes waiting for a workspace memory grant
3909. 5491
3910. The number of lock owner blocks that are currently in use on the server. Refreshed periodically.
3911. 5493
3912. Total amount of dynamic memory the server is using for locks
3913. 5495
3914. Total amount of dynamic memory the server is willing to consume
3915. 5497
3916. Total amount of dynamic memory the server is using for maintaining connections
3917. 5499
3918. The current number of allocated lock blocks.
3919. 5501
3920. Total amount of dynamic memory the server is using for query optimization
3921. 5503
3922. The current number of allocated lock owner blocks.
3923. 5505
3924. Current number of processes that have successfully acquired a workspace memory grant
3925. 5507
3926. Total amount of memory granted to executing processes. This memory is used for hash, sort and create index operations.
3927. 5509
3928. This defines user definable counters
3929. 5511
3930. As defined by the user.
3931. 5513
3932. Replication Summary
3933. 5515
3934. The number of replication agents currently running.
3935. 5517
3936. Replication Merge Agent Statistics
3937. 5519
3938. The number of rows per second merged from the Subscriber to the Publisher.
3939. 5521
3940. The number of conflicts per second occurring during the merge process.
3941. 5523
3942. The number of rows per second merged from the Publisher to the Subscriber.
3943. 5525
3944. Replication Logreader Agent Statistics
3945. 5527
3946. The number of commands per second delivered to the Distributor.
3947. 5529
3948. The current amount of time, in milliseconds, elapsed from when transactions are applied at the Publisher to when they are delivered to the Distributor.
3949. 5531
3950. The number of transactions per second delivered to the Distributor.
3951. 5533
3952. Replication Distribution Agent Statistics
3953. 5535
3954. The number of transactions per second delivered to the Subscriber.
3955. 5537
3956. The number of commands per second delivered to the Subscriber.
3957. 5539
3958. The current amount of time, in milliseconds, elapsed from when transactions are delivered to the Distributor to when they are applied at the Subscriber.
3959. 5541
3960. Replication Snapshot Agent Statistics
3961. 5543
3962. The number of transactions per second delivered to the Distributor.
3963. 5545
3964. The number of commands per second delivered to the Distributor.
3965. 5547
3966. This defines a backup device object for SQL Server
3967. 5549
3968. Read/write throughput for a backup device.
3969. 5551
3970. Statistics related to SQL Server transactions.
3971. 5553
3972. The size of the version store in KB.
3973. 5555
3974. The longest running time of any transcation in seconds.
3975. 5557
3976. The total number of active transactions.
3977. 5559
3978. Truncation of unit in Version Store.
3979. 5561
3980. The total number of active non-snapshot transactions that generate version records.
3981. 5563
3982. The total number of active snapshot transactions.
3983. 5565
3984. The total number of active snapshot transactions that do updates.
3985. 5567
3986. Number of unit in Version Store.
3987. 5569
3988. Creation of new unit in Version Store.
3989. 5571
3990. The version generation rate in KB per seconds.
3991. 5573
3992. The version cleanup rate in KB per seconds.
3993. 5575
3994. The free space in tempdb in KB.
3995. 5577
3996. The fraction of update snapshot transactions that have update conflicts to the total number of update snapshot transactions.
3997. 5579
3998. The total number of update snapshot transactions.
3999. 5581
4000. Service Broker Statistics
4001. 5583
4002. The number of forwarded message bytes successfully sent per second.
4003. 5585
4004. The number of forwarded messages that have not been successfully sent yet.
4005. 5587
4006. The number of message fragments from the transport that are successfully delivered into queues per second. Note the cooresponding message may not be complete yet or may be out of order, and therefore the message can be in the queue as disabled.
4007. 5589
4008. Total number of SQL RECEIVE commands processed by the Broker.
4009. 5591
4010. The number of messages from the transport that are successfully delivered as ready into queues per second.
4011. 5593
4012. Total number of SQL SEND commands processed by the Broker.
4013. 5595
4014. The number of SQL RECEIVE commands processed by the Broker per second.
4015. 5597
4016. Total number of message fragments from the transport that are successfully delivered into queues. Note the cooresponding message may not be complete yet or may be out of order, and therefore the message can be in the queue as disabled.
4017. 5599
4018. Total number of message fragments from local endpoints and the transport that are successfully delivered as ready into queues.
4019. 5601
4020. Total number of message fragments from local endpoints that are successfully delivered as ready into queues.
4021. 5603
4022. The number of Service Broker related transactions that have rolled back.
4023. 5605
4024. Total number of forwarded messages successfully sent.
4025. 5607
4026. The number of forwarded message bytes that have not been successfully sent yet.
4027. 5609
4028. The number of forwarded messages successfully sent per second.
4029. 5611
4030. The number of messages from local endpoints that are successfully delivered as ready into queues per second.
4031. 5613
4032. The number of messages from local endpoints and the transport that are successfully delivered as ready into queues per second.
4033. 5615
4034. The number of SQL SEND commands processed by the Broker per second.
4035. 5617
4036. Total number of forwarded messages discarded due to forwarded message memory limits, age limits, etc.
4037. 5619
4038. The number of dialog endpoint related timer events in the Broker.
4039. 5621
4040. The number of forwarded messages that were discarded per second due to forwarded message memory limits, age limits, etc.
4041. 5623
4042. Total number of forwarded message bytes successfully sent.
4043. 5625
4044. Total number of messages from the transport that are successfully delivered as ready into queues.
4045. 5627
4046. Service Broker/Database Mirroring Transport Statistics
4047. 5629
4048. The number of bytes associated with in completed transport receive I/O operations whose message fragments haven't been enqueued (or rejected) yet.
4049. 5631
4050. The average byte size of message fragments received in transport receive I/O operations.
4051. 5633
4052. The current number of message fragments associated with current transport send I/O operations that haven't completed.
4053. 5635
4054. Base for the average byte size of message fragments received in transport receive I/O operations.
4055. 5637
4056. The number of message fragments received per second in transport receive I/O operations.
4057. 5639
4058. The number of message fragments sent per second in transport send I/O operations.
4059. 5641
4060. The number of transport send I/Os per second. Note that a transport send I/O may contain more than one message fragment.
4061. 5643
4062. The number of transport receive I/O bytes per second.
4063. 5645
4064. The number of buffer bytes associated with current transport send I/O operations that haven't completed.
4065. 5647
4066. The average byte length of transport send I/O operations.
4067. 5649
4068. The average byte size of message fragments sent in transport send I/O operations.
4069. 5651
4070. The total number of transport connections currently open.
4071. 5653
4072. The current number of message fragments received in transport receive I/O operations that have not been enqueued (or rejected) yet.
4073. 5655
4074. The number of transport send I/O bytes per second.
4075. 5657
4076. The number of transport receives I/O per second. Note that a transport receive I/O may contain more than one message fragment.
4077. 5659
4078. The number of times when transport receive I/O operations had to move buffer fragments in memory.
4079. 5661
4080. The number of buffer bytes associated with message fragments being marshalled, or marshalled and ready to be sent with send I/O operations.
4081. 5663
4082. The average byte length of transport receive I/O operations.
4083. 5665
4084. The rate at witch transport receive I/O operations had to move buffer fragments in memory.
4085. 5667
4086. Base for the average byte length of transport send I/O operations.
4087. 5669
4088. The current number of message fragments that are being marshalled, or marshalled and ready to be sent via the transport layer.
4089. 5671
4090. Base for the average byte size of message fragments sent in transport send I/O operations.
4091. 5673
4092. Base for the average byte length of transport receive I/O operations.
4093. 5675
4094. The number of bytes associated with current transport receive I/O operations that haven't completed.
4095. 5677
4096. Service Broker Activation
4097. 5679
4098. The number of times the activated task limit on a queue has been reached per second.
4099. 5681
4100. The total number of times the activated task limit on a queue has been reached.
4101. 5683
4102. The total number of activated tasks that are currently running.
4103. 5685
4104. The number of stored procedures that are being invoked per second.
4105. 5687
4106. The number of activated tasks that are being aborted per second.
4107. 5689
4108. The number of activated tasks that are being started per second.
4109. 5691
4110. Wait Statistics
4111. 5693
4112. Statistics relevant to processes synchronizing access to workspace.
4113. 5695
4114. Statistics relevant to non-page latches.
4115. 5697
4116. Statistics relevant to page latches, not including IO latches
4117. 5699
4118. Statistics for processes waiting on thread-safe memory allocators.
4119. 5701
4120. Statistics relevant to page IO latches.
4121. 5703
4122. Statistics relevant to processes waiting for worker to become available.
4123. 5705
4124. Statistics for processes waiting for log buffer to be written.
4125. 5707
4126. Statistics relevant to processes synchronizing access to transaction.
4127. 5709
4128. Statistics for processes waiting on a lock.
4129. 5711
4130. Statistics relevant to wait on network IO.
4131. 5713
4132. Statistics for processes waiting for memory grant to become available.
4133. 5715
4134. Statistics for processes waiting for log buffer to be available.
4135. 5717
4136. Execution statistics for external calls
4137. 5719
4138. Statistics relevant to execution of OLEDB calls.
4139. 5721
4140. Statistics relevant to execution of distributed queries.
4141. 5723
4142. Statistics relevant to execution of DTC calls.
4143. 5725
4144. Statistics relevant to execution of XP calls.
4145. 5727
4146. CLR Execution in SQL Server
4147. 5729
4148. Total Execution time in CLR ( microseconds ).
4149. 5731
4150. This defines a catalog metadata manager object for SQL Server
4151. 5733
4152. Number of entries in the catalog metadata cache
4153. 5735
4154. Ratio between catalog metadata cache hits and lookups
4155. 5737
4156. Base for prior entry
4157. 5739
4158. Number of catalog metadata cache entries that are pinned
4159. 6353
4160. Counters for classes in the System.Net namespace.
4161. 6355
4162. The cumulative total number of socket connections established for this process since the process was started.
4163. 6357
4164. 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.
4165. 6359
4166. 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.
4167. 6361
4168. The cumulative total number of datagram packets received since the process was started.
4169. 6363
4170. The cumulative total number of datagram packets sent since the process was started.
4171. 6365
4172. The number of HttpWebRequest objects created during the last sample interval (typically 1 sec).
4173. 6367
4174. 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.
4175. 6369
4176. HttpWebRequests Average Lifetime Base
4177. 6371
4178. 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.
4179. 6373
4180. 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.
4181. 6375
4182. HttpWebRequests Average Queue Time Base
4183. 6377
4184. 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.
4185. 6379
4186. 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()
4187. 8185
4188. System.Runtime.Caching.MemoryCache Performance Counters
4189. 8187
4190. The number of cache hits.
4191. 8189
4192. The number of cache misses.
4193. 8191
4194. The percentage of cache hits in the total number of cache requests.
4195. 8193
4196. Cache Hit Ratio Base
4197. 8195
4198. Total number of entries removed from the cache due to memory pressure or Trim invocations.
4199. 8197
4200. The number of entries within the cache.
4201. 8199
4202. The number of entries added to the cache or removed from the cache per second.
4203. 8435
4204. ASP.NET global performance counters
4205. 8437
4206. ASP.NET application performance counters
4207. 8439
4208. Number of times the application has been restarted during the web server's lifetime.
4209. 8441
4210. Number of currently running web applications.
4211. 8443
4212. The number of requests disconnected due to communication errors or user terminated.
4213. 8445
4214. The number of milliseconds that it took to execute the most recent request.
4215. 8447
4216. The number of requests rejected because the request queue was full.
4217. 8449
4218. The number of requests waiting to be processed.
4219. 8451
4220. Number of worker processes running on the machine.
4221. 8453
4222. Number of times a worker process has restarted on the machine.
4223. 8455
4224. The number of milliseconds the most recent request was waiting in the queue.
4225. 8457
4226. The current number of sessions currently active.
4227. 8459
4228. The number of sessions that have been explicitly abandoned.
4229. 8461
4230. The number of sessions timed out.
4231. 8463
4232. The number of sessions total.
4233. 8465
4234. 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.
4235. 8467
4236. Number of audit successes in the application since it was started.
4237. 8469
4238. Number of audit failures in the application since it was started.
4239. 8471
4240. Number of error events raised since the application was started.
4241. 8473
4242. Number of runtime error events raised since the application was started.
4243. 8475
4244. Number of HTTP error events raised since the application was started.
4245. 8477
4246. Requests queued because the concurrency limits have been exceeded.
4247. 8479
4248. Number of requests utilizing anonymous authentication.
4249. 8481
4250. Number of Authentication Anonymous Requests/Sec
4251. 8483
4252. Total number of entries within the cache (both internal and user added)
4253. 8485
4254. Number of additions and removals to the total cache per second.
4255. 8487
4256. Total number of hits from the cache.
4257. 8489
4258. Total number of cache misses.
4259. 8491
4260. Ratio of hits from all cache calls.
4261. 8493
4262. Cache Total Hit Ratio Base
4263. 8495
4264. Total number of entries within the cache added by the user.
4265. 8497
4266. Number of additions and removals to the API cache per second.
4267. 8499
4268. Number of cache hits from user code.
4269. 8501
4270. Number of cache misses called from user code.
4271. 8503
4272. Ratio of hits called from user code.
4273. 8505
4274. Cache API Hit Ratio Base
4275. 8507
4276. Current number of entries in the output cache.
4277. 8509
4278. Number of additions and removals to the output cache per second.
4279. 8511
4280. Total number of output cacheable requests served from the output cache.
4281. 8513
4282. Total number of output cacheable requests not served from the output cache.
4283. 8515
4284. Ratio of hits to requests for output cacheable requests.
4285. 8517
4286. Output Cache Hit Ratio Base
4287. 8519
4288. Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled.
4289. 8521
4290. Number of debugging requests processed.
4291. 8523
4292. Number of errors that have occurred during parsing and configuration.
4293. 8525
4294. Number of errors that have occurred during compilation.
4295. 8527
4296. Number of errors that have occurred during the processing of a request.
4297. 8529
4298. Number of errors not handled by user code, but by the default error handler.
4299. 8531
4300. Rate of unhandled errors.
4301. 8533
4302. Total number of errors occurred.
4303. 8535
4304. Rate of errors occurred.
4305. 8537
4306. Number of active pipeline instances.
4307. 8539
4308. The total size, in bytes, of all requests.
4309. 8541
4310. The total size, in bytes, of responses sent to a client. This does not include standard HTTP response headers.
4311. 8543
4312. The number of requests currently executing.
4313. 8545
4314. Total number of failed requests.
4315. 8547
4316. The number of requests for resources that were not found.
4317. 8549
4318. Number of requests failed due to unauthorized access.
4319. 8551
4320. The number of requests in the application request queue.
4321. 8553
4322. The number of requests that timed out.
4323. 8555
4324. The number of requests that executed successfully.
4325. 8557
4326. The total number of requests since the application was started.
4327. 8559
4328. The number of requests executed per second.
4329. 8561
4330. The current number of sessions currently active.
4331. 8563
4332. The number of sessions that have been explicitly abandoned.
4333. 8565
4334. The number of sessions timed out.
4335. 8567
4336. Total number of sessions since the application was started.
4337. 8569
4338. The number of transactions aborted.
4339. 8571
4340. The number of transactions committed.
4341. 8573
4342. Number of transactions in progress.
4343. 8575
4344. The total number of transactions since the application was started.
4345. 8577
4346. Transactions started per second.
4347. 8579
4348. The total number of connections to the State Server used by session state.
4349. 8581
4350. The total number of connections to the SQL Server used by session state.
4351. 8583
4352. Total number of instrumentation events raised since the application was started.
4353. 8585
4354. Total number of instrumentation events per second.
4355. 8587
4356. Number of application events raised since the application was started.
4357. 8589
4358. Number of application events raised per second.
4359. 8591
4360. Number of error events raised since the application was started.
4361. 8593
4362. Number of error events per second.
4363. 8595
4364. Number of runtime error events raised since the application was started.
4365. 8597
4366. Number of runtime error events per second.
4367. 8599
4368. Number of HTTP error events raised since the application was started.
4369. 8601
4370. Number of HTTP error events raised per second.
4371. 8603
4372. Number of request events raised since the application was started
4373. 8605
4374. Number of request events raised per second.
4375. 8607
4376. Number of audit successes in the application since it was started.
4377. 8609
4378. Number of audit failures in the application since it was started.
4379. 8611
4380. Number of successful membership credential validations since the application was started.
4381. 8613
4382. Number of failed membership credential validations since the application was started.
4383. 8615
4384. Number of successful forms authentication ticket validations since the application was started.
4385. 8617
4386. Number of failed forms authentication ticket validations since the application was started.
4387. 8619
4388. Number of viewstate MAC validations that failed since the application was started.
4389. 8621
4390. The number of milliseconds that it took to execute the most recent request.
4391. 8623
4392. The number of requests disconnected due to communication errors or user terminated.
4393. 8625
4394. The number of requests rejected because the application request queue was full.
4395. 8627
4396. The number of milliseconds the most recent request was waiting in the queue.
4397. 8629
4398. 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.
4399. 8631
4400. Cache % Machine Memory Limit Used Base
4401. 8633
4402. 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.
4403. 8635
4404. Cache % Process Memory Limit Used Base
4405. 8637
4406. Total number of entries forcibly removed from the cache due to memory pressure.
4407. 8639
4408. 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.
4409. 8641
4410. 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.
4411. 8643
4412. 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.
4413. 8645
4414. % Managed Processor Time Base (estimated)
4415. 8647
4416. 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.
4417. 8649
4418. The total size, in bytes, of data received by ASP.NET on WebSocket connections.
4419. 8651
4420. The total size, in bytes, of data sent to a client on WebSocket connections.
4421. 8653
4422. The number of WebSocket requests currently executing.
4423. 8655
4424. Total number of WebSocket requests that ended up in an aborted state.
4425. 8657
4426. Total number of WebSocket requests that completed gracefully.
4427. 8659
4428. The total number of WebSocket requests since the application was started.
4429. 9087
4430. SMSvcHost 4.0.0.0 performance counters
4431. 9089
4432. The total number of failures at the protocol layer of net.tcp.
4433. 9091
4434. The total number of failures at the protocol layer of net.pipe.
4435. 9093
4436. The total number of failures dispatching messages received over net.tcp.
4437. 9095
4438. The total number of failures dispatching messages received over net.pipe.
4439. 9097
4440. The total number of connections dispatched over net.tcp.
4441. 9099
4442. The total number of connections dispatched over net.pipe.
4443. 9101
4444. The total number of TCP connections accepted over net.tcp.
4445. 9103
4446. The total number of named pipe connections accepted over net.pipe.
4447. 9105
4448. The number of uri registrations currently active for net.tcp.
4449. 9107
4450. The number of uri registrations currently active for net.pipe.
4451. 9109
4452. The total number of uris that were succesfully registered for net.tcp.
4453. 9111
4454. The total number of uris that were succesfully registered for net.pipe.
4455. 9113
4456. The total number of uris that were succesfully unregistered for net.tcp.
4457. 9115
4458. The total number of uris that were succesfully unregistered for net.pipe.
4459. 9117
4460. MSDTC Bridge 4.0.0.0 performance counters
4461. 9119
4462. The number of WS-AT protocol messages that the WS-AT service failed to send per second.
4463. 9121
4464. The number of Prepare retry messages that the WS-AT service has sent per second.
4465. 9123
4466. The number of Commit retry messages that the WS-AT service has sent per second.
4467. 9125
4468. The number of Prepared retry messages that the WS-AT service has sent per second.
4469. 9127
4470. The number of Replay retry messages that the WS-AT service has sent per second.
4471. 9129
4472. The number of Fault messages that the WS-AT service has received per second.
4473. 9131
4474. The number of Fault messages that the WS-AT service has sent per second.
4475. 9133
4476. Average time in milliseconds for the WS-AT service to receive a Prepare message response from a participant.
4477. 9135
4478. Base counter for the 'Average participant prepare response time' counter.
4479. 9137
4480. Average time in milliseconds for the WS-AT service to receive a Commit message response from a participant.
4481. 9139
4482. Base counter for the 'Average participant commit response time' counter.
4483. 9141
4484. Windows Workflow Foundation Performance Counters
4485. 9143
4486. Total number of workflows created.
4487. 9145
4488. Rate of workflows created per second.
4489. 9147
4490. Total number of workflows unloaded.
4491. 9149
4492. Rate of workflows unloaded per second.
4493. 9151
4494. Total number of workflows loaded.
4495. 9153
4496. Rate of workflows loaded per second.
4497. 9155
4498. Total number of workflows completed.
4499. 9157
4500. Rate of workflows completed per second.
4501. 9159
4502. Total number of workflows suspended.
4503. 9161
4504. Rate of workflows suspended per second.
4505. 9163
4506. Total number of workflows terminated.
4507. 9165
4508. Rate of workflows terminated per second.
4509. 9167
4510. Total number of workflows in memory.
4511. 9169
4512. Total number of workflows aborted.
4513. 9171
4514. Rate of workflows aborted per second.
4515. 9173
4516. Total number of workflows persisted.
4517. 9175
4518. Rate of workflows persisted per second.
4519. 9177
4520. Total number of workflow instances actively executing.
4521. 9179
4522. Rate of workflows becoming idle per second.
4523. 9181
4524. Total number of workflows ready to execute.
4525. 9183
4526. Total number of workflows waiting for a thread.
4527. 12465
4528. ASP.NET State Service
4529. 12691
4530. The current number of sessions currently active.
4531. 12693
4532. The number of sessions that have been explicitly abandoned.
4533. 12695
4534. The number of sessions timed out.
4535. 12697
4536. The number of sessions total.
4537. 12699
4538. ASP.NET global performance counters
4539. 12701
4540. ASP.NET application performance counters
4541. 12703
4542. Number of times the application has been restarted during the web server's lifetime.
4543. 12705
4544. Number of currently running web applications.
4545. 12707
4546. The number of requests disconnected due to communication errors or user terminated.
4547. 12709
4548. The number of milliseconds that it took to execute the most recent request.
4549. 12711
4550. The number of requests rejected because the request queue was full.
4551. 12713
4552. The number of requests waiting to be processed.
4553. 12715
4554. Number of worker processes running on the machine.
4555. 12717
4556. Number of times a worker process has restarted on the machine.
4557. 12719
4558. The number of milliseconds the most recent request was waiting in the queue.
4559. 12721
4560. The current number of sessions currently active.
4561. 12723
4562. The number of sessions that have been explicitly abandoned.
4563. 12725
4564. The number of sessions timed out.
4565. 12727
4566. The number of sessions total.
4567. 12729
4568. 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.
4569. 12731
4570. Number of audit successes in the application since it was started.
4571. 12733
4572. Number of audit failures in the application since it was started.
4573. 12735
4574. Number of error events raised since the application was started.
4575. 12737
4576. Number of runtime error events raised since the application was started.
4577. 12739
4578. Number of HTTP error events raised since the application was started.
4579. 12741
4580. Requests queued because the concurrency limits have been exceeded.
4581. 12743
4582. Number of requests utilizing anonymous authentication.
4583. 12745
4584. Number of Authentication Anonymous Requests/Sec
4585. 12747
4586. Total number of entries within the cache (both internal and user added)
4587. 12749
4588. Number of additions and removals to the total cache per second.
4589. 12751
4590. Total number of hits from the cache.
4591. 12753
4592. Total number of cache misses.
4593. 12755
4594. Ratio of hits from all cache calls.
4595. 12757
4596. Cache Total Hit Ratio Base
4597. 12759
4598. Total number of entries within the cache added by the user.
4599. 12761
4600. Number of additions and removals to the API cache per second.
4601. 12763
4602. Number of cache hits from user code.
4603. 12765
4604. Number of cache misses called from user code.
4605. 12767
4606. Ratio of hits called from user code.
4607. 12769
4608. Cache API Hit Ratio Base
4609. 12771
4610. Current number of entries in the output cache.
4611. 12773
4612. Number of additions and removals to the output cache per second.
4613. 12775
4614. Total number of output cacheable requests served from the output cache.
4615. 12777
4616. Total number of output cacheable requests not served from the output cache.
4617. 12779
4618. Ratio of hits to requests for output cacheable requests.
4619. 12781
4620. Output Cache Hit Ratio Base
4621. 12783
4622. Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled.
4623. 12785
4624. Number of debugging requests processed.
4625. 12787
4626. Number of errors that have occurred during parsing and configuration.
4627. 12789
4628. Number of errors that have occurred during compilation.
4629. 12791
4630. Number of errors that have occurred during the processing of a request.
4631. 12793
4632. Number of errors not handled by user code, but by the default error handler.
4633. 12795
4634. Rate of unhandled errors.
4635. 12797
4636. Total number of errors occurred.
4637. 12799
4638. Rate of errors occurred.
4639. 12801
4640. Number of active pipeline instances.
4641. 12803
4642. The total size, in bytes, of all requests.
4643. 12805
4644. The total size, in bytes, of responses sent to a client. This does not include standard HTTP response headers.
4645. 12807
4646. The number of requests currently executing.
4647. 12809
4648. Total number of failed requests.
4649. 12811
4650. The number of requests for resources that were not found.
4651. 12813
4652. Number of requests failed due to unauthorized access.
4653. 12815
4654. The number of requests in the application request queue.
4655. 12817
4656. The number of requests that timed out.
4657. 12819
4658. The number of requests that executed successfully.
4659. 12821
4660. The total number of requests since the application was started.
4661. 12823
4662. The number of requests executed per second.
4663. 12825
4664. The current number of sessions currently active.
4665. 12827
4666. The number of sessions that have been explicitly abandoned.
4667. 12829
4668. The number of sessions timed out.
4669. 12831
4670. Total number of sessions since the application was started.
4671. 12833
4672. The number of transactions aborted.
4673. 12835
4674. The number of transactions committed.
4675. 12837
4676. Number of transactions in progress.
4677. 12839
4678. The total number of transactions since the application was started.
4679. 12841
4680. Transactions started per second.
4681. 12843
4682. The total number of connections to the State Server used by session state.
4683. 12845
4684. The total number of connections to the SQL Server used by session state.
4685. 12847
4686. Total number of instrumentation events raised since the application was started.
4687. 12849
4688. Total number of instrumentation events per second.
4689. 12851
4690. Number of application events raised since the application was started.
4691. 12853
4692. Number of application events raised per second.
4693. 12855
4694. Number of error events raised since the application was started.
4695. 12857
4696. Number of error events per second.
4697. 12859
4698. Number of runtime error events raised since the application was started.
4699. 12861
4700. Number of runtime error events per second.
4701. 12863
4702. Number of HTTP error events raised since the application was started.
4703. 12865
4704. Number of HTTP error events raised per second.
4705. 12867
4706. Number of request events raised since the application was started
4707. 12869
4708. Number of request events raised per second.
4709. 12871
4710. Number of audit successes in the application since it was started.
4711. 12873
4712. Number of audit failures in the application since it was started.
4713. 12875
4714. Number of successful membership credential validations since the application was started.
4715. 12877
4716. Number of failed membership credential validations since the application was started.
4717. 12879
4718. Number of successful forms authentication ticket validations since the application was started.
4719. 12881
4720. Number of failed forms authentication ticket validations since the application was started.
4721. 12883
4722. Number of viewstate MAC validations that failed since the application was started.
4723. 12885
4724. The number of milliseconds that it took to execute the most recent request.
4725. 12887
4726. The number of requests disconnected due to communication errors or user terminated.
4727. 12889
4728. The number of requests rejected because the application request queue was full.
4729. 12891
4730. The number of milliseconds the most recent request was waiting in the queue.
4731. 12893
4732. 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.
4733. 12895
4734. Cache % Machine Memory Limit Used Base
4735. 12897
4736. 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.
4737. 12899
4738. Cache % Process Memory Limit Used Base
4739. 12901
4740. Total number of entries forcibly removed from the cache due to memory pressure.
4741. 12903
4742. 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.
4743. 12905
4744. 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.
4745. 12907
4746. 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.
4747. 12909
4748. % Managed Processor Time Base (estimated)
4749. 12911
4750. 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.
4751. 12913
4752. The total size, in bytes, of data received by ASP.NET on WebSocket connections.
4753. 12915
4754. The total size, in bytes, of data sent to a client on WebSocket connections.
4755. 12917
4756. The number of WebSocket requests currently executing.
4757. 12919
4758. Total number of WebSocket requests that ended up in an aborted state.
4759. 12921
4760. Total number of WebSocket requests that completed gracefully.
4761. 12923
4762. The total number of WebSocket requests since the application was started.
4763. 12925
4764. Number of WMI High Performance provider returned by WMI Adapter
4765. 12927
4766. Shows High Performance Classes
4767. 12929
4768. Shows if High Performance Classes are valid
4769. 12931
4770. BatteryStatus
4771. 12933
4772. ChargeRate
4773. 12935
4774. DischargeRate
4775. 12937
4776. RemainingCapacity
4777. 12939
4778. Tag
4779. 12941
4780. Voltage
4781. 12943
4782. MSiSCSI_ConnectionStatistics
4783. 12945
4784. BytesReceived
4785. 12947
4786. BytesSent
4787. 12949
4788. PDUCommandsSent
4789. 12951
4790. PDUResponsesReceived
4791. 12953
4792. MSiSCSI_InitiatorInstanceStatistics
4793. 12955
4794. SessionConnectionTimeoutErrorCount
4795. 12957
4796. SessionDigestErrorCount
4797. 12959
4798. SessionFailureCount
4799. 12961
4800. SessionFormatErrorCount
4801. 12963
4802. MSiSCSI_InitiatorLoginStatistics
4803. 12965
4804. LoginAcceptRsps
4805. 12967
4806. LoginAuthenticateFails
4807. 12969
4808. LoginAuthFailRsps
4809. 12971
4810. LoginFailures
4811. 12973
4812. LoginNegotiateFails
4813. 12975
4814. LoginOtherFailRsps
4815. 12977
4816. LoginRedirectRsps
4817. 12979
4818. LogoutNormals
4819. 12981
4820. LogoutOtherCodes
4821. 12983
4822. MSiSCSI_MMIPSECStats
4823. 12985
4824. AcquireFailures
4825. 12987
4826. AcquireHeapSize
4827. 12989
4828. ActiveAcquire
4829. 12991
4830. ActiveReceive
4831. 12993
4832. AuthenticationFailures
4833. 12995
4834. ConnectionListSize
4835. 12997
4836. GetSPIFailures
4837. 12999
4838. InvalidCookiesReceived
4839. 13001
4840. InvalidPackets
4841. 13003
4842. KeyAdditionFailures
4843. 13005
4844. KeyAdditions
4845. 13007
4846. KeyUpdateFailures
4847. 13009
4848. KeyUpdates
4849. 13011
4850. NegotiationFailures
4851. 13013
4852. OakleyMainMode
4853. 13015
4854. OakleyQuickMode
4855. 13017
4856. ReceiveFailures
4857. 13019
4858. ReceiveHeapSize
4859. 13021
4860. SendFailures
4861. 13023
4862. SoftAssociations
4863. 13025
4864. TotalGetSPI
4865. 13027
4866. MSiSCSI_NICPerformance
4867. 13029
4868. BytesReceived
4869. 13031
4870. BytesTransmitted
4871. 13033
4872. PDUReceived
4873. 13035
4874. PDUTransmitted
4875. 13037
4876. MSiSCSI_QMIPSECStats
4877. 13039
4878. ActiveSA
4879. 13041
4880. ActiveTunnels
4881. 13043
4882. AuthenticatedBytesReceived
4883. 13045
4884. AuthenticatedBytesSent
4885. 13047
4886. BadSPIPackets
4887. 13049
4888. ConfidentialBytesReceived
4889. 13051
4890. ConfidentialBytesSent
4891. 13053
4892. KeyAdditions
4893. 13055
4894. KeyDeletions
4895. 13057
4896. PacketsNotAuthenticated
4897. 13059
4898. PacketsNotDecrypted
4899. 13061
4900. PacketsWithReplayDetection
4901. 13063
4902. PendingKeyOperations
4903. 13065
4904. ReKeys
4905. 13067
4906. TransportBytesReceived
4907. 13069
4908. TransportBytesSent
4909. 13071
4910. TunnelBytesReceived
4911. 13073
4912. TunnelBytesSent
4913. 13075
4914. MSiSCSI_RequestTimeStatistics
4915. 13077
4916. AverageProcessingTime
4917. 13079
4918. MaximumProcessingTime
4919. 13081
4920. MSiSCSI_SessionStatistics
4921. 13083
4922. BytesReceived
4923. 13085
4924. BytesSent
4925. 13087
4926. ConnectionTimeoutErrors
4927. 13089
4928. DigestErrors
4929. 13091
4930. FormatErrors
4931. 13093
4932. PDUCommandsSent
4933. 13095
4934. PDUResponsesReceived
4935. 13097
4936. ProcessorPerformance
4937. 13099
4938. frequency
4939. 13101
4940. percentage
4941. 13103
4942. power
4943. 13105
4944. Video_Scheduler_Statistics
4945. 13107
4946. WmiCompletedDMABufferCount
4947. 13109
4948. WmiGPUBusy
4949. 13111
4950. WmiGPUContext
4951. 13113
4952. WmiGPUContextSwitch
4953. 13115
4954. WmiPreemptedDMABufferCount
4955. 13117
4956. WmiPresentCount
4957. 13119
4958. WmiSubmitDMABufferCount
4959. 9039
4960. Compteurs de performances WorkflowServiceHost du service de workflow
4961. 9041
4962. Nombre total d'instances de workflows créées depuis le démarrage du serveur d'hébergement de workflow.
4963. 9043
4964. Taux d'instances de workflows créées par seconde.
4965. 9045
4966. Nombre total d'instances de workflows en cours d'exécution.
4967. 9047
4968. Nombre total d'instances de workflows terminées depuis le démarrage du serveur d'hébergement de workflow.
4969. 9049
4970. Taux d'instances de workflows terminées par seconde.
4971. 9051
4972. Nombre total d'instances de workflows annulées depuis le démarrage du serveur d'hébergement de workflow.
4973. 9053
4974. Taux d'instances de workflows annulées par seconde.
4975. 9055
4976. Nombre total d'instances de workflows actuellement en mémoire.
4977. 9057
4978. Nombre total d'instances de workflows rendues persistantes depuis le démarrage du serveur d'hébergement de workflow.
4979. 9059
4980. Taux d'instances de workflows persistantes par seconde.
4981. 9061
4982. Nombre total d'instances de workflows arrêtées depuis le démarrage du serveur d'hébergement de workflow.
4983. 9063
4984. Taux d'instances de workflows arrêtées par seconde.
4985. 9065
4986. Nombre total d'instances de workflows chargées depuis le démarrage du serveur d'hébergement de workflow.
4987. 9067
4988. Taux d'instances de workflows chargées par seconde.
4989. 9069
4990. Nombre total d'instances de workflows déchargées depuis le démarrage du serveur d'hébergement de workflow.
4991. 9071
4992. Taux d'instances de workflows déchargées par seconde.
4993. 9073
4994. Nombre total d'instances de workflows interrompues depuis le démarrage du serveur d'hébergement de workflow.
4995. 9075
4996. Taux d'instances de workflows interrompues par seconde.
4997. 9077
4998. Taux d'instances de workflows devenant inactives par seconde.
4999. 9079
5000. Durée moyenne du chargement d'une instance de workflow.
5001. 9081
5002. Durée de base moyenne de chargement d'une instance de workflow.
5003. 9083
5004. Durée moyenne de persistance des instances de workflows.
5005. 9085
5006. Durée de base moyenne de persistance d'une instance de workflow.
5007. 4699
5008. Informations de résumé des services Terminal Server
5009. 4701
5010. Nombre de sessions actives des services Terminal Server
5011. 4703
5012. Nombre de sessions inactives des services Terminal Server
5013. 4705
5014. Nombre total de sessions des services Terminal Server
5015. 1927
5016. WFPv4 est l’ensemble de compteurs de la plateforme de filtrage Windows qui s’appliquent au trafic et aux connexions via le protocole IPv4.
5017. 1929
5018. 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.
5019. 1931
5020. 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.
5021. 1933
5022. 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.
5023. 1935
5024. 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é.
5025. 1937
5026. 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.
5027. 1939
5028. 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.
5029. 1941
5030. 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.
5031. 1943
5032. 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.
5033. 1945
5034. 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é.
5035. 1947
5036. 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é.
5037. 1949
5038. Le compteur Connexions entrantes actives représente le nombre de connexions entrantes autorisées par la plateforme de filtrage Windows.
5039. 1951
5040. Le compteur Connexions sortantes actives représente le nombre de connexions sortantes autorisées par la plateforme de filtrage Windows.
5041. 1953
5042. Le compteur Classifications autorisées/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.
5043. 1987
5044. 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.
5045. 1989
5046. Associations de sécurité active est le nombre d’associations de sécurité de mode rapide actives.
5047. 1991
5048. Les associations de sécurité en attente représentent le nombre d’associations de sécurité en mode rapide en attente.
5049. 1993
5050. 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.
5051. 1995
5052. Le compteur Octets reçus en mode tunnel par seconde représente le nombre d’octets reçus par seconde avec le mode tunnel.
5053. 1997
5054. Le compteur Octets reçus en mode tunnel par seconde représente le nombre d’octets envoyés par seconde avec le mode tunnel d’IPsec.
5055. 1999
5056. Le compteur Octets reçus en mode transport par seconde représente le nombre d’octets reçus par seconde avec le mode transport.
5057. 2001
5058. Le compteur Octets envoyés en mode transport par seconde représente le débit d’octets envoyés par seconde avec le mode transport.
5059. 2003
5060. 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.
5061. 2005
5062. 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.
5063. 2007
5064. 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.
5065. 2009
5066. 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.
5067. 2011
5068. 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éseaux.
5069. 2013
5070. 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.
5071. 2015
5072. 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.
5073. 2017
5074. 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.
5075. 2019
5076. 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.
5077. 2021
5078. Le compteur Paquets ayant échoué à la validation EDP-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.
5079. 2023
5080. 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.
5081. 2025
5082. 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.
5083. 1983
5084. WFP est l’ensemble de compteurs de la plateforme de filtrage Windows qui ne s’appliquent à aucune version spécifique du protocole IP.
5085. 1985
5086. Le compteur Nombre de fournisseurs est le nombre de fournisseurs inscrits avec la plateforme de filtrage Windows.
5087. 1955
5088. WFPv6 est l’ensemble de compteurs de la plateforme de filtrage Windows qui s’appliquent au trafic et aux connexions sur le protocole IPv6.
5089. 1957
5090. 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.
5091. 1959
5092. 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.
5093. 1961
5094. 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.
5095. 1963
5096. 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é.
5097. 1965
5098. 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.
5099. 1967
5100. 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.
5101. 1969
5102. 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.
5103. 1971
5104. 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.
5105. 1973
5106. 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é.
5107. 1975
5108. 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é.
5109. 1977
5110. Le compteur Connexions entrantes actives représente le nombre de connexions entrantes autorisées par la plateforme de filtrage Windows.
5111. 1979
5112. Le compteur Connexions sortantes actives représente le nombre de connexions sortantes autorisées par la plateforme de filtrage Windows.
5113. 1981
5114. Le compteur Classifications autorisées/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.
5115. 4707
5116. Ensemble de compteurs pour l’objet d’application Gestionnaire d’autorisations
5117. 4709
5118. Affiche le nombre total d’étendues dans l’application
5119. 4711
5120. Affiche le nombre d’étendues actuellement chargées en mémoire
5121. 4847
5122. Objet de performance des dossiers répliqués DFS. Il comprend des compteurs de quotas intermédiaires et de conflits.
5123. 4849
5124. Fichiers en conflit générés indique le nombre de fichiers et de dossiers dans ce dossier répliqué que le service de réplication DFS a déplacé vers le dossier des fichiers en conflit et supprimés. Le service de réplication DFS détecte et résout automatiquement les conflits rencontrés dans les dossiers répliqués et place la version qui ne prévaut pas dans le dossier des fichiers en conflit et supprimés. Le service nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5125. 4851
5126. Octets en conflit générés indique la taille totale (en octets) des fichiers et des dossiers dans ce dossier répliqué que le service de réplication DFS a déplacé vers le dossier des fichiers en conflit et supprimés. Le service de réplication DFS détecte et résout automatiquement les conflits rencontrés dans les dossiers répliqués et place la version qui ne prévaut pas dans le dossier des fichiers en conflit et supprimés. Le service nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5127. 4853
5128. Fichiers en conflit nettoyés indique le nombre de fichiers et dossiers en conflit ne faisant pas précédence qui ont été supprimés du dossier des fichiers en conflit et supprimés par le service de réplication DFS. Le service de réplication DFS détecte et résout automatiquement les conflits rencontrés dans les dossiers répliqués et place la version qui ne prévaut pas dans le dossier des fichiers en conflit et supprimés. Le service nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5129. 4855
5130. Octets en conflit nettoyés indique la taille totale (en octets) des fichiers et dossiers en conflit ne faisant pas précédence qui ont été supprimés du dossier des fichiers en conflit et supprimés par le service de réplication DFS. Le service de réplication DFS détecte et résout automatiquement les conflits rencontrés dans les dossiers répliqués et place la version qui ne prévaut pas dans le dossier des fichiers en conflit et supprimés. Le service nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5131. 4857
5132. Espace de conflits utilisé indique la taille totale (en octets) des fichiers et dossiers en conflit ne faisant pas précédence se trouvant dans le dossier des fichiers en conflit et supprimés utilisé par le service de réplication DFS. Le service de réplication DFS détecte et résout automatiquement les conflits rencontrés dans les dossiers répliqués et place la version qui ne prévaut pas dans le dossier des fichiers en conflit et supprimés. Le service nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5133. 4859
5134. Nettoyages du dossier des conflits indique le nombre de suppressions des fichiers et dossiers en conflit ne faisant pas précédence du dossier des fichiers en conflit et supprimés effectué par le service de réplication DFS. Le service de réplication DFS détecte et résout automatiquement les conflits rencontrés dans les dossiers répliqués et place la version qui ne prévaut pas dans le dossier des fichiers en conflit et supprimés. Le service nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5135. 4861
5136. Installations de fichiers réussies indique le nombre de fichiers reçus de membres d’envoi et installés localement sur le serveur. Le service de réplication DFS réplique les fichiers intermédiaires dans le dossier intermédiaire, les décompresse dans le dossier d’installation et les renomme en fonction de l’emplacement cible. Les deuxième et troisième étapes de ce processus constituent l’installation des fichiers.
5137. 4863
5138. Nouvelles tentatives d’installation de fichiers indique le nombre de tentatives d’installation de fichiers effectué en raison de violations de partage ou d’autres erreurs rencontrées lors de l’installation de fichiers. Le service de réplication DFS réplique les fichiers intermédiaires dans le dossier intermédiaire, les décompresse dans le dossier d’installation et les renomme en fonction de l’emplacement cible. Les deuxième et troisième étapes de ce processus constituent l’installation de fichiers.
5139. 4865
5140. Mises à jour supprimées indique le nombre d’enregistrements de mise à jour de réplication de fichiers redondants qui ont été ignorés par le service de réplication DFS, car le fichier ou dossier répliqué n’a pas été modifié. Par exemple, des mises à jour peuvent être ignorées lorsque les listes de contrôle d’accès sont remplacées par des listes identiques pour un fichier ou un dossier.
5141. 4867
5142. Fichiers supprimés générés indique le nombre de fichiers et dossiers répliqués supprimés qui ont été déplacés vers le dossier des fichiers en conflit et supprimés une fois supprimés d’un dossier répliqué sur un membre d’envoi. Le service de réplication DFS nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5143. 4869
5144. Octets supprimés générés indique la taille totale (en octets) des fichiers et dossiers répliqués supprimés qui ont été déplacés vers le dossier des fichiers en conflit et supprimés une fois supprimés d’un dossier répliqué sur un membre d’envoi. Le service de réplication DFS nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5145. 4871
5146. Fichiers supprimés nettoyés indique le nombre de fichiers répliqués supprimés qui ont été supprimés du dossier des fichiers en conflit et supprimés par le service de réplication DFS. Le service de réplication DFS nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5147. 4873
5148. Octets supprimés nettoyés indique la taille totale (en octets) des fichiers de réplication supprimés qui ont été nettoyés du dossier des fichiers en conflit et supprimés par le service de réplication DFS. Le service de réplication DFS nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5149. 4875
5150. Espace utilisé par les fichiers supprimés indique la taille totale (en octets) des fichiers et dossiers supprimés dans le dossier des fichiers en conflit et supprimés utilisé par le service de réplication DFS. Le service de réplication DFS détecte les suppressions à distance de son partenaire d’envoi et déplace le fichier ou le dossier vers le dossier des fichiers en conflit et supprimé. Le service nettoie automatiquement le dossier des fichiers en conflit et supprimés lorsque le seuil préconfiguré du quota est dépassé.
5151. 4877
5152. Total des fichiers reçus indique le nombre de fichiers reçus par le dossier répliqué.
5153. 4879
5154. Taille des fichiers reçus indique la taille décompressée (en octets) des fichiers reçus pour le dossier répliqué. Il s’agit du nombre d’octets qui auraient été reçus si la compression de réplication DFS n’avait pas été utilisée.
5155. 4881
5156. Taille compressée des fichiers reçus indique la taille compressée (en octets) des fichiers reçus pour le dossier répliqué.
5157. 4883
5158. RDC - Nombre de fichiers reçus indique le nombre de fichiers reçus pour le dossier répliqué.
5159. 4885
5160. RDC - Taille des fichiers reçus indique la taille décompressée (en octets) des fichiers reçus avec la compression différentielle à distance (RDC) pour ce dossier répliqué. Il s’agit du nombre d’octets qui auraient été reçus si la compression ou RDC n’avait pas été utilisée, et non du nombre d’octets réellement reçus sur le réseau.
5161. 4887
5162. RDC - Taille compressée des fichiers reçus indique la taille compressée (en octets) des fichiers reçus avec la compression différentielle à distance (RDC) pour le dossier répliqué. Il s’agit du nombre d’octets qui auraient été reçus si RDC n’avait pas été utilisée, et non du nombre d’octets réellement reçus sur le réseau.
5163. 4889
5164. RDC - Octets reçus indique le nombre d’octets reçus lors de la réplication des fichiers avec la compression différentielle à distance (RDC) pour le dossier répliqué. Il s’agit du nombre d’octets réellement reçus sur le réseau sans le traitement des protocoles de gestion réseau.
5165. 4891
5166. Économies de bande passante réalisées grâce à la réplication DFS indique le pourcentage de bande passante économisé par le service de réplication DFS pour le dossier répliqué en associant la compression différentielle à distance (RDC) à d’autres technologies de compression réduisant l’utilisation de la bande passante réseau. Par exemple, une valeur de 20 indique que le service de réplication DFS a utilisé 20 % de bande passante en moins que si les fichiers avaient été transférés sur le réseau sans être compressés.
5167. 4893
5168. Objet de performance des connexions de réplication DFS pour les connexions entrantes.
5169. 4895
5170. Total des octets reçus indique le nombre total d’octets reçus sur la connexion. Cette valeur comprend les données de fichiers et les métadonnées de réplication.
5171. 4897
5172. Total des fichiers reçus indique le nombre de fichiers reçus sur la connexion.
5173. 4899
5174. Taille des fichiers reçus indique la taille décompressée (en octets) des fichiers reçus sur la connexion. Il s’agit du nombre d’octets qui auraient été reçus si la compression de réplication DFS n’avait pas été utilisée.
5175. 4901
5176. Taille compressée des fichiers reçus indique la taille compressée (en octets) des fichiers reçus sur la connexion.
5177. 4903
5178. Octets reçus par seconde indique une estimation du nombre moyen d’octets reçus par seconde au cours des 30 dernières secondes.
5179. 4905
5180. RDC - Nombre de fichiers reçus indique le nombre de fichiers reçus sur la connexion.
5181. 4907
5182. RDC - Taille des fichiers reçus indique la taille décompressée (en octets) des fichiers reçus avec la compression différentielle à distance (RDC) sur la connexion. Il s’agit du nombre d’octets qui auraient été reçus si la compression ou RDC n’avait pas été utilisée, et non du nombre d’octets réellement reçus sur le réseau.
5183. 4909
5184. RDC - Taille compressée des fichiers reçus indique la taille compressée (en octets) des fichiers reçus avec la compression différentielle à distance (RDC) sur la connexion. Il s’agit du nombre d’octets qui auraient été reçus si RDC n’avait pas été utilisée, et non du nombre d’octets réellement reçus sur le réseau.
5185. 4911
5186. RDC - Octets reçus indique les octets reçus sur la connexion lors de la réplication des fichiers avec la compression différentielle à distance (RDC). Il s’agit du nombre d’octets réellement reçus sur le réseau sans le traitement des protocoles de gestion réseau.
5187. 4913
5188. Économies de bande passante réalisées grâce à la réplication DFS indique le pourcentage de bande passante économisé par le service de réplication DFS sur la connexion en associant la compression différentielle à distance (RDC) à d’autres technologies de compression réduisant l’utilisation de bande passante réseau. Par exemple, une valeur de 20 indique que le service de réplication DFS a utilisé 20 % de bande passante en moins que si les fichiers avaient été transférés sur le réseau sans être compressés.
5189. 4835
5190. Objet de performance du volume du service de réplication DFS. Il comprend des compteurs relatifs aux enregistrements de journal USN et au traitement de base de données sur chaque volume.
5191. 4837
5192. Enregistrements de journal USN lus indique le nombre d’enregistrements de journal USN lus par le service de réplication DFS.
5193. 4839
5194. Enregistrements de journal USN acceptés indique le nombre d’enregistrements de journal USN traités par le service de réplication DFS. Ce service traite tous les enregistrements de journal USN de contenu répliqué sur un volume et ignore les enregistrements des fichiers et dossiers non répliqués sur le volume.
5195. 4841
5196. Pourcentage non lu du journal UNS indique le pourcentage du journal USN qui n’a pas encore été lu et traité par le service de réplication DFS. Un dépassement de taille de journal se produit lorsque ce compteur atteint 100.
5197. 4843
5198. Validations de base de données indique le nombre d’opérations de validation de base de données effectué par le service de réplication DFS. Ce compteur indique la charge du service de réplication DFS du point de vue de la base de données.
5199. 4845
5200. Recherches de base de données indique le nombre d’opérations de recherche de base de données effectué par le service de réplication DFS. Ce compteur indique la charge du service de réplication DFS du point de vue de la base de données.
5201. 2223
5202. IKE et AuthIP génériques et le jeu de compteurs Internet Protocol Security (IPsec) Internet Key Exchange (IKE) et Authenticated IP (AuthIP) génériques qui ne s'appliquent pas à une version spécifique du protocole Internet.
5203. 2225
5204. Le compteur Durée de négociation en mode principal IKE représente le nombre de millisecondes requis par la dernière association de sécurité négociée en mode principal IKE.
5205. 2227
5206. 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.
5207. 2229
5208. Le compteur Durée de négociation en mode rapide IKE représente le nombre de millisecondes requis par la dernière association de sécurité négociée en mode rapide IKE.
5209. 2231
5210. 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.
5211. 2233
5212. 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.
5213. 2235
5214. Paquets reçus par seconde est le nombre de paquets IPsec validés par seconde.
5215. 2237
5216. Le compteur Paquets non valides reçus par seconde représente le nombre de paquets IPsec non valides reçus par seconde.
5217. 2239
5218. Le compteur Négociations réussies représente le nombre de négociations achevées pour IKE et AuthIP depuis le dernier démarrage d'IPSec.
5219. 2241
5220. Le compteur Négociations réussies par seconde représente le nombre de négociations achevées pour IKE et AuthIP.
5221. 2243
5222. Le compteur Négociations en échec représente le nombre de négociations en échec pour IKE et AuthIP depuis le dernier démarrage d'IPSec.
5223. 2245
5224. Le compteur Négociations en échec/seconde représente le nombre de négociations ayant échoué pour IKE et AuthIP.
5225. 2103
5226. IPsec AuthIPv4 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 4.
5227. 2105
5228. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
5229. 2107
5230. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
5231. 2109
5232. 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.
5233. 2111
5234. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées à la seconde.
5235. 2113
5236. 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.
5237. 2115
5238. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées.
5239. 2117
5240. 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.
5241. 2119
5242. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué à la seconde.
5243. 2121
5244. 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 homologue depuis le dernier démarrage d’IPsec.
5245. 2123
5246. 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 homologue à la seconde.
5247. 2125
5248. 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.
5249. 2127
5250. Le compteur Associations de sécurité en mode principal ayant utilisé l’emprunt d’identité par seconde est le nombre par seconde d’associations de sécurité en mode principal réalisées à l’aide de l’emprunt d’identité.
5251. 2129
5252. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
5253. 2131
5254. Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
5255. 2133
5256. 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.
5257. 2135
5258. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées à la seconde.
5259. 2137
5260. 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.
5261. 2139
5262. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées à la seconde.
5263. 2141
5264. 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.
5265. 2143
5266. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué à la seconde.
5267. 2145
5268. Le compteur Associations de sécurité actives en mode étendu représente le nombre d’associations de sécurité en mode étendu actuellement actives.
5269. 2147
5270. 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.
5271. 2149
5272. 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.
5273. 2151
5274. Le compteur Négociations en mode étendu par seconde représente le nombre de négociations en mode étendu tentées à la seconde.
5275. 2153
5276. 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.
5277. 2155
5278. 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.
5279. 2157
5280. Le compteur Négociations en mode étendu en échec représente le nombre de négociations en mode étendu ayant échoué depuis le dernier démarrage d’IPsec.
5281. 2159
5282. 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.
5283. 2161
5284. 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.
5285. 2163
5286. IPsec AuthIPv6 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.
5287. 2165
5288. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
5289. 2167
5290. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
5291. 2169
5292. 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.
5293. 2171
5294. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées à la seconde.
5295. 2173
5296. 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.
5297. 2175
5298. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées.
5299. 2177
5300. 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.
5301. 2179
5302. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué à la seconde.
5303. 2181
5304. 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 homologue depuis le dernier démarrage d’IPsec.
5305. 2183
5306. 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 homologue à la seconde.
5307. 2185
5308. 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.
5309. 2187
5310. Le compteur Associations de sécurité en mode principal ayant utilisé l’emprunt d’identité par seconde est le nombre par seconde d’associations de sécurité en mode principal réalisées à l’aide de l’emprunt d’identité.
5311. 2189
5312. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
5313. 2191
5314. Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
5315. 2193
5316. 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.
5317. 2195
5318. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées à la seconde.
5319. 2197
5320. 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.
5321. 2199
5322. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées à la seconde.
5323. 2201
5324. 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.
5325. 2203
5326. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué à la seconde.
5327. 2205
5328. Le compteur Associations de sécurité actives en mode étendu représente le nombre d’associations de sécurité en mode étendu actuellement actives.
5329. 2207
5330. 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.
5331. 2209
5332. 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.
5333. 2211
5334. Le compteur Négociations en mode étendu par seconde représente le nombre de négociations en mode étendu tentées à la seconde.
5335. 2213
5336. 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.
5337. 2215
5338. 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.
5339. 2217
5340. Le compteur Négociations en mode étendu en échec représente le nombre de négociations en mode étendu ayant échoué depuis le dernier démarrage d’IPsec.
5341. 2219
5342. 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.
5343. 2221
5344. 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.
5345. 2027
5346. IPsec IKEv4 est l’ensemble de compteurs Internet Key Exchange (IKE) de sécurité du protocole Internet (IPsec) qui s’appliquent au trafic et aux connexions via IPv4.
5347. 2029
5348. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
5349. 2031
5350. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
5351. 2033
5352. 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.
5353. 2035
5354. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées à la seconde.
5355. 2037
5356. 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.
5357. 2039
5358. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées.
5359. 2041
5360. 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.
5361. 2043
5362. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué à la seconde.
5363. 2045
5364. 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 homologue depuis le dernier démarrage d’IPsec.
5365. 2047
5366. 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 homologue à la seconde.
5367. 2049
5368. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
5369. 2051
5370. Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
5371. 2053
5372. 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.
5373. 2055
5374. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées à la seconde.
5375. 2057
5376. 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.
5377. 2059
5378. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées à la seconde.
5379. 2061
5380. 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.
5381. 2063
5382. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué à la seconde.
5383. 2065
5384. IPsec IKEv6 est l’ensemble de compteurs Internet Key Exchange (IKE) de sécurité du protocole Internet (IPsec) qui s’appliquent au trafic et aux connexions via IPv6.
5385. 2067
5386. Le compteur Associations de sécurité actives en mode principal représente le nombre d’associations de sécurité en mode principal actuellement actives.
5387. 2069
5388. Le compteur Négociations en mode principal en attente représente le nombre de négociations en mode principal en attente.
5389. 2071
5390. 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.
5391. 2073
5392. Le compteur Négociations en mode principal par seconde représente le nombre de négociations en mode principal tentées à la seconde.
5393. 2075
5394. 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.
5395. 2077
5396. Le compteur Négociations en mode principal réussies par seconde représente le nombre de négociations en mode principal achevées.
5397. 2079
5398. 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.
5399. 2081
5400. Le compteur Négociations en mode principal en échec par seconde représente le nombre de négociations en mode principal ayant échoué à la seconde.
5401. 2083
5402. 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 homologue depuis le dernier démarrage d’IPsec.
5403. 2085
5404. 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 homologue à la seconde.
5405. 2087
5406. Le compteur Associations de sécurité actives en mode rapide représente le nombre d’associations de sécurité en mode rapide actuellement actives.
5407. 2089
5408. Négociations en mode rapide en attente représente le nombre de négociations en mode rapide en attente.
5409. 2091
5410. 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.
5411. 2093
5412. Le compteur Négociations en mode rapide par seconde représente le nombre de négociations en mode rapide tentées à la seconde.
5413. 2095
5414. 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.
5415. 2097
5416. Le compteur Négociations en mode rapide réussies par seconde représente le nombre de négociations en mode rapide achevées à la seconde.
5417. 2099
5418. 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.
5419. 2101
5420. Le compteur Négociations en mode rapide en échec par seconde représente le nombre de négociations en mode rapide ayant échoué à la seconde.
5421. 8887
5422. Compteurs de performance ServiceModel pour le service
5423. 8889
5424. Nombre d'appels à ce service. http://go.microsoft.com/fwlink/?LinkId=222530
5425. 8891
5426. Nombre d'appels à ce service par seconde. http://go.microsoft.com/fwlink/?LinkId=222531
5427. 8893
5428. Nombre d'appels en cours à ce service. http://go.microsoft.com/fwlink/?LinkId=222532
5429. 8895
5430. Nombre d'appels avec des exceptions non prises en charge dans ce service. http://go.microsoft.com/fwlink/?LinkId=222533
5431. 8897
5432. Nombre d'appels avec des exceptions non prises en charge dans ce service par seconde. http://go.microsoft.com/fwlink/?LinkId=222534
5433. 8899
5434. Nombre d'appels à ce service qui ont renvoyé des erreurs. http://go.microsoft.com/fwlink/?LinkId=222535
5435. 8901
5436. Nombre d'appels à ce service qui ont renvoyé des erreurs par seconde. http://go.microsoft.com/fwlink/?LinkId=222536
5437. 8903
5438. Durée moyenne des appels à ce service. http://go.microsoft.com/fwlink/?LinkId=222537
5439. 8905
5440. Nombre d'appels à ce service dont la validation ou l'authentification a échoué. http://go.microsoft.com/fwlink/?LinkId=222558
5441. 8907
5442. Nombre d'appels à ce service dont la validation ou l'authentification a échoué par seconde. http://go.microsoft.com/fwlink/?LinkId=222559
5443. 8909
5444. Nombre d'appels à ce service avec échec d'autorisation. http://go.microsoft.com/fwlink/?LinkId=222555
5445. 8911
5446. Nombre d'appels à ce service avec échec d'autorisation par seconde. http://go.microsoft.com/fwlink/?LinkId=222556
5447. 8913
5448. Nombre total d'instances du service. http://go.microsoft.com/fwlink/?LinkId=222538
5449. 8915
5450. Vitesse de création des instances de service par seconde. http://go.microsoft.com/fwlink/?LinkId=222539
5451. 8917
5452. Nombre de sessions de messagerie fiables en erreur dans ce service. http://go.microsoft.com/fwlink/?LinkId=222552
5453. 8919
5454. Nombre de sessions de messagerie fiables en erreur dans ce service par seconde. http://go.microsoft.com/fwlink/?LinkId=222553
5455. 8921
5456. Nombre de messages de messagerie fiables déposés dans ce service. http://go.microsoft.com/fwlink/?LinkId=222550
5457. 8923
5458. Nombre de messages de messagerie fiables déposés dans ce service par seconde. http://go.microsoft.com/fwlink/?LinkId=222551
5459. 8925
5460. Nombre de transactions passées à des opérations dans ce service. Ce compteur est incrémenté chaque fois qu'un ID de transaction est présent dans le message envoyé au service. http://go.microsoft.com/fwlink/?LinkId=222560
5461. 8927
5462. Nombre de transactions passées à des opérations dans ce service par seconde. Ce compteur est incrémenté chaque fois qu'un ID de transaction est présent dans le message envoyé au service. http://go.microsoft.com/fwlink/?LinkId=222561
5463. 8929
5464. Nombre d'opérations traitées avec des résultats validés dans ce service. Le travail effectué dans le cadre de telles opérations a été entièrement validé. Les ressources sont mises à jour en fonction du travail effectué dans l'opération. http://go.microsoft.com/fwlink/?LinkId=222564
5465. 8931
5466. Nombre d'opérations traitées avec des résultats validés dans ce service par seconde. Le travail effectué dans le cadre de telles opérations a été entièrement validé. Les ressources sont mises à jour en fonction du travail effectué dans l'opération. http://go.microsoft.com/fwlink/?LinkId=222565
5467. 8933
5468. Nombre d'opérations traitées avec des résultats annulés dans ce service. Le travail effectué dans le cadre de telles opérations est restauré. Les ressources sont rétablies à leur état antérieur. http://go.microsoft.com/fwlink/?LinkId=222562
5469. 8935
5470. Nombre d'opérations traitées avec des résultats annulés dans ce service par seconde. Le travail effectué dans le cadre de telles opérations est restauré. Les ressources sont rétablies à leur état antérieur. http://go.microsoft.com/fwlink/?LinkId=222563
5471. 8937
5472. Nombre d'opérations traitées avec des résultats incertains dans ce service. L'état d'un travail effectué avec un résultat incertain est indéterminé. Les ressources sont conservées dans l'attente des résultats. http://go.microsoft.com/fwlink/?LinkId=222566
5473. 8939
5474. Nombre d'opérations traitées avec des résultats incertains dans ce service par seconde. L'état d'un travail effectué avec un résultat incertain est indéterminé. Les ressources sont conservées dans l'attente des résultats. http://go.microsoft.com/fwlink/?LinkId=222567
5475. 8941
5476. Nombre de messages à ce service marqués comme étant empoisonnés par le transport de mise en file d'attente. http://go.microsoft.com/fwlink/?LinkId=222546
5477. 8943
5478. Nombre de messages à ce service marqués comme étant empoisonnés par le transport de mise en file d'attente par seconde. http://go.microsoft.com/fwlink/?LinkId=222547
5479. 8945
5480. Nombre de messages à ce service rejetés par le transport de mise en file d'attente. http://go.microsoft.com/fwlink/?LinkId=222548
5481. 8947
5482. Nombre de messages à ce service rejetés par le transport de mise en file d'attente par seconde. http://go.microsoft.com/fwlink/?LinkId=222549
5483. 8949
5484. Nombre de messages à ce service déposés par le transport de mise en file d'attente. http://go.microsoft.com/fwlink/?LinkId=222543
5485. 8951
5486. Nombre de messages à ce service déposés par le transport de mise en file d'attente par seconde. http://go.microsoft.com/fwlink/?LinkId=222544
5487. 8953
5488. Nombre d'appels en attente ou en cours de traitement dans le répartiteur en pourcentage de la limitation d'appels maximale. http://go.microsoft.com/fwlink/?LinkId=222540
5489. 8955
5490. Nombre d'instances actives et de messages en attente d'instances en pourcentage de la limitation d'instances maximale. http://go.microsoft.com/fwlink/?LinkId=222541
5491. 8957
5492. Nombre de sessions actives et de messages en attente de sessions en pourcentage du nombre maximal de sessions. http://go.microsoft.com/fwlink/?LinkId=222542
5493. 8959
5494.
5495. 8961
5496.
5497. 8963
5498.
5499. 9007
5500. Compteurs de performance ServiceModelOperation 4.0.0.0
5501. 9009
5502. Nombre d'appels à cette opération. http://go.microsoft.com/fwlink/?LinkId=222615
5503. 9011
5504. Nombre d'appels à cette opération par seconde. http://go.microsoft.com/fwlink/?LinkId=222616
5505. 9013
5506. Nombre d'appels en cours à cette opération. http://go.microsoft.com/fwlink/?LinkId=222617
5507. 9015
5508. Nombre d'appels avec des exceptions non prises en charge dans cette opération. http://go.microsoft.com/fwlink/?LinkId=222618
5509. 9017
5510. Nombre d'appels avec des exceptions non prises en charge dans cette opération par seconde. http://go.microsoft.com/fwlink/?LinkId=222619
5511. 9019
5512. Nombre d'appels à cette opération qui ont renvoyé des erreurs. http://go.microsoft.com/fwlink/?LinkId=222620
5513. 9021
5514. Nombre d'appels à cette opération qui ont renvoyé des erreurs par seconde. http://go.microsoft.com/fwlink/?LinkId=222621
5515. 9023
5516. Durée moyenne des appels à cette opération. http://go.microsoft.com/fwlink/?LinkId=222622
5517. 9025
5518. Nombre d'appels à cette opération dont la validation ou l'authentification a échoué. http://go.microsoft.com/fwlink/?LinkId=222623
5519. 9027
5520. Nombre d'appels à cette opération dont la validation ou l'authentification a échoué par seconde. http://go.microsoft.com/fwlink/?LinkId=222624
5521. 9029
5522. Nombre d'appels à cette opération avec échec d'autorisation. http://go.microsoft.com/fwlink/?LinkId=222631
5523. 9031
5524. Nombre d'appels à cette opération avec échec d'autorisation par seconde. http://go.microsoft.com/fwlink/?LinkId=222633
5525. 9033
5526. Nombre de transactions passées à cette opération. Ce compteur est incrémenté chaque fois qu'un ID de transaction est présent dans le message envoyé à l'opération. http://go.microsoft.com/fwlink/?LinkId=222634
5527. 9035
5528. Nombre de transactions passées à cette opération par seconde. Ce compteur est incrémenté chaque fois qu'un ID de transaction est présent dans le message envoyé à l'opération. http://go.microsoft.com/fwlink/?LinkId=222637
5529. 9037
5530. Durée moyenne des appels à cette opération. http://go.microsoft.com/fwlink/?LinkId=222622
5531. 8967
5532. Compteurs de performance ServiceModel pour le point de terminaison
5533. 8969
5534. Nombre d'appels à ce point de terminaison. http://go.microsoft.com/fwlink/?LinkId=222641
5535. 8971
5536. Nombre d'appels à ce point de terminaison par seconde. http://go.microsoft.com/fwlink/?LinkId=222642
5537. 8973
5538. Nombre d'appels en cours à ce point de terminaison. http://go.microsoft.com/fwlink/?LinkId=222643
5539. 8975
5540. Nombre d'appels à ce point de terminaison avec des exceptions non prises en charge. http://go.microsoft.com/fwlink/?LinkId=222644
5541. 8977
5542. Nombre d'appels à ce point de terminaison avec des exceptions non prises en charge par seconde. http://go.microsoft.com/fwlink/?LinkId=222645
5543. 8979
5544. Nombre d'appels à ce point de terminaison qui ont renvoyé des erreurs. http://go.microsoft.com/fwlink/?LinkId=222646
5545. 8981
5546. Nombre d'appels à ce point de terminaison qui ont renvoyé des erreurs par seconde. http://go.microsoft.com/fwlink/?LinkId=222647
5547. 8983
5548. Durée moyenne des appels à ce point de terminaison. http://go.microsoft.com/fwlink/?LinkId=222648
5549. 8985
5550. Nombre d'appels à ce point de terminaison dont la validation ou l'authentification a échoué. http://go.microsoft.com/fwlink/?LinkId=222656
5551. 8987
5552. Nombre d'appels à ce point de terminaison dont la validation ou l'authentification a échoué par seconde. http://go.microsoft.com/fwlink/?LinkId=222657
5553. 8989
5554. Nombre d'appels à ce point de terminaison avec échec d'autorisation. http://go.microsoft.com/fwlink/?LinkId=222653
5555. 8991
5556. Nombre d'appels à ce point de terminaison avec échec d'autorisation par seconde. http://go.microsoft.com/fwlink/?LinkId=222655
5557. 8993
5558. Nombre de sessions de messagerie fiables ayant généré des erreurs au niveau de ce point de terminaison. http://go.microsoft.com/fwlink/?LinkId=222651
5559. 8995
5560. Nombre de sessions de messagerie fiables ayant généré des erreurs au niveau de ce point de terminaison par seconde. http://go.microsoft.com/fwlink/?LinkId=222652
5561. 8997
5562. Nombre de messages de messagerie fiables déposés au niveau de ce point de terminaison. http://go.microsoft.com/fwlink/?LinkId=222649
5563. 8999
5564. Nombre de messages de messagerie fiables déposés au niveau de ce point de terminaison par seconde. http://go.microsoft.com/fwlink/?LinkId=222650
5565. 9001
5566. Nombre de transactions passées à des opérations au niveau de ce point de terminaison. Ce compteur est incrémenté chaque fois qu'un ID de transaction est présent dans le message envoyé au point de terminaison. http://go.microsoft.com/fwlink/?LinkId=222658
5567. 9003
5568. Nombre de transactions passées à des opérations au niveau de ce point de terminaison par seconde. Ce compteur est incrémenté chaque fois qu'un ID de transaction est présent dans le message envoyé au point de terminaison. http://go.microsoft.com/fwlink/?LinkId=222659
5569. 9005
5570. Durée moyenne des appels à ce point de terminaison. http://go.microsoft.com/fwlink/?LinkId=222648
5571. 4681
5572. Ensemble des compteurs de file d’attente des requêtes
5573. 4683
5574. Nombre de requêtes dans la file d’attente
5575. 4685
5576. Antériorité de la requête la plus ancienne de la file d’attente
5577. 4687
5578. Taux auquel les requêtes arrivent dans la file d’attente
5579. 4689
5580. Taux auquel les requêtes sont rejetées de la file d’attente
5581. 4691
5582. Nombre total de requêtes rejetées de la file d’attente
5583. 4693
5584. Taux des accès cache pour la file d’attente
5585. 4661
5586. Ensemble de compteurs d’URL spécifiques au groupe
5587. 4663
5588. Taux de données envoyées par le service HTTP pour ce site
5589. 4665
5590. Taux de données reçues par le service HTTP pour ce site
5591. 4667
5592. Taux d’octets transférés (envoyés et reçus) par le service HTTP pour ce site
5593. 4669
5594. Nombre de connexions actuellement établies pour ce site
5595. 4671
5596. Nombre maximal de connexions simultanées établies pour ce site
5597. 4673
5598. Taux auquel les tentatives de connexion sont effectuées pour ce site
5599. 4675
5600. Taux auquel les demandes de méthode GET sont effectuées pour ce site
5601. 4677
5602. Taux auquel les demandes de méthode HEAD sont effectuées pour ce site
5603. 4679
5604. Nombre total de requêtes HTTP effectuées pour ce site
5605. 4647
5606. Ensemble de compteurs de service HTTP
5607. 4649
5608. Nombre total d’URI actuellement mis en cache par le noyau
5609. 4651
5610. Nombre total d’URI ajoutés au noyau depuis le démarrage du service
5611. 4653
5612. Nombre total de recherches abouties dans la mémoire cache URI du noyau
5613. 4655
5614. Nombre total de recherches infructueuses dans la mémoire cache URI du noyau
5615. 4657
5616. Nombre total de vidages du cache URI (complets ou partiels) depuis le démarrage du service
5617. 4659
5618. Nombre total d’URI supprimés du cache URI du noyau depuis le démarrage du service
5619. 4633
5620. Compteurs de mesure des performances de Netlogon.
5621. 4635
5622. Nombre de threads attendant l'acquisition du sémaphore.
5623. 4637
5624. Nombre de threads actuellement détenteurs du sémaphore.
5625. 4639
5626. 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).
5627. 4641
5628. 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).
5629. 4643
5630. Durée moyenne de retenue du sémaphore lors du dernier échantillonnage.
5631. 4645
5632. La valeur de base utilisée pour calculer le temps moyen de retenue du sémaphore.
5633. 5937
5634. Affiche des informations sur l’utilisation et la violation des quotas pour les processus de la Gestion des services Web.
5635. 5939
5636. Affiche le nombre de demandes approuvées et rejetées par seconde provenant d’utilisateurs autorisés.
5637. 5941
5638. Affiche le nombre de violations de quota d’utilisateur.
5639. 5943
5640. Affiche le nombre de demandes ayant fait l’objet d’une limitation du système.
5641. 5945
5642. Affiche le nombre actuel de shells actifs pour tous les utilisateurs.
5643. 5947
5644. Affiche le nombre actuel d’opérations actives pour tous les utilisateurs.
5645. 5949
5646. Affiche le nombre actuel d’utilisateurs actifs autorisés.
5647. 3419
5648. Compteurs de performance du composant des services de base de module de plateforme sécurisée.
5649. 3421
5650. Le nombre de contextes TBS qui sont actuellement actifs.
5651. 3423
5652. Le nombre de ressources qui sont actuellement gérées par le TBS.
5653. " (REG_MULTI_SZ)
5654.
5655. [HKLM\Software\Skype\Installer]
5656. "BINGSRCHFF"="255" (REG_DWORD)
5657.
5658. [HKLM\Software\Skype\Installer]
5659. "BINGSRCHIE"="255" (REG_DWORD)
5660.
5661. [HKLM\Software\Skype\Installer]
5662. "BINGSRCHGC"="255" (REG_DWORD)
5663.
5664. [HKLM\System\ControlSet001\Services\NlaSvc\Parameters\Internet]
5665. "EnableActiveProbing"="1" (REG_DWORD)
5666.
5667. [HKLM\System\ControlSet010\Services\NlaSvc\Parameters\Internet]
5668. "EnableActiveProbing"="1" (REG_DWORD)
5669.
5670. [HKLM\System\CurrentControlSet\Services\NlaSvc\Parameters\Internet]
5671. "EnableActiveProbing"="1" (REG_DWORD)
5672.
5673. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5674. "DisplayName"="Bing" (REG_SZ)
5675.
5676. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5677. "URL"="http://www.bing.com/search?FORM=SK2MDF&PC=SK2M&q={searchTerms}&src=IE-SearchBox" (REG_SZ)
5678.
5679. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5680. "SuggestionsURL"="http://www.bing.com/as/api/qsml?query={searchTerms}&market={Language}&FORM=SK2MDF&PC=SK2M&&maxwidth={ie:maxWidth}&rowheight={ie:rowHeight}§ionHeight={ie:sectionHeight}" (REG_SZ)
5681.
5682. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5683. "FaviconURL"="http://www.bing.com/favicon.ico" (REG_SZ)
5684.
5685. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5686. "NTURL"="http://www.bing.com/search?FORM=UWDFNU&PC=SK2M&q={searchTerms}&src=IE-TopResult" (REG_SZ)
5687.
5688. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5689. "NTTopResultURL"="http://www.bing.com/search?FORM=UWDFNT&PC=SK2M&q={searchTerms}&src=IE-TopResult" (REG_SZ)
5690.
5691. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5692. "NTSuggestionsURL"="http://www.bing.com/as/api/qsml?query={searchTerms}&market={Language}&FORM=UWDFNS&PC=SK2M&&maxwidth={ie:maxWidth}&rowheight={ie:rowHeight}&sectionHeight={ie:sectionHeight}" (REG_SZ)
5693.
5694. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5695. "TopResultURL"="http://www.bing.com/search?FORM=UWDFTU&PC=SK2M&q={searchTerms}&src=IE-TopResult" (REG_SZ)
5696.
5697. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5698. "TopResultURLFallback"="http://www.bing.com/search?FORM=UWDFTF&PC=SK2M&q={searchTerms}&src=IE-TopResult" (REG_SZ)
5699.
5700. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5701. "FaviconURLFallback"="http://www.bing.com/favicon.ico" (REG_SZ)
5702.
5703. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}]
5704. "SuggestionsURLFallback"="http://www.bing.com/as/api/qsml?query={searchTerms}&market={Language}&FORM=UWDFSF&PC=SK2M&&maxwidth={ie:maxWidth}&rowheight={ie:rowHeight}&sectionHeight={ie:sectionHeight}" (REG_SZ)
5705.
5706. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\MediaPlayer\Services\Bing]
5707. DA: 03/03/2019 10:58:42
5708.
5709. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\MediaPlayer\Subscriptions]
5710. "ActiveService"="Service=Bing&userlocale=40c&GEOID=54&locale=40c" (REG_SZ)
5711.
5712. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\MediaPlayer\Subscriptions]
5713. "ActiveServiceName"="Bing" (REG_SZ)
5714.
5715. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\Windows\CurrentVersion\Run]
5716. "BingSvc"="C:\Users\SAMSUNG\AppData\Local\Microsoft\BingSvc\BingSvc.exe" (REG_SZ)
5717.
5718. [HKU\S-1-5-21-1228387082-1587413325-2831801477-1003\Software\Microsoft\BingSvc]
5719. DA: 03/03/2019 11:03:10
5720.
5721. =========================
5722.
5723. Fin à: 13:00:52 le 04/03/2019
5724. 635877 Éléments analysés
5725.
5726. =========================
5727. E.O.F