cjoint

Publicité


Publicité

Format du document : text/plain

Prévisualisation

1. ========================= SEAF 1.0.1.0 - C_XX
2.
3. Commencé à: 21:18:22 le 18/08/2016
4.
5. Valeur(s) recherchée(s):
6. Crack
7.
8. Légende: TC => Date de création, TM => Date de modification, DA => Dernier accès
9.
10. (!) --- Calcul du Hash "MD5"
11. (!) --- Informations supplémentaires
12. (!) --- Recherche registre
13.
14. ====== Fichier(s) ======
15.
16.
17. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\client\game\common\sounds\honey_tile_lid_soft_crack.wav" [ ARCHIVE | 33 Ko ]
18. TC: 17/06/2016,22:17:03 | TM: 17/06/2016,22:22:08 | DA: 17/06/2016,22:17:03
19.
20. Hash MD5: 9067CF3FFD2A3369C16447873091F381
21.
22.
23. =========================
24.
25.
26. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\diorama\diorama06\episode16\models\crack_shadow.ffm" [ ARCHIVE | 5 Ko ]
27. TC: 17/06/2016,22:17:07 | TM: 17/06/2016,22:26:36 | DA: 17/06/2016,22:17:07
28.
29. Hash MD5: 61AE39B6274D8755866D8C2778227B4B
30.
31.
32. =========================
33.
34.
35. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\models\honey\honey_tile_crack.ffa" [ ARCHIVE | 36 Ko ]
36. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:29:56 | DA: 17/06/2016,22:17:09
37.
38. Hash MD5: 562F5EA239DA3F67F3AA181D7CA9BEE0
39.
40.
41. =========================
42.
43.
44. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\models\honey\honey_tile_cracked.ffm" [ ARCHIVE | 35 Ko ]
45. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:29:56 | DA: 17/06/2016,22:17:09
46.
47. Hash MD5: 151AC2C4CAF0B4EEA7F3F79BE303C844
48.
49.
50. =========================
51.
52.
53. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\tex\chain_blocker\chain_cracked_tex_a.png" [ ARCHIVE | 2 Ko ]
54. TC: 22/06/2016,15:01:55 | TM: 22/06/2016,15:02:18 | DA: 22/06/2016,15:01:55
55.
56. Hash MD5: 26FDBD9AE862D2C18D68C08E0069C5A4
57.
58.
59. =========================
60.
61.
62. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\tex\chain_blocker\chain_cracked_tex_rgb.jpg" [ ARCHIVE | 4 Ko ]
63. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:32:59 | DA: 17/06/2016,22:17:09
64.
65. Hash MD5: 040D4B905877172FB6CD4E7E0102A97D
66.
67.
68. =========================
69.
70.
71. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\tex\chocolate\choko_cracked_normal.jpg" [ ARCHIVE | 13 Ko ]
72. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:32:59 | DA: 17/06/2016,22:17:09
73.
74. Hash MD5: 4D94C30E567F79AEE032AA67EAF3B9FD
75.
76.
77. =========================
78.
79.
80. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\tex\chocolate\choko_cracked_tex.jpg" [ ARCHIVE | 8 Ko ]
81. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:32:59 | DA: 17/06/2016,22:17:09
82.
83. Hash MD5: A5F336EF1003E87FDFB093FC63BA1945
84.
85.
86. =========================
87.
88.
89. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\tex\white_chocolate\white_choco_layertwo_cracked_tex.jpg" [ ARCHIVE | 6 Ko ]
90. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:32:59 | DA: 17/06/2016,22:17:09
91.
92. Hash MD5: 794C181A673ABED299B5DFC6D0ABEBCF
93.
94.
95. =========================
96.
97.
98. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\tex\white_chocolate\white_choko_cracked_normal.jpg" [ ARCHIVE | 15 Ko ]
99. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:32:59 | DA: 17/06/2016,22:17:09
100.
101. Hash MD5: F96A5E950BB46CF886DF2D44B6E32B51
102.
103.
104. =========================
105.
106.
107. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\tex\white_chocolate\white_choko_cracked_tex.jpg" [ ARCHIVE | 7 Ko ]
108. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:32:59 | DA: 17/06/2016,22:17:09
109.
110. Hash MD5: E0290EF08A5144E0093EFB1EBA4456A3
111.
112.
113. =========================
114.
115.
116. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\timelines\mode\giant_bears\ice_crack.xml" [ ARCHIVE | 307 o ]
117. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:30:36 | DA: 17/06/2016,22:17:09
118.
119. Hash MD5: BA57494013BADA580C0D5563B1F7E6FB
120.
121.
122. =========================
123.
124.
125. "C:\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.68.500.0_x86__kgqvnymyfvs32\res_output\shared\game\common\timelines\mode\giant_bears\ice_crack_scene.xml" [ ARCHIVE | 182 o ]
126. TC: 17/06/2016,22:17:09 | TM: 17/06/2016,22:30:37 | DA: 17/06/2016,22:17:09
127.
128. Hash MD5: D821A4A9A4832DAECD7432A64BB10802
129.
130.
131. =========================
132.
133.
134. "C:\Program Files (x86)\Bethesda Softworks\Dishonored - Game of the Year Edition\DishonoredGame\DLC\PCConsole\DLC07\UI_Tuto_CrackedCharms_SF.upk" [ ARCHIVE | 59 Ko ]
135. TC: 20/07/2016,18:23:51 | TM: 03/01/2014,19:17:14 | DA: 20/07/2016,18:23:51
136.
137. Hash MD5: 980E438A867728D7F13F337AF605EAAC
138.
139.
140. =========================
141.
142.
143. "C:\Program Files (x86)\Bethesda Softworks\Dishonored - Game of the Year Edition\DishonoredGame\Localization\CZE\DLC07_Pckp_CrackedBoneCharms.cze" [ ARCHIVE | 244 o ]
144. TC: 20/07/2016,18:23:51 | TM: 03/01/2014,19:11:48 | DA: 20/07/2016,18:23:51
145.
146. Hash MD5: BCF157A79E07E7A48F52058CC92DE356
147.
148.
149. =========================
150.
151.
152. "C:\Program Files (x86)\Bethesda Softworks\Dishonored - Game of the Year Edition\DishonoredGame\Localization\FRA\DLC07_Pckp_CrackedBoneCharms.fra" [ ARCHIVE | 238 o ]
153. TC: 14/08/2013,01:12:56 | TM: 06/08/2013,23:49:48 | DA: 14/08/2013,01:12:56
154.
155. Hash MD5: E0D4A08C1900AD415011C8CBADC88F3B
156.
157.
158. =========================
159.
160.
161. "C:\Program Files (x86)\Bethesda Softworks\Dishonored - Game of the Year Edition\DishonoredGame\Localization\HUN\DLC07_Pckp_CrackedBoneCharms.hun" [ ARCHIVE | 250 o ]
162. TC: 20/07/2016,18:23:53 | TM: 03/01/2014,19:09:36 | DA: 20/07/2016,18:23:53
163.
164. Hash MD5: F4F2ED6B8C6516DF6BB7925A7B5DEC00
165.
166.
167. =========================
168.
169.
170. "C:\Program Files (x86)\Bethesda Softworks\Dishonored - Game of the Year Edition\DishonoredGame\Localization\INT\DLC07_Pckp_CrackedBoneCharms.int" [ ARCHIVE | 238 o ]
171. TC: 20/07/2016,18:23:54 | TM: 06/08/2013,23:49:48 | DA: 14/08/2013,01:13:09
172.
173. Hash MD5: E0D4A08C1900AD415011C8CBADC88F3B
174.
175.
176. =========================
177.
178.
179. "C:\Program Files (x86)\Bethesda Softworks\Dishonored - Game of the Year Edition\DishonoredGame\Localization\POL\DLC07_Pckp_CrackedBoneCharms.pol" [ ARCHIVE | 242 o ]
180. TC: 20/07/2016,18:23:57 | TM: 03/01/2014,19:11:50 | DA: 20/07/2016,18:23:57
181.
182. Hash MD5: 180E730AC768EAD86B9FBE5F799FE754
183.
184.
185. =========================
186.
187.
188. "C:\Program Files (x86)\Bethesda Softworks\Dishonored - Game of the Year Edition\DishonoredGame\Localization\RUS\DLC07_Pckp_CrackedBoneCharms.rus" [ ARCHIVE | 254 o ]
189. TC: 20/07/2016,18:24:01 | TM: 03/01/2014,19:10:12 | DA: 20/07/2016,18:24:01
190.
191. Hash MD5: C8A64316280D3A29E9F8407F17A8F41A
192.
193.
194. =========================
195.
196.
197. "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\materials\sprites\ptrunners\trails\crackedbeam.vmt" [ ARCHIVE | 128 o ]
198. TC: 13/08/2016,19:34:32 | TM: 13/08/2016,19:34:32 | DA: 13/08/2016,19:34:32
199.
200. Hash MD5: 6671E25B8EEED0DD1E01074BD43EA0A2
201.
202.
203. =========================
204.
205.
206. "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\materials\sprites\ptrunners\trails\crackedbeam.vtf" [ ARCHIVE | 22 Ko ]
207. TC: 13/08/2016,19:34:32 | TM: 13/08/2016,19:34:32 | DA: 13/08/2016,19:34:32
208.
209. Hash MD5: D9AF5303DC13F63F341DC8744C7FD7DC
210.
211.
212. =========================
213.
214.
215. "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\materials\sprites\store\trails\crackedbeam.vmt" [ ARCHIVE | 124 o ]
216. TC: 01/07/2016,01:38:33 | TM: 01/07/2016,01:38:33 | DA: 01/07/2016,01:38:33
217.
218. Hash MD5: D453BF02C33B2EA4DDAE4C26A2B83C02
219.
220.
221. =========================
222.
223.
224. "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\materials\sprites\store\trails\crackedbeam.vtf" [ ARCHIVE | 22 Ko ]
225. TC: 01/07/2016,01:38:33 | TM: 01/07/2016,01:38:33 | DA: 01/07/2016,01:38:33
226.
227. Hash MD5: D9AF5303DC13F63F341DC8744C7FD7DC
228.
229.
230. =========================
231.
232.
233. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\addons\CSS_Content_Addon-Jan2015\materials\concrete\prodwllecracked.vmt" [ ARCHIVE | 100 o ]
234. TC: 21/06/2016,17:22:12 | TM: 07/01/2015,08:02:44 | DA: 21/06/2016,17:22:12
235.
236. Hash MD5: 4406B49F72775D8D4606CD50E099ABAF
237.
238.
239. =========================
240.
241.
242. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\addons\CSS_Content_Addon-Jan2015\materials\concrete\prodwllecracked.vtf" [ ARCHIVE | 175 Ko ]
243. TC: 21/06/2016,17:22:12 | TM: 07/01/2015,08:02:44 | DA: 21/06/2016,17:22:12
244.
245. Hash MD5: 6D51B4B5A0469912FDD0057DE1CA3DC6
246.
247.
248. =========================
249.
250.
251. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\addons\keypad_tool_and_cracker_with_wire_support_108424005.gma" [ ARCHIVE | 44 Ko ]
252. TC: 05/07/2016,17:35:06 | TM: 05/07/2016,17:35:06 | DA: 05/07/2016,17:35:06
253.
254. Hash MD5: FB049F379DFE05D03A382AA6F682020D
255.
256.
257. =========================
258.
259.
260. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\addons\nogitsus_keypad_cracker_667376411.gma" [ ARCHIVE | 15 Ko ]
261. TC: 05/07/2016,17:40:45 | TM: 05/07/2016,17:40:45 | DA: 05/07/2016,17:40:45
262.
263. Hash MD5: 34B369DB8E7BF21C4CFCC11E690BB735
264.
265.
266. =========================
267.
268.
269. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\materials\models\cloud\xmastree\bluecracker.vmt" [ ARCHIVE | 108 o ]
270. TC: 21/06/2016,17:44:54 | TM: 21/06/2016,17:44:54 | DA: 21/06/2016,17:44:54
271.
272. Hash MD5: 331F79469B7D9CDCFD4F083372B89940
273.
274.
275. =========================
276.
277.
278. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\materials\models\cloud\xmastree\bluecracker.vtf" [ ARCHIVE | 22 Ko ]
279. TC: 21/06/2016,17:44:54 | TM: 21/06/2016,17:44:54 | DA: 21/06/2016,17:44:54
280.
281. Hash MD5: BB92E05249BD04EDB2AC19B73E30F743
282.
283.
284. =========================
285.
286.
287. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\materials\models\cloud\xmastree\goldcracker.vmt" [ ARCHIVE | 108 o ]
288. TC: 21/06/2016,17:44:55 | TM: 21/06/2016,17:44:55 | DA: 21/06/2016,17:44:55
289.
290. Hash MD5: EC72B064E0860031611145C4DFE3B6AF
291.
292.
293. =========================
294.
295.
296. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\materials\models\cloud\xmastree\goldcracker.vtf" [ ARCHIVE | 22 Ko ]
297. TC: 21/06/2016,17:44:55 | TM: 21/06/2016,17:44:55 | DA: 21/06/2016,17:44:55
298.
299. Hash MD5: BEA3741F76E8BC636B74910D6413B76C
300.
301.
302. =========================
303.
304.
305. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\materials\models\cloud\xmastree\greencracker.vmt" [ ARCHIVE | 109 o ]
306. TC: 21/06/2016,17:44:55 | TM: 21/06/2016,17:44:55 | DA: 21/06/2016,17:44:55
307.
308. Hash MD5: 326AE741E61A082F4B768F30C5AD64A1
309.
310.
311. =========================
312.
313.
314. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\materials\models\cloud\xmastree\greencracker.vtf" [ ARCHIVE | 22 Ko ]
315. TC: 21/06/2016,17:44:55 | TM: 21/06/2016,17:44:55 | DA: 21/06/2016,17:44:55
316.
317. Hash MD5: 8441C8D7A4C6328A93803F53BF92822A
318.
319.
320. =========================
321.
322.
323. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\materials\models\cloud\xmastree\redcracker.vmt" [ ARCHIVE | 107 o ]
324. TC: 21/06/2016,17:44:57 | TM: 21/06/2016,17:44:57 | DA: 21/06/2016,17:44:57
325.
326. Hash MD5: 63945347A3534A81452D29063B3717B4
327.
328.
329. =========================
330.
331.
332. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\materials\models\cloud\xmastree\redcracker.vtf" [ ARCHIVE | 22 Ko ]
333. TC: 21/06/2016,17:44:57 | TM: 21/06/2016,17:44:57 | DA: 21/06/2016,17:44:57
334.
335. Hash MD5: 538CDA83119C950C8F64A91085754AE1
336.
337.
338. =========================
339.
340.
341. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker.dx80.vtx" [ ARCHIVE | 3 Ko ]
342. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
343.
344. Hash MD5: 44FE2187E08DE0EDD72948FD7470149C
345.
346.
347. =========================
348.
349.
350. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker.dx90.vtx" [ ARCHIVE | 3 Ko ]
351. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
352.
353. Hash MD5: BC880652DA3FEB9B2A8BA9B940D1E2AE
354.
355.
356. =========================
357.
358.
359. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker.mdl" [ ARCHIVE | 2 Ko ]
360. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
361.
362. Hash MD5: 5B9BCEF6793FD928753F23D5A2D6BF89
363.
364.
365. =========================
366.
367.
368. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker.phy" [ ARCHIVE | 1 Ko ]
369. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
370.
371. Hash MD5: 7E4E0CF4911DDEB63D6B6BF12D9A6227
372.
373.
374. =========================
375.
376.
377. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker.vvd" [ ARCHIVE | 11 Ko ]
378. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
379.
380. Hash MD5: 86E61CB71C25F75A6E2C88446BA7A752
381.
382.
383. =========================
384.
385.
386. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue.dx80.vtx" [ ARCHIVE | 3 Ko ]
387. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
388.
389. Hash MD5: 18D7F29C1157C3FEACA20D1408F09464
390.
391.
392. =========================
393.
394.
395. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue.dx90.vtx" [ ARCHIVE | 3 Ko ]
396. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
397.
398. Hash MD5: 4699DB5958B441D31407152770D083B0
399.
400.
401. =========================
402.
403.
404. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue.mdl" [ ARCHIVE | 1 Ko ]
405. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
406.
407. Hash MD5: DE96709C13244C40557FEDCB6C3B9F5A
408.
409.
410. =========================
411.
412.
413. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue.phy" [ ARCHIVE | 1 Ko ]
414. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
415.
416. Hash MD5: 803E5A4A441A35E12B924FAECE961A79
417.
418.
419. =========================
420.
421.
422. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue.vvd" [ ARCHIVE | 11 Ko ]
423. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
424.
425. Hash MD5: 96BAFED1EA62D43997000007FCB05DB1
426.
427.
428. =========================
429.
430.
431. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p1.dx80.vtx" [ ARCHIVE | 2 Ko ]
432. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
433.
434. Hash MD5: 0D8E8AD5267C9930D25E728CA34D8340
435.
436.
437. =========================
438.
439.
440. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p1.dx90.vtx" [ ARCHIVE | 2 Ko ]
441. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
442.
443. Hash MD5: 11FD7BC9F37BF2B0A53CA22013B0054B
444.
445.
446. =========================
447.
448.
449. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p1.mdl" [ ARCHIVE | 1 Ko ]
450. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
451.
452. Hash MD5: CF6549721AF0015175032923B736489C
453.
454.
455. =========================
456.
457.
458. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p1.phy" [ ARCHIVE | 1 Ko ]
459. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
460.
461. Hash MD5: 550D5673210191DA0B656AB935578B99
462.
463.
464. =========================
465.
466.
467. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p1.vvd" [ ARCHIVE | 10 Ko ]
468. TC: 21/06/2016,17:44:34 | TM: 21/06/2016,17:44:34 | DA: 21/06/2016,17:44:34
469.
470. Hash MD5: 259C1FF93432A6D02853F1049CD9356F
471.
472.
473. =========================
474.
475.
476. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p2.dx80.vtx" [ ARCHIVE | 1 Ko ]
477. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
478.
479. Hash MD5: 8A8D4F936FBB84F7909E3133DC035237
480.
481.
482. =========================
483.
484.
485. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p2.dx90.vtx" [ ARCHIVE | 1 Ko ]
486. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
487.
488. Hash MD5: 0D001FCFC50A0E4544FC7021BC6FF285
489.
490.
491. =========================
492.
493.
494. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p2.mdl" [ ARCHIVE | 1 Ko ]
495. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
496.
497. Hash MD5: 53C07A63A57AC500EA6BA45936ED5EE9
498.
499.
500. =========================
501.
502.
503. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p2.phy" [ ARCHIVE | 1 Ko ]
504. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
505.
506. Hash MD5: BF3531A47E6FB4E811D193EA4E1081D8
507.
508.
509. =========================
510.
511.
512. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_blue_p2.vvd" [ ARCHIVE | 4 Ko ]
513. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
514.
515. Hash MD5: 59207E52F4D1849A005E3F226AA2951A
516.
517.
518. =========================
519.
520.
521. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold.dx80.vtx" [ ARCHIVE | 3 Ko ]
522. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
523.
524. Hash MD5: 5B381915954DE3F5325CA0CE43CA8DBA
525.
526.
527. =========================
528.
529.
530. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold.dx90.vtx" [ ARCHIVE | 3 Ko ]
531. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
532.
533. Hash MD5: 31DD60612B50ACC0919250E91EA35B6D
534.
535.
536. =========================
537.
538.
539. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold.mdl" [ ARCHIVE | 1 Ko ]
540. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
541.
542. Hash MD5: 58C736BF61CE3AE13C4D68011116DCCE
543.
544.
545. =========================
546.
547.
548. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold.phy" [ ARCHIVE | 1 Ko ]
549. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
550.
551. Hash MD5: 950C6805A3ED4FF2178871CA09F63976
552.
553.
554. =========================
555.
556.
557. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold.vvd" [ ARCHIVE | 11 Ko ]
558. TC: 21/06/2016,17:44:35 | TM: 21/06/2016,17:44:35 | DA: 21/06/2016,17:44:35
559.
560. Hash MD5: E2C13A02496A3AE0546C97AE9821A6EC
561.
562.
563. =========================
564.
565.
566. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p1.dx80.vtx" [ ARCHIVE | 2 Ko ]
567. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
568.
569. Hash MD5: B3D30C58D19AA286BCF1CB76AA3E4708
570.
571.
572. =========================
573.
574.
575. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p1.dx90.vtx" [ ARCHIVE | 2 Ko ]
576. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
577.
578. Hash MD5: 45F31F0CA1B9DF33A87066927E26298E
579.
580.
581. =========================
582.
583.
584. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p1.mdl" [ ARCHIVE | 1 Ko ]
585. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
586.
587. Hash MD5: 70B85DF5F7F731D1A383A4165106597F
588.
589.
590. =========================
591.
592.
593. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p1.phy" [ ARCHIVE | 1 Ko ]
594. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
595.
596. Hash MD5: FF5FCB5E7C6ACA236F2BC03E3BAE0B41
597.
598.
599. =========================
600.
601.
602. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p1.vvd" [ ARCHIVE | 10 Ko ]
603. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
604.
605. Hash MD5: 7B5C310CECB060972791697700EB522C
606.
607.
608. =========================
609.
610.
611. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p2.dx80.vtx" [ ARCHIVE | 1 Ko ]
612. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
613.
614. Hash MD5: D6E9A8BDF7103AC8E0BA9437F0CED9FD
615.
616.
617. =========================
618.
619.
620. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p2.dx90.vtx" [ ARCHIVE | 1 Ko ]
621. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
622.
623. Hash MD5: 25017A50E185C88405D65AD6E91B85E6
624.
625.
626. =========================
627.
628.
629. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p2.mdl" [ ARCHIVE | 1 Ko ]
630. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
631.
632. Hash MD5: 58EBDA610CB0B4FF8C094E11A953AC20
633.
634.
635. =========================
636.
637.
638. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p2.phy" [ ARCHIVE | 1 Ko ]
639. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
640.
641. Hash MD5: 7CD94135BC8BE5DB8AA050A843FF59A7
642.
643.
644. =========================
645.
646.
647. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_gold_p2.vvd" [ ARCHIVE | 4 Ko ]
648. TC: 21/06/2016,17:44:36 | TM: 21/06/2016,17:44:36 | DA: 21/06/2016,17:44:36
649.
650. Hash MD5: CC8E9961D6E114346050088B5680FD01
651.
652.
653. =========================
654.
655.
656. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green.dx80.vtx" [ ARCHIVE | 3 Ko ]
657. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
658.
659. Hash MD5: 64D425C29DAC98B971F6D573C8F9082E
660.
661.
662. =========================
663.
664.
665. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green.dx90.vtx" [ ARCHIVE | 3 Ko ]
666. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
667.
668. Hash MD5: CB708B4F7B99BC553955CA86F35E4F0D
669.
670.
671. =========================
672.
673.
674. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green.mdl" [ ARCHIVE | 1 Ko ]
675. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
676.
677. Hash MD5: 4C7E3DEB10FF229AD0EC854DA7FCF493
678.
679.
680. =========================
681.
682.
683. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green.phy" [ ARCHIVE | 1 Ko ]
684. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
685.
686. Hash MD5: D920AD70362AFE95688DC7557A67EB19
687.
688.
689. =========================
690.
691.
692. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green.vvd" [ ARCHIVE | 11 Ko ]
693. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
694.
695. Hash MD5: DF2D471A5533D4E09D1DB03FC9907A78
696.
697.
698. =========================
699.
700.
701. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p1.dx80.vtx" [ ARCHIVE | 2 Ko ]
702. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
703.
704. Hash MD5: 0081058A56D70111A8CB977B29286409
705.
706.
707. =========================
708.
709.
710. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p1.dx90.vtx" [ ARCHIVE | 2 Ko ]
711. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
712.
713. Hash MD5: 54275818A8F7D950E96B795B17243298
714.
715.
716. =========================
717.
718.
719. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p1.mdl" [ ARCHIVE | 1 Ko ]
720. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
721.
722. Hash MD5: CF4351373FB088EFB1C30015B8638680
723.
724.
725. =========================
726.
727.
728. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p1.phy" [ ARCHIVE | 1 Ko ]
729. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
730.
731. Hash MD5: 9F2AE878F8C17F71379B8044680B375D
732.
733.
734. =========================
735.
736.
737. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p1.vvd" [ ARCHIVE | 10 Ko ]
738. TC: 21/06/2016,17:44:37 | TM: 21/06/2016,17:44:37 | DA: 21/06/2016,17:44:37
739.
740. Hash MD5: 1CD77CCFF9F6D25FFEDF3BD14CEB2AE6
741.
742.
743. =========================
744.
745.
746. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p2.dx80.vtx" [ ARCHIVE | 1 Ko ]
747. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
748.
749. Hash MD5: 6C7D52BAA27D2253D8A8ECCCDA8EAB4A
750.
751.
752. =========================
753.
754.
755. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p2.dx90.vtx" [ ARCHIVE | 1 Ko ]
756. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
757.
758. Hash MD5: E75DA101C89963C5757C3BB551BD4BDB
759.
760.
761. =========================
762.
763.
764. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p2.mdl" [ ARCHIVE | 1 Ko ]
765. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
766.
767. Hash MD5: 180A6E052A14748592549BF6E0DB7330
768.
769.
770. =========================
771.
772.
773. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p2.phy" [ ARCHIVE | 1 Ko ]
774. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
775.
776. Hash MD5: 20B827C4FBDB7B7FD3446E352E645FD2
777.
778.
779. =========================
780.
781.
782. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_green_p2.vvd" [ ARCHIVE | 4 Ko ]
783. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
784.
785. Hash MD5: 8F9F069A8224B7594C7FA884EBE27429
786.
787.
788. =========================
789.
790.
791. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red.dx80.vtx" [ ARCHIVE | 3 Ko ]
792. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
793.
794. Hash MD5: A028C3361EC5E9D82F3CEACCEE1775D3
795.
796.
797. =========================
798.
799.
800. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red.dx90.vtx" [ ARCHIVE | 3 Ko ]
801. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
802.
803. Hash MD5: C7D1CECDEF1F1C6C4A733FAC44F570B1
804.
805.
806. =========================
807.
808.
809. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red.mdl" [ ARCHIVE | 1 Ko ]
810. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
811.
812. Hash MD5: A5BDE90377B23EDA69055B671FCF93B5
813.
814.
815. =========================
816.
817.
818. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red.phy" [ ARCHIVE | 1 Ko ]
819. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
820.
821. Hash MD5: E7C3F38C99880E07DD3E27C7F18EC925
822.
823.
824. =========================
825.
826.
827. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red.vvd" [ ARCHIVE | 11 Ko ]
828. TC: 21/06/2016,17:44:38 | TM: 21/06/2016,17:44:38 | DA: 21/06/2016,17:44:38
829.
830. Hash MD5: 67F7CC4C41A13F296137C96E5C4545C0
831.
832.
833. =========================
834.
835.
836. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p1.dx80.vtx" [ ARCHIVE | 2 Ko ]
837. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
838.
839. Hash MD5: 7D873FA9D4EB01CB5EF0A179D43D0DE0
840.
841.
842. =========================
843.
844.
845. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p1.dx90.vtx" [ ARCHIVE | 2 Ko ]
846. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
847.
848. Hash MD5: EA7F63DAC9F02701E4F36F8F2B399B33
849.
850.
851. =========================
852.
853.
854. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p1.mdl" [ ARCHIVE | 1 Ko ]
855. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
856.
857. Hash MD5: 091EFFBA451E73F198CF04E58D079B33
858.
859.
860. =========================
861.
862.
863. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p1.phy" [ ARCHIVE | 1 Ko ]
864. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
865.
866. Hash MD5: 9BFE7E969DFC7757044B641EE0175CB7
867.
868.
869. =========================
870.
871.
872. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p1.vvd" [ ARCHIVE | 10 Ko ]
873. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
874.
875. Hash MD5: B607FC55EE23999BDFEF27953329F8A7
876.
877.
878. =========================
879.
880.
881. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p2.dx80.vtx" [ ARCHIVE | 1 Ko ]
882. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
883.
884. Hash MD5: E09A22F79E7F7FB238D8F914390A2D69
885.
886.
887. =========================
888.
889.
890. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p2.dx90.vtx" [ ARCHIVE | 1 Ko ]
891. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
892.
893. Hash MD5: D66F120574309C21F85BC6E7497646BA
894.
895.
896. =========================
897.
898.
899. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p2.mdl" [ ARCHIVE | 1 Ko ]
900. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
901.
902. Hash MD5: 96F17596D4E20CF77360A49834AFE63F
903.
904.
905. =========================
906.
907.
908. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p2.phy" [ ARCHIVE | 1 Ko ]
909. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
910.
911. Hash MD5: CC3D08A25DFC8B03B6F343B668332BB2
912.
913.
914. =========================
915.
916.
917. "C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\download\models\cloud\kn_cracker_red_p2.vvd" [ ARCHIVE | 4 Ko ]
918. TC: 21/06/2016,17:44:39 | TM: 21/06/2016,17:44:39 | DA: 21/06/2016,17:44:39
919.
920. Hash MD5: 3466299E4AF3294C2A33063B310D1702
921.
922.
923. =========================
924.
925.
926. "C:\Users\Marwan Louraichia\AppData\Roaming\Microsoft\Windows\Recent\Crack By FlashShzer.lnk" [ ARCHIVE | 730 o ]
927. TC: 16/08/2016,19:06:53 | TM: 16/08/2016,19:06:53 | DA: 16/08/2016,19:06:53
928.
929. Hash MD5: E16DA228103DB18794069F7A2D020EA0
930.
931.
932. =========================
933.
934.
935. "C:\Users\Marwan Louraichia\Downloads\1300 Photoshop Brushes\missm-crackedstained\missm-crackedstained.abr" [ ARCHIVE | 219 Ko ]
936. TC: 23/06/2016,17:00:49 | TM: 26/01/2004,08:36:38 | DA: 23/06/2016,17:00:49
937.
938. Hash MD5: 20364330480056460F41E4BFE4E1F0A5
939.
940.
941. =========================
942.
943.
944. "C:\Users\Marwan Louraichia\Downloads\1300 Photoshop Brushes\vered_cracked_wall_ps7_brush.abr" [ ARCHIVE | 5165 Ko ]
945. TC: 23/06/2016,17:00:51 | TM: 08/06/2003,01:48:52 | DA: 23/06/2016,17:00:51
946.
947. Hash MD5: 0C64DB760A749D561311B468B1DE7FB6
948.
949.
950. =========================
951.
952.
953. "C:\Users\Marwan Louraichia\Downloads\1300 Photoshop Brushes\winter\crack _ Brushes.abr" [ ARCHIVE | 55 Ko ]
954. TC: 23/06/2016,17:00:56 | TM: 05/12/2003,12:24:10 | DA: 23/06/2016,17:00:56
955.
956. Hash MD5: D563C6D884389EB829A232B4B010B8CF
957.
958.
959. =========================
960.
961.
962. "C:\Users\Marwan Louraichia\Downloads\After Effect CS6 by Viiperza\App\Ae\Support Files\Presets\Image - Special Effects\Cracked Tiles.ffx" [ ARCHIVE | 1159 Ko ]
963. TC: 19/06/2016,02:09:24 | TM: 01/03/2012,22:24:04 | DA: 19/06/2016,02:09:24
964.
965. Hash MD5: A36908F65A96E1B61DF9FA7AB9EE5946
966.
967.
968. =========================
969.
970.
971. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\Crackme2\CRACKME par inverse de push.exe" [ ARCHIVE | 20 Ko ]
972. TC: 25/06/2016,16:30:06 | TM: 30/07/2011,19:18:14 | DA: 25/06/2016,16:30:06
973.
974. Hash MD5: 33164B87417BF045221307BCCE8260CD
975.
976.
977. =========================
978.
979.
980. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\Crackme2\CRACKME par nop.exe" [ ARCHIVE | 20 Ko ]
981. TC: 25/06/2016,16:30:06 | TM: 30/07/2011,19:51:11 | DA: 25/06/2016,16:30:06
982.
983. Hash MD5: C01AE62AAB3D9968C8855E7F5F4D4559
984.
985.
986. =========================
987.
988.
989. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\Crackme2\CRACKME.EXE" [ ARCHIVE | 20 Ko ]
990. TC: 25/06/2016,16:30:06 | TM: 12/12/1998,18:17:12 | DA: 25/06/2016,16:30:06
991.
992. Hash MD5: 03732D98863AE4CF5A36F129CBF46781
993.
994.
995. =========================
996.
997.
998. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\CrackWep\Tools\winaircrackpack\WinAircrackPack\WinAircrackPack\WinAircrack.exe" [ ARCHIVE | 1057 Ko ]
999. TC: 25/06/2016,16:30:06 | TM: 17/11/2005,08:17:48 | DA: 25/06/2016,16:30:06
1000.
1001. Hash MD5: 5FE772F7942748FDCE214147B43E1850
1002.
1003. CompanyName: Hexanium
1004. ProductName: WinAircrack
1005. InternalName: WinAircrack
1006. OriginalFileName: WinAircrack.exe
1007. LegalCopyright: Hexanium
1008. LegalTrademarks: WinAircrack
1009. ProductVersion: 1.0.0.0
1010. FileVersion: 2.6.0.0
1011.
1012. =========================
1013.
1014.
1015. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\CrackWep\Tools\winaircrackpack\WinAircrackPack\WinAircrackPack\WinAircrack.ini" [ ARCHIVE | 195 o ]
1016. TC: 25/06/2016,16:30:06 | TM: 30/07/2011,18:41:22 | DA: 25/06/2016,16:30:06
1017.
1018. Hash MD5: A9A6881DB61D91E8CD863600CE7594DB
1019.
1020.
1021. =========================
1022.
1023.
1024. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\CrackWep\Tools\winaircrackpack\WinAircrackPack\WinAircrackPack by sheppard\tuto WinAircrack.docx" [ ARCHIVE | 165 Ko ]
1025. TC: 25/06/2016,16:30:06 | TM: 21/01/2007,05:36:50 | DA: 25/06/2016,16:30:06
1026.
1027. Hash MD5: BB52CB1D2E843BB256EEFD7DEB8C1103
1028.
1029.
1030. =========================
1031.
1032.
1033. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\CrackWep\Tools\winaircrackpack\WinAircrackPack\WinAircrackPack by sheppard\WinAircrack.exe" [ ARCHIVE | 1057 Ko ]
1034. TC: 25/06/2016,16:30:06 | TM: 17/11/2005,09:17:48 | DA: 25/06/2016,16:30:06
1035.
1036. Hash MD5: 5FE772F7942748FDCE214147B43E1850
1037.
1038. CompanyName: Hexanium
1039. ProductName: WinAircrack
1040. InternalName: WinAircrack
1041. OriginalFileName: WinAircrack.exe
1042. LegalCopyright: Hexanium
1043. LegalTrademarks: WinAircrack
1044. ProductVersion: 1.0.0.0
1045. FileVersion: 2.6.0.0
1046.
1047. =========================
1048.
1049.
1050. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\CrackWep\Tools\winaircrackpack\WinAircrackPack\WinAircrackPack by sheppard\WinAircrack.ini" [ ARCHIVE | 142 o ]
1051. TC: 25/06/2016,16:30:06 | TM: 08/12/2011,16:05:49 | DA: 25/06/2016,16:30:06
1052.
1053. Hash MD5: B1EBAFEBBEEF4F21177528D184E8958E
1054.
1055.
1056. =========================
1057.
1058.
1059. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\odbg110\CRACKME.udd" [ ARCHIVE | 2 Ko ]
1060. TC: 25/06/2016,16:30:06 | TM: 31/07/2007,01:27:06 | DA: 25/06/2016,16:30:06
1061.
1062. Hash MD5: 702F91CF0EA4BB8E3A5642AF3409018C
1063.
1064.
1065. =========================
1066.
1067.
1068. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crack pack\odbg110\CRACKME_1.udd" [ ARCHIVE | 12 Ko ]
1069. TC: 25/06/2016,16:30:06 | TM: 01/08/2007,01:32:54 | DA: 25/06/2016,16:30:06
1070.
1071. Hash MD5: 2B2AAFA87D625C12F8FA1675CE7952F1
1072.
1073.
1074. =========================
1075.
1076.
1077. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\CRACKME.EXE" [ ARCHIVE | 619 o ]
1078. TC: 25/06/2016,16:30:05 | TM: 30/07/2011,20:41:10 | DA: 25/06/2016,16:30:05
1079.
1080. Hash MD5: 85E263FE2245E4F711F04DDE2A51649F
1081.
1082.
1083. =========================
1084.
1085.
1086. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\CrackMe10.zip" [ ARCHIVE | 8 Ko ]
1087. TC: 25/06/2016,16:30:05 | TM: 13/06/2011,08:24:28 | DA: 25/06/2016,16:30:05
1088.
1089. Hash MD5: 38B2B067CCD2AF013CC5D5AA85487081
1090.
1091.
1092. =========================
1093.
1094.
1095. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crackme13.zip" [ ARCHIVE | 8 Ko ]
1096. TC: 25/06/2016,16:30:05 | TM: 04/06/2011,10:39:20 | DA: 25/06/2016,16:30:05
1097.
1098. Hash MD5: E273C432552FA9F44D3BD3CF6D8934DD
1099.
1100.
1101. =========================
1102.
1103.
1104. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crackme14.zip" [ ARCHIVE | 46 Ko ]
1105. TC: 25/06/2016,16:30:05 | TM: 04/06/2011,12:31:24 | DA: 25/06/2016,16:30:05
1106.
1107. Hash MD5: 59C62CD6132173D29566E0ABC3046E73
1108.
1109.
1110. =========================
1111.
1112.
1113. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crackme2.zip" [ ARCHIVE | 11 Ko ]
1114. TC: 25/06/2016,16:30:05 | TM: 04/06/2011,10:04:18 | DA: 25/06/2016,16:30:05
1115.
1116. Hash MD5: BFC8D83F4115A8D96596CA1D65BBD486
1117.
1118.
1119. =========================
1120.
1121.
1122. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\crackme24.rar" [ ARCHIVE | 346 Ko ]
1123. TC: 25/06/2016,16:30:05 | TM: 04/06/2011,12:37:44 | DA: 25/06/2016,16:30:05
1124.
1125. Hash MD5: 8FE40E56848CA3F424D61A6501842ABB
1126.
1127.
1128. =========================
1129.
1130.
1131. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\CRACKME3 keygen.exe" [ ARCHIVE | 146 o ]
1132. TC: 25/06/2016,16:30:05 | TM: 30/07/2011,20:28:31 | DA: 25/06/2016,16:30:05
1133.
1134. Hash MD5: 1283DF220559F1DD2CBD31EA49A0C813
1135.
1136.
1137. =========================
1138.
1139.
1140. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crackme3.2.exe" [ ARCHIVE | 310 Ko ]
1141. TC: 25/06/2016,16:30:05 | TM: 30/07/2011,20:09:56 | DA: 25/06/2016,16:30:05
1142.
1143. Hash MD5: FF7D8DDBDD31D5B4AFF63C4B99F54D3D
1144.
1145.
1146. =========================
1147.
1148.
1149. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crackme3.exe" [ ARCHIVE | 310 Ko ]
1150. TC: 25/06/2016,16:30:05 | TM: 17/01/1999,05:52:04 | DA: 25/06/2016,16:30:05
1151.
1152. Hash MD5: 40ECB17CBB004CBD27EBC9A45BA45C38
1153.
1154.
1155. =========================
1156.
1157.
1158. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Crackme3.zip" [ ARCHIVE | 172 Ko ]
1159. TC: 25/06/2016,16:30:05 | TM: 30/07/2011,20:05:41 | DA: 25/06/2016,16:30:05
1160.
1161. Hash MD5: C9C48B8CF53511131A8F39C7076999D6
1162.
1163.
1164. =========================
1165.
1166.
1167. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\CrackMe9.exe" [ ARCHIVE | 135 Ko ]
1168. TC: 25/06/2016,16:30:05 | TM: 08/05/2002,12:17:02 | DA: 25/06/2016,16:30:05
1169.
1170. Hash MD5: 088BB00B9AC4627ADC8F3E10D5622FC0
1171.
1172. CompanyName: Crackers For Freedom
1173. ProductName: Crackers For Freedom CrackMe v2.0
1174. InternalName: CrackMe #2
1175. OriginalFileName: CrackMe2.exe
1176. LegalCopyright: Crackers For Freedom
1177. LegalTrademarks: Coder: Acid Bytes [Lz0,CFF]
1178. ProductVersion: 2.0.0.0
1179. FileVersion: 2.0.0.0
1180.
1181. =========================
1182.
1183.
1184. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\CrackMe9.zip" [ ARCHIVE | 136 Ko ]
1185. TC: 25/06/2016,16:30:05 | TM: 02/06/2011,16:57:36 | DA: 25/06/2016,16:30:05
1186.
1187. Hash MD5: D89957AE3341DFF140A7A8D05B7E04DC
1188.
1189.
1190. =========================
1191.
1192.
1193. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\crack & cracker relatif aux programmes\Restorator\Restorator\crack.exe" [ ARCHIVE | 7 Ko ]
1194. TC: 25/06/2016,16:30:06 | TM: 16/02/2000,13:41:08 | DA: 25/06/2016,16:30:06
1195.
1196. Hash MD5: D1602DA22645D004F63366BBD90E5AFC
1197.
1198.
1199. =========================
1200.
1201.
1202. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\Wifi\WinAircrackPack by sheppard\tuto WinAircrack.docx" [ ARCHIVE | 165 Ko ]
1203. TC: 25/06/2016,16:30:07 | TM: 21/01/2007,05:36:50 | DA: 25/06/2016,16:30:07
1204.
1205. Hash MD5: BB52CB1D2E843BB256EEFD7DEB8C1103
1206.
1207.
1208. =========================
1209.
1210.
1211. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\Wifi\WinAircrackPack by sheppard\WinAircrack.exe" [ ARCHIVE | 1057 Ko ]
1212. TC: 25/06/2016,16:30:07 | TM: 26/06/2016,23:08:25 | DA: 25/06/2016,16:30:07
1213.
1214. Hash MD5: 5FE772F7942748FDCE214147B43E1850
1215.
1216. CompanyName: Hexanium
1217. ProductName: WinAircrack
1218. InternalName: WinAircrack
1219. OriginalFileName: WinAircrack.exe
1220. LegalCopyright: Hexanium
1221. LegalTrademarks: WinAircrack
1222. ProductVersion: 1.0.0.0
1223. FileVersion: 2.6.0.0
1224.
1225. =========================
1226.
1227.
1228. "C:\Users\Marwan Louraichia\Downloads\Hack, crack et virus\CRACK\Wifi\WinAircrackPack by sheppard\WinAircrack.ini" [ ARCHIVE | 142 o ]
1229. TC: 25/06/2016,16:30:07 | TM: 26/06/2016,23:08:27 | DA: 25/06/2016,16:30:07
1230.
1231. Hash MD5: B1EBAFEBBEEF4F21177528D184E8958E
1232.
1233.
1234. =========================
1235.
1236.
1237.
1238. ====== Entrée(s) du registre ======
1239.
1240.
1241. [HKLM\Software\Microsoft\Windows NT\CurrentVersion\Perflib\009]
1242. "Help"="3
1243. The System performance object consists of counters that apply to more than one instance of a component processors on the computer.
1244. 5
1245. 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.
1246. 7
1247. % 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.
1248. 9
1249. % 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.
1250. 11
1251. 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.
1252. 13
1253. 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.
1254. 15
1255. 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.
1256. 17
1257. 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.
1258. 19
1259. 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.
1260. 21
1261. 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.
1262. 23
1263. % 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.
1264. 25
1265. 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.
1266. 27
1267. 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.
1268. 29
1269. 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.
1270. 31
1271. 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.
1272. 33
1273. 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.
1274. 35
1275. 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.
1276. 37
1277. 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.
1278. 39
1279. 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.
1280. 41
1281. 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.
1282. 43
1283. 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.
1284. 45
1285. 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.
1286. 47
1287. 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.
1288. 49
1289. 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.
1290. 51
1291. 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.
1292. 53
1293. The Browser performance object consists of counters that measure the rates of announcements, enumerations, and other Browser transmissions.
1294. 55
1295. Announcements Server/sec is the rate at which the servers in this domain have announced themselves to this server.
1296. 57
1297. Pool Paged Bytes is the size, in bytes, of the paged pool, an area of the system virtual memory that is used for objects that can be written to disk when they are not being used. Memory\\Pool Paged Bytes is calculated differently than Process\\Pool Paged Bytes, so it might not equal Process(_Total)\\Pool Paged Bytes. This counter displays the last observed value only; it is not an average.
1298. 59
1299. Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of the system virtual memory that is used for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated. Memory\\Pool Nonpaged Bytes is calculated differently than Process\\Pool Nonpaged Bytes, so it might not equal Process(_Total)\\Pool Nonpaged Bytes. This counter displays the last observed value only; it is not an average.
1300. 61
1301. Pool Paged Allocs is the number of calls to allocate space in the paged pool. The paged pool is an area of the system virtual memory that is used for objects that can be written to disk when they are not being used. It is measured in numbers of calls to allocate space, regardless of the amount of space allocated in each call. This counter displays the last observed value only; it is not an average.
1302. 63
1303. Pool Paged Resident Bytes is the size, in bytes, of the portion of the paged pool that is currently resident and active in physical memory. The paged pool is an area of the system virtual memory that is used for objects that can be written to disk when they are not being used. This counter displays the last observed value only; it is not an average.
1304. 65
1305. 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.
1306. 67
1307. 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.
1308. 69
1309. System Code Total Bytes is the size, in bytes, of the pageable operating system code currently mapped into the system virtual address space. This value is calculated by summing the bytes in Ntoskrnl.exe, Hal.dll, the boot drivers, and file systems loaded by Ntldr/osloader. This counter does not include code that must remain in physical memory and cannot be written to disk. This counter displays the last observed value only; it is not an average.
1310. 71
1311. System Code Resident Bytes is the size, in bytes, of the pageable operating system code that is currently resident and active in physical memory. This value is a component of Memory\\System Code Total Bytes. Memory\\System Code Resident Bytes (and Memory\\System Code Total Bytes) does not include code that must remain in physical memory and cannot be written to disk. This counter displays the last observed value only; it is not an average.
1312. 73
1313. 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 both physical memory (Memory\\System Driver Resident Bytes) and code and data paged to disk. It is a component of Memory\\System Code Total Bytes. This counter displays the last observed value only; it is not an average.
1314. 75
1315. 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.
1316. 77
1317. System Cache Resident Bytes is the size, in bytes, of the portion of the system file cache which is currently resident and active in physical memory. The System Cache Resident Bytes and Memory\\Cache Bytes counters are equivalent. This counter displays the last observed value only; it is not an average.
1318. 79
1319. Announcements Domain/sec is the rate at which a domain has announced itself to the network.
1320. 81
1321. Election Packets/sec is the rate at which browser election packets have been received by this workstation.
1322. 83
1323. Mailslot Writes/sec is the rate at which mailslot messages have been successfully received.
1324. 85
1325. Server List Requests/sec is the rate at which requests to retrieve a list of browser servers have been processed by this workstation.
1326. 87
1327. 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.
1328. 89
1329. 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.
1330. 91
1331. 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.
1332. 93
1333. 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.
1334. 95
1335. 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.
1336. 97
1337. 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.
1338. 99
1339. 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.
1340. 101
1341. 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.
1342. 103
1343. 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.
1344. 105
1345. 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.
1346. 107
1347. 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.
1348. 109
1349. 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.
1350. 111
1351. 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.
1352. 113
1353. 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.
1354. 115
1355. 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.
1356. 117
1357. 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.
1358. 119
1359. 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.
1360. 121
1361. 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.
1362. 123
1363. 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.
1364. 125
1365. 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.
1366. 127
1367. 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.
1368. 129
1369. 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.
1370. 131
1371. Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request.
1372. 133
1373. 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.
1374. 135
1375. 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.
1376. 137
1377. 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.
1378. 139
1379. 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.
1380. 141
1381. 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.
1382. 143
1383. % 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.
1384. 145
1385. % 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.
1386. 147
1387. 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.
1388. 149
1389. 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.
1390. 151
1391. 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.
1392. 153
1393. 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.
1394. 155
1395. 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.
1396. 157
1397. % 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.
1398. 159
1399. % 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.
1400. 161
1401. Enumerations Server/sec is the rate at which server browse requests have been processed by this workstation.
1402. 163
1403. Enumerations Domain/sec is the rate at which domain browse requests have been processed by this workstation.
1404. 165
1405. Enumerations Other/sec is the rate at which browse requests processed by this workstation are not domain or server browse requests.
1406. 167
1407. Missed Server Announcements is the number of server announcements that have been missed due to configuration or allocation limits.
1408. 169
1409. Missed Mailslot Datagrams is the number of Mailslot Datagrams that have been discarded due to configuration or allocation limits.
1410. 171
1411. 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.
1412. 173
1413. 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.
1414. 175
1415. 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.
1416. 177
1417. 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.
1418. 179
1419. 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.
1420. 181
1421. 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.
1422. 183
1423. 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.
1424. 185
1425. 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.
1426. 187
1427. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes.
1428. 189
1429. % 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.
1430. 191
1431. % 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.
1432. 193
1433. % 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.
1434. 195
1435. % 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.
1436. 197
1437. 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.
1438. 199
1439. 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.
1440. 201
1441. % Disk Time is the percentage of elapsed time that the selected disk drive was busy servicing read or write requests.
1442. 203
1443. % Disk Read Time is the percentage of elapsed time that the selected disk drive was busy servicing read requests.
1444. 205
1445. % Disk Write Time is the percentage of elapsed time that the selected disk drive was busy servicing write requests.
1446. 207
1447. Avg. Disk sec/Transfer is the time, in seconds, of the average disk transfer.
1448. 209
1449. Avg. Disk sec/Read is the average time, in seconds, of a read of data from the disk.
1450. 211
1451. Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk.
1452. 213
1453. Disk Transfers/sec is the rate of read and write operations on the disk.
1454. 215
1455. Disk Reads/sec is the rate of read operations on the disk.
1456. 217
1457. Disk Writes/sec is the rate of write operations on the disk.
1458. 219
1459. Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations.
1460. 221
1461. Disk Read Bytes/sec is the rate at which bytes are transferred from the disk during read operations.
1462. 223
1463. Disk Write Bytes/sec is rate at which bytes are transferred to the disk during write operations.
1464. 225
1465. Avg. Disk Bytes/Transfer is the average number of bytes transferred to or from the disk during write or read operations.
1466. 227
1467. Avg. Disk Bytes/Read is the average number of bytes transferred from the disk during read operations.
1468. 229
1469. Avg. Disk Bytes/Write is the average number of bytes transferred to the disk during write operations.
1470. 231
1471. 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.
1472. 233
1473. 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.
1474. 235
1475. 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.
1476. 237
1477. 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.
1478. 239
1479. 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.
1480. 241
1481. % 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%.
1482. 243
1483. % 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.
1484. 245
1485. % 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.
1486. 247
1487. 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.
1488. 249
1489. 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.
1490. 251
1491. 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.
1492. 253
1493. 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.
1494. 255
1495. 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.
1496. 257
1497. 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.
1498. 259
1499. 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.
1500. 261
1501. 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.
1502. 263
1503. The Redirector performance object consists of counter that monitor network connections originating at the local computer.
1504. 265
1505. 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).
1506. 267
1507. 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).
1508. 269
1509. 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).
1510. 271
1511. 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.
1512. 273
1513. 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).
1514. 275
1515. 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).
1516. 277
1517. 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).
1518. 279
1519. 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.
1520. 281
1521. 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).
1522. 283
1523. 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.
1524. 285
1525. 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.
1526. 287
1527. 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).
1528. 289
1529. 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.
1530. 291
1531. 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.
1532. 293
1533. 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.
1534. 295
1535. 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.
1536. 297
1537. 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.
1538. 299
1539. 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.
1540. 301
1541. 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.
1542. 303
1543. 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.
1544. 305
1545. 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.
1546. 307
1547. 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.
1548. 309
1549. 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.
1550. 311
1551. 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.
1552. 313
1553. 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 Message Block) protocol error is a Network Error. An entry is written to the System Event Log and provide details.
1554. 315
1555. 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.
1556. 317
1557. 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.
1558. 319
1559. 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.
1560. 321
1561. Connects LAN Manager 2.0 counts connections to LAN Manager 2.0 servers, including LMX servers.
1562. 323
1563. Connects LAN Manager 2.1 counts connections to LAN Manager 2.1 servers, including LMX servers.
1564. 325
1565. Connects Windows NT counts the connections to Windows 2000 or earlier computers.
1566. 327
1567. Server Disconnects counts the number of times a Server has disconnected your Redirector. See also Server Reconnects.
1568. 329
1569. 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.
1570. 331
1571. The Server performance object consists of counters that measure communication between the local computer and the network.
1572. 333
1573. The number of bytes the server has received from the network. Indicates how busy the server is.
1574. 335
1575. The number of bytes the server has sent on the network. Indicates how busy the server is.
1576. 337
1577. 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).
1578. 339
1579. % 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.
1580. 341
1581. 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.
1582. 343
1583. 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. The autodisconnect timeout value represents the number of seconds that idle connections with no session attached to have before being disconnected automatically by a server. The default value is 30 seconds. This counter increments as a result of normal server operation, not as an indication of network problems or unexpected error condition.
1584. 345
1585. The number of sessions that have terminated normally. Useful in interpreting the Sessions Times Out and Sessions Errored Out statistics--allows percentage calculations.
1586. 347
1587. The number of sessions that have been forced to logoff. Can indicate how many sessions were forced to logoff due to logon time constraints.
1588. 349
1589. 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.
1590. 351
1591. 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.
1592. 353
1593. The number of times accesses to files opened successfully were denied. Can indicate attempts to access files without proper access authorization.
1594. 355
1595. The number of times an internal Server Error was detected. Unexpected errors usually indicate a problem with the Server.
1596. 357
1597. 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.
1598. 359
1599. 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.
1600. 361
1601. 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.
1602. 363
1603. The number of files currently opened in the server. Indicates current server activity.
1604. 365
1605. The number of sessions currently active in the server. Indicates current server activity.
1606. 367
1607. The number of searches for files currently active in the server. Indicates current server activity.
1608. 369
1609. 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.
1610. 371
1611. The number of times allocations from nonpaged pool have failed. Indicates that the computer's physical memory is too small.
1612. 373
1613. 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.
1614. 375
1615. The number of bytes of pageable computer memory the server is currently using. Can help in determining good values for the MaxPagedMemoryUsage parameter.
1616. 377
1617. The number of times allocations from paged pool have failed. Indicates that the computer's physical memory or paging file are too small.
1618. 379
1619. 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.
1620. 381
1621. Server Announce Allocations Failed/sec is the rate at which server (or domain) announcements have failed due to lack of memory.
1622. 383
1623. Mailslot Allocations Failed is the number of times the datagram receiver has failed to allocate a buffer to hold a user mailslot write.
1624. 385
1625. Mailslot Receives Failed indicates the number of mailslot messages that could not be received due to transport failures.
1626. 387
1627. Mailslot Writes Failed is the total number of mailslot messages that have been successfully received, but that could not be written to the mailslot.
1628. 389
1629. 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.
1630. 391
1631. 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.
1632. 393
1633. 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.
1634. 395
1635. 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.
1636. 397
1637. % 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.
1638. 399
1639. The NWLink NetBIOS performance object consists of counters that monitor IPX transport rates and connections.
1640. 401
1641. 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.
1642. 405
1643. 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.
1644. 407
1645. 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.
1646. 409
1647. % Free Space is the percentage of total usable space on the selected logical disk drive that was free.
1648. 411
1649. Free Megabytes displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.
1650. 413
1651. 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.
1652. 415
1653. 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.
1654. 417
1655. 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.
1656. 419
1657. 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.
1658. 421
1659. 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.
1660. 423
1661. 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.
1662. 425
1663. 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.
1664. 427
1665. 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.
1666. 429
1667. Connections Canceled is the number of connections that were canceled. This number is an accumulator and shows a running total.
1668. 431
1669. 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.
1670. 433
1671. 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.
1672. 435
1673. 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.
1674. 437
1675. Failures No Listen is the number of connections that were rejected because the remote computer was not listening for connection requests.
1676. 439
1677. 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.
1678. 441
1679. 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.
1680. 443
1681. 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.
1682. 445
1683. 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.
1684. 447
1685. 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.
1686. 449
1687. 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.
1688. 451
1689. 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.
1690. 453
1691. 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.
1692. 455
1693. 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.
1694. 457
1695. 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.
1696. 459
1697. 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.
1698. 461
1699. 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.
1700. 463
1701. 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.
1702. 465
1703. 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.
1704. 467
1705. 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.
1706. 469
1707. 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.
1708. 471
1709. 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.
1710. 473
1711. Frames Rejected/sec is the rate at which data frames are rejected. This counter only counts the frames (packets) that carry data.
1712. 475
1713. 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.
1714. 477
1715. Expirations Response is the count of T1 timer expirations.
1716. 479
1717. Expirations Ack is the count of T2 timer expirations.
1718. 481
1719. Window Send Maximum is the maximum number of bytes of data that will be sent before waiting for an acknowledgment from the remote computer.
1720. 483
1721. Window Send Average is the running average number of data bytes that were sent before waiting for an acknowledgment from the remote computer.
1722. 485
1723. 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.
1724. 487
1725. 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.
1726. 489
1727. The NWLink IPX performance object consists of counters that measure datagram transmission to and from computers using the IPX protocol.
1728. 491
1729. The NWLink SPX performance object consist of counters that measure data transmission and session connections for computers using the SPX protocol.
1730. 493
1731. The NetBEUI performance object consists of counters that measure data transmission for network activity which conforms to the NetBIOS End User Interface standard.
1732. 495
1733. The NetBEUI Resource performance object consists of counters that track the use of buffers by the NetBEUI protocol.
1734. 497
1735. 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.
1736. 499
1737. 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.
1738. 501
1739. 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.
1740. 503
1741. 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.
1742. 505
1743. 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.
1744. 507
1745. 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.
1746. 509
1747. 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.
1748. 511
1749. The Network Interface performance object consists of counters that measure the rates at which bytes and packets are sent and received over a network connection. It includes counters that monitor connection errors.
1750. 513
1751. 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.
1752. 515
1753. Packets/sec is the rate at which packets are sent and received on the network interface.
1754. 517
1755. Packets Received/sec is the rate at which packets are received on the network interface.
1756. 519
1757. Packets Sent/sec is the rate at which packets are sent on the network interface.
1758. 521
1759. 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.
1760. 523
1761. 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.
1762. 525
1763. Packets Received Unicast/sec is the rate at which (subnet) unicast packets are delivered to a higher-layer protocol.
1764. 527
1765. 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.
1766. 529
1767. 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.
1768. 531
1769. Packets Received Errors is the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
1770. 533
1771. Packets Received Unknown is the number of packets received through the interface that were discarded because of an unknown or unsupported protocol.
1772. 535
1773. 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.
1774. 537
1775. 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.
1776. 539
1777. 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.
1778. 541
1779. 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.
1780. 543
1781. Packets Outbound Errors is the number of outbound packets that could not be transmitted because of errors.
1782. 545
1783. 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.
1784. 547
1785. 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.
1786. 549
1787. 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.
1788. 551
1789. 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.
1790. 553
1791. 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.
1792. 555
1793. 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.
1794. 557
1795. 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.
1796. 559
1797. 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.
1798. 561
1799. 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.
1800. 563
1801. 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).
1802. 565
1803. 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.
1804. 567
1805. 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.
1806. 569
1807. 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.
1808. 571
1809. Fragments Received/sec is the rate, in incidents per second, at which IP fragments that need to be reassembled at this entity are received.
1810. 573
1811. Fragments Re-assembled/sec is the rate, in incidents per second, at which IP fragments were successfully reassembled.
1812. 575
1813. 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.
1814. 577
1815. Fragmented Datagrams/sec is the rate, in incidents per second, at which datagrams are successfully fragmented.
1816. 579
1817. 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).
1818. 581
1819. Fragments Created/sec is the rate, in incidents per second, at which IP datagram fragments were generated as a result of fragmentation.
1820. 583
1821. 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.
1822. 585
1823. 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.
1824. 587
1825. Messages Received/sec is the rate, in incidents per second at which ICMP messages were received. The rate includes messages received in error.
1826. 589
1827. Messages Received Errors is the number of ICMP messages that the entity received but had errors, such as bad ICMP checksums, bad length, etc.
1828. 591
1829. Received Destination Unreachable is the number of ICMP Destination Unreachable messages received.
1830. 593
1831. Received Time Exceeded is the number of ICMP Time Exceeded messages received.
1832. 595
1833. Received Parameter Problem is the number of ICMP Parameter Problem messages received.
1834. 597
1835. Received Source Quench is the number of ICMP Source Quench messages received.
1836. 599
1837. Received Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were received.
1838. 601
1839. Received Echo/sec is the rate, in incidents per second, at which ICMP Echo messages were received.
1840. 603
1841. Received Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were received.
1842. 605
1843. Received Timestamp/sec is the rate, in incidents per second at which ICMP Timestamp Request messages were received.
1844. 607
1845. Received Timestamp Reply/sec is the rate of ICMP Timestamp Reply messages received.
1846. 609
1847. Received Address Mask is the number of ICMP Address Mask Request messages received.
1848. 611
1849. Received Address Mask Reply is the number of ICMP Address Mask Reply messages received.
1850. 613
1851. 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.
1852. 615
1853. 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.
1854. 617
1855. Sent Destination Unreachable is the number of ICMP Destination Unreachable messages sent.
1856. 619
1857. Sent Time Exceeded is the number of ICMP Time Exceeded messages sent.
1858. 621
1859. Sent Parameter Problem is the number of ICMP Parameter Problem messages sent.
1860. 623
1861. Sent Source Quench is the number of ICMP Source Quench messages sent.
1862. 625
1863. Sent Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were sent.
1864. 627
1865. Sent Echo/sec is the rate of ICMP Echo messages sent.
1866. 629
1867. Sent Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were sent.
1868. 631
1869. Sent Timestamp/sec is the rate, in incidents per second, at which ICMP Timestamp Request messages were sent.
1870. 633
1871. Sent Timestamp Reply/sec is the rate, in incidents per second, at which ICMP Timestamp Reply messages were sent.
1872. 635
1873. Sent Address Mask is the number of ICMP Address Mask Request messages sent.
1874. 637
1875. Sent Address Mask Reply is the number of ICMP Address Mask Reply messages sent.
1876. 639
1877. 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.
1878. 641
1879. Segments/sec is the rate at which TCP segments are sent or received using the TCP protocol.
1880. 643
1881. Connections Established is the number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
1882. 645
1883. 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.
1884. 647
1885. 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.
1886. 649
1887. 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.
1888. 651
1889. 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.
1890. 653
1891. 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.
1892. 655
1893. Segments Sent/sec is the rate at which segments are sent, including those on current connections, but excluding those containing only retransmitted bytes.
1894. 657
1895. Segments Retransmitted/sec is the rate at which segments are retransmitted, that is, segments transmitted containing one or more previously transmitted bytes.
1896. 659
1897. 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.
1898. 661
1899. Datagrams/sec is the rate at which UDP datagrams are sent or received by the entity.
1900. 663
1901. Datagrams Received/sec is the rate at which UDP datagrams are delivered to UDP users.
1902. 665
1903. Datagrams No Port/sec is the rate of received UDP datagrams for which there was no application at the destination port.
1904. 667
1905. 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.
1906. 669
1907. Datagrams Sent/sec is the rate at which UDP datagrams are sent from the entity.
1908. 671
1909. Disk Storage device statistics from the foreign computer
1910. 673
1911. The number of allocation failures reported by the disk storage device
1912. 675
1913. 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.
1914. 677
1915. The current number of system handles in use.
1916. 679
1917. 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.
1918. 681
1919. 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.
1920. 683
1921. 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.
1922. 685
1923. The total elapsed time, in seconds, that this process has been running.
1924. 687
1925. Alignment Fixups/sec is the rate, in incidents per seconds, at alignment faults were fixed by the system.
1926. 689
1927. Exception Dispatches/sec is the rate, in incidents per second, at which exceptions were dispatched by the system.
1928. 691
1929. 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.
1930. 693
1931. Logon/sec is the rate of all server logons.
1932. 695
1933. 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.
1934. 697
1935. 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.
1936. 699
1937. The total elapsed time (in seconds) this thread has been running.
1938. 701
1939. 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.
1940. 703
1941. The amount of the Page File instance in use in percent. See also Process\\Page File Bytes.
1942. 705
1943. The peak usage of the Page File instance in percent. See also Process\\Page File Bytes Peak.
1944. 707
1945. Starting virtual address for this thread.
1946. 709
1947. Current User Program Counter for this thread.
1948. 711
1949. 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.
1950. 713
1951. 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.
1952. 715
1953. 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.
1954. 717
1955. 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.
1956. 719
1957. 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.
1958. 721
1959. 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.
1960. 723
1961. 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.
1962. 725
1963. 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.
1964. 727
1965. 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.
1966. 729
1967. 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.
1968. 731
1969. 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.
1970. 733
1971. 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.
1972. 735
1973. 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.
1974. 737
1975. 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.
1976. 739
1977. 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.
1978. 741
1979. The Image performance object consists of counters that monitor the virtual address usage of images executed by processes on the computer.
1980. 743
1981. 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.
1982. 745
1983. 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.
1984. 747
1985. 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.
1986. 749
1987. 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.
1988. 751
1989. 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.
1990. 753
1991. 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.
1992. 755
1993. 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.
1994. 757
1995. 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.
1996. 759
1997. 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.
1998. 761
1999. 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.
2000. 763
2001. 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.
2002. 765
2003. 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.
2004. 767
2005. 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.
2006. 769
2007. 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.
2008. 771
2009. 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.
2010. 773
2011. 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.
2012. 775
2013. 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.
2014. 777
2015. Bytes Image Reserved is the sum of all virtual memory reserved by images within this process.
2016. 779
2017. Bytes Image Free is the amount of virtual address space that is not in use or reserved by images within this process.
2018. 781
2019. Bytes Reserved is the total amount of virtual memory reserved for future use by this process.
2020. 783
2021. Bytes Free is the total unused virtual address space of this process.
2022. 785
2023. 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.
2024. 787
2025. The Process Address Space performance object consists of counters that monitor memory allocation and use for a selected process.
2026. 789
2027. 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.
2028. 791
2029. 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.
2030. 793
2031. 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.
2032. 795
2033. 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.
2034. 797
2035. 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.
2036. 799
2037. 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.
2038. 801
2039. 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.
2040. 803
2041. 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.
2042. 805
2043. 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.
2044. 807
2045. 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.
2046. 809
2047. Duplicate Master Announcements indicates the number of times that the master browser has detected another master browser on the same domain.
2048. 811
2049. Illegal Datagrams/sec is the rate at which incorrectly formatted datagrams have been received by the workstation.
2050. 813
2051. Announcements Total/sec is the sum of Announcements Server/sec and Announcements Domain/sec.
2052. 815
2053. 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.
2054. 817
2055. 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.
2056. 819
2057. Cache Bytes the size, in bytes, of the portion of the system file cache which is currently resident and active in physical memory. The Cache Bytes and Memory\\System Cache Resident Bytes counters are equivalent. This counter displays the last observed value only; it is not an average.
2058. 821
2059. Cache Bytes Peak is the maximum number of bytes used by the system file cache since the system was last restarted. This might be larger than the current size of the cache. This counter displays the last observed value only; it is not an average.
2060. 823
2061. 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.
2062. 825
2063. 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.
2064. 873
2065. The number of bytes transmitted total for this connection.
2066. 875
2067. The number of bytes received total for this connection.
2068. 877
2069. The number of data frames transmitted total for this connection.
2070. 879
2071. The number of data frames received total for this connection.
2072. 881
2073. The compression ratio for bytes being transmitted.
2074. 883
2075. The compression ratio for bytes being received.
2076. 885
2077. The total number of CRC Errors for this connection. CRC Errors occur when the frame received contains erroneous data.
2078. 887
2079. The total number of Timeout Errors for this connection. Timeout Errors occur when an expected is not received in time.
2080. 889
2081. 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.
2082. 891
2083. The total number of Alignment Errors for this connection. Alignment Errors occur when a byte received is different from the byte expected.
2084. 893
2085. 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.
2086. 895
2087. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.
2088. 897
2089. The number of bytes transmitted per second.
2090. 899
2091. The number of bytes received per second.
2092. 901
2093. The number of frames transmitted per second.
2094. 903
2095. The number of frames received per second.
2096. 905
2097. The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.
2098. 909
2099. The total number of Remote Access connections.
2100. 921
2101. The WINS Server performance object consists of counters that monitor communications using the WINS Server service.
2102. 923
2103. Unique Registrations/sec is the rate at which unique registration are received by the WINS server.
2104. 925
2105. Group Registrations/sec is the rate at which group registration are received by the WINS server.
2106. 927
2107. 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.
2108. 929
2109. Unique Renewals/sec is the rate at which unique renewals are received by the WINS server.
2110. 931
2111. Group Renewals/sec is the rate at which group renewals are received by the WINS server.
2112. 933
2113. 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.
2114. 935
2115. Total Number of Releases/sec is the rate at which releases are received by the WINS server.
2116. 937
2117. Total Number of Queries/sec is the rate at which queries are received by the WINS server.
2118. 939
2119. Unique Conflicts/sec is the rate at which unique registrations/renewals received by the WINS server resulted in conflicts with records in the database.
2120. 941
2121. Group Conflicts/sec is the rate at which group registration received by the WINS server resulted in conflicts with records in the database.
2122. 943
2123. 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.
2124. 945
2125. Total Number of Successful Releases/sec
2126. 947
2127. Total Number of Failed Releases/sec
2128. 949
2129. Total Number of Successful Queries/sec
2130. 951
2131. Total Number of Failed Queries/sec
2132. 953
2133. 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.
2134. 1001
2135. Services for Macintosh AFP File Server.
2136. 1003
2137. The maximum amount of paged memory resources used by the MacFile Server.
2138. 1005
2139. The current amount of paged memory resources used by the MacFile Server.
2140. 1007
2141. The maximum amount of nonpaged memory resources use by the MacFile Server.
2142. 1009
2143. The current amount of nonpaged memory resources used by the MacFile Server.
2144. 1011
2145. The number of sessions currently connected to the MacFile server. Indicates current server activity.
2146. 1013
2147. The maximum number of sessions connected at one time to the MacFile server. Indicates usage level of server.
2148. 1015
2149. The number of internal files currently open in the MacFile server. This count does not include files opened on behalf of Macintosh clients.
2150. 1017
2151. 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.
2152. 1019
2153. 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.
2154. 1021
2155. The number of bytes read from disk per second.
2156. 1023
2157. The number of bytes written to disk per second.
2158. 1025
2159. The number of bytes received from the network per second. Indicates how busy the server is.
2160. 1027
2161. The number of bytes sent on the network per second. Indicates how busy the server is.
2162. 1029
2163. The number of outstanding work items waiting to be processed.
2164. 1031
2165. The maximum number of outstanding work items waiting at one time.
2166. 1033
2167. The current number of threads used by MacFile server. Indicates how busy the server is.
2168. 1035
2169. The maximum number of threads used by MacFile server. Indicates peak usage level of server.
2170. 1051
2171. AppleTalk Protocol
2172. 1053
2173. Number of packets received per second by Appletalk on this port.
2174. 1055
2175. Number of packets sent per second by Appletalk on this port.
2176. 1057
2177. Number of bytes received per second by Appletalk on this port.
2178. 1059
2179. Number of bytes sent per second by Appletalk on this port.
2180. 1061
2181. Average time in milliseconds to process a DDP packet on this port.
2182. 1063
2183. Number of DDP packets per second received by Appletalk on this port.
2184. 1065
2185. Average time in milliseconds to process an AARP packet on this port.
2186. 1067
2187. Number of AARP packets per second received by Appletalk on this port.
2188. 1069
2189. Average time in milliseconds to process an ATP packet on this port.
2190. 1071
2191. Number of ATP packets per second received by Appletalk on this port.
2192. 1073
2193. Average time in milliseconds to process an NBP packet on this port.
2194. 1075
2195. Number of NBP packets per second received by Appletalk on this port.
2196. 1077
2197. Average time in milliseconds to process a ZIP packet on this port.
2198. 1079
2199. Number of ZIP packets per second received by Appletalk on this port.
2200. 1081
2201. Average time in milliseconds to process an RTMP packet on this port.
2202. 1083
2203. Number of RTMP packets per second received by Appletalk on this port.
2204. 1085
2205. Number of ATP requests retransmitted on this port.
2206. 1087
2207. Number of ATP release timers that have expired on this port.
2208. 1089
2209. Number of ATP Exactly-once transaction responses per second on this port.
2210. 1091
2211. Number of ATP At-least-once transaction responses per second on this port.
2212. 1093
2213. Number of ATP transaction release packets per second received on this port.
2214. 1095
2215. The current amount of nonpaged memory resources used by AppleTalk.
2216. 1097
2217. Number of packets routed in on this port.
2218. 1099
2219. Number of packets dropped due to resource limitations on this port.
2220. 1101
2221. Number of ATP requests retransmitted to this port.
2222. 1103
2223. Number of packets routed out on this port.
2224. 1111
2225. Provides Network Statistics for the local network segment via the Network Monitor Service.
2226. 1113
2227. The total number of frames received per second on this network segment.
2228. 1115
2229. The number of bytes received per second on this network segment.
2230. 1117
2231. The number of Broadcast frames received per second on this network segment.
2232. 1119
2233. The number of Multicast frames received per second on this network segment.
2234. 1121
2235. Percentage of network bandwidth in use on this network segment.
2236. 1125
2237. Percentage of network bandwidth which is made up of broadcast traffic on this network segment.
2238. 1127
2239. Percentage of network bandwidth which is made up of multicast traffic on this network segment.
2240. 1151
2241. The Telephony System
2242. 1153
2243. The number of telephone lines serviced by this computer.
2244. 1155
2245. The number of telephone devices serviced by this computer.
2246. 1157
2247. The number of telephone lines serviced by this computer that are currently active.
2248. 1159
2249. The number of telephone devices that are currently being monitored.
2250. 1161
2251. The rate of outgoing calls made by this computer.
2252. 1163
2253. The rate of incoming calls answered by this computer.
2254. 1165
2255. The number of applications that are currently using telephony services.
2256. 1167
2257. Current outgoing calls being serviced by this computer.
2258. 1169
2259. Current incoming calls being serviced by this computer.
2260. 1233
2261. 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.
2262. 1235
2263. 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.
2264. 1237
2265. 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.
2266. 1239
2267. 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.
2268. 1241
2269. Packet Burst IO/sec is the sum of Packet Burst Read NCPs/sec and Packet Burst Write NCPs/sec.
2270. 1261
2271. Logon Total indicates the total session setup attempts, including all successful logon and failed logons since the server service is started.
2272. 1263
2273. The total number of durable handle disconnects that have occurred.
2274. 1265
2275. The total number of durable handles that are successfully reconnected. The ratio of "reconnected durable handles"/"total durable handles" indicates the stability gain from reconnect durable handles.
2276. 1267
2277. The number of SMB BranchCache hash requests that were for the header only received by the server. This indicates how many requests are being done to validate hashes that are already cached by the client.
2278. 1269
2279. The number of SMB BranchCache hash generation requests that were sent by SRV2 to the SMB Hash Generation service because a client requested hashes for the file and there was either no hash content for the file or the existing hashes were out of date.
2280. 1271
2281. The number of SMB BranchCache hash requests that were received by the server.
2282. 1273
2283. The number of SMB BranchCache hash responses that have been sent from the server.
2284. 1275
2285. The amount of SMB BranchCache hash data sent from the server. This includes bytes transferred for both hash header requests and full hash data requests.
2286. 1277
2287. The total number of resilient handle disconnect that have occurred.
2288. 1279
2289. The total number of resilient handles that are successfully reconnected. The ratio of "reconnected resilient handles"/"total resilient handles" indicates the stability gain from reconnect resilient handles.
2290. 1301
2291. The Server Work Queues performance object consists of counters that monitor the length of the queues and objects in the queues.
2292. 1303
2293. Queue length is the current number of workitem in Blocking queues and Nonblocking queues, which indicates how busy the server is to process outstanding workitems for this CPU. A sustained queue length greater than four might indicate processor congestion. This is an instantaneous count, not an average over time.
2294. 1305
2295. 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.
2296. 1307
2297. 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.
2298. 1309
2299. 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 SMB1 Blocking Queue instance.
2300. 1311
2301. 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 and SMB2 Queue instances.
2302. 1313
2303. 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 and SMB2 Queue instances.
2304. 1315
2305. 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.
2306. 1317
2307. 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.
2308. 1319
2309. 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.
2310. 1321
2311. 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.
2312. 1323
2313. 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.
2314. 1325
2315. 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.
2316. 1327
2317. 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.
2318. 1329
2319. 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.
2320. 1331
2321. 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.
2322. 1333
2323. 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.
2324. 1335
2325. 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.
2326. 1337
2327. 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.
2328. 1343
2329. 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.
2330. 1345
2331. 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.
2332. 1351
2333. % 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.
2334. 1361
2335. Counters that indicate the status of local and system Very Large memory allocations.
2336. 1363
2337. VLM % Virtual Size In Use
2338. 1365
2339. Current size of the process VLM Virtual memory space in bytes.
2340. 1367
2341. 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.
2342. 1369
2343. 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.
2344. 1371
2345. The current size of committed VLM memory space for the current process in bytes.
2346. 1373
2347. The peak size of the committed VLM memory space in bytes for the current process since the process started.
2348. 1375
2349. The current size of all committed VLM memory space in bytes for the system.
2350. 1377
2351. The peak size of all committed VLM memory space in bytes since the system was started.
2352. 1379
2353. The current size of all committed shared VLM memory space in bytes for the system.
2354. 1381
2355. 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.
2356. 1383
2357. 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.
2358. 1401
2359. 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.
2360. 1403
2361. Avg. Disk Read Queue Length is the average number of read requests that were queued for the selected disk during the sample interval.
2362. 1405
2363. Avg. Disk Write Queue Length is the average number of write requests that were queued for the selected disk during the sample interval.
2364. 1407
2365. % 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.
2366. 1409
2367. 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.
2368. 1411
2369. 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.
2370. 1413
2371. 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.
2372. 1415
2373. 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.
2374. 1417
2375. 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.
2376. 1419
2377. 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.
2378. 1421
2379. 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.
2380. 1423
2381. 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.
2382. 1425
2383. 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.
2384. 1427
2385. 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.
2386. 1451
2387. Displays performance statistics about a Print Queue.
2388. 1453
2389. Total number of jobs printed on a print queue since the last restart.
2390. 1455
2391. Number of bytes per second printed on a print queue.
2392. 1457
2393. Total number of pages printed through GDI on a print queue since the last restart.
2394. 1459
2395. Current number of jobs in a print queue.
2396. 1461
2397. Current number of references (open handles) to this printer.
2398. 1463
2399. Peak number of references (open handles) to this printer.
2400. 1465
2401. Current number of spooling jobs in a print queue.
2402. 1467
2403. Maximum number of spooling jobs in a print queue since last restart.
2404. 1469
2405. Total number of out of paper errors in a print queue since the last restart.
2406. 1471
2407. Total number of printer not ready errors in a print queue since the last restart.
2408. 1473
2409. Total number of job errors in a print queue since last restart.
2410. 1475
2411. Total number of calls from browse clients to this print server to request network browse lists since last restart.
2412. 1477
2413. Total number of calls from other print servers to add shared network printers to this server since last restart.
2414. 1479
2415. 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.
2416. 1481
2417. 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.
2418. 1483
2419. % Idle Time reports the percentage of time during the sample interval that the disk was idle.
2420. 1485
2421. 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.
2422. 1501
2423. Reports the accounting and processor usage data collected by each active named Job object.
2424. 1503
2425. Current % Processor Time shows the percentage of the sample interval that the processes in the Job object spent executing code.
2426. 1505
2427. Current % User mode Time shows the percentage of the sample interval that the processes in the Job object spent executing code in user mode.
2428. 1507
2429. 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.
2430. 1509
2431. 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.
2432. 1511
2433. 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.
2434. 1513
2435. 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.
2436. 1515
2437. Pages/Sec shows the page fault rate of all the processes in the Job object.
2438. 1517
2439. Process Count - Total shows the number of processes, both active and terminated, that are or have been associated with the Job object.
2440. 1519
2441. Process Count - Active shows the number of processes that are currently associated with the Job object.
2442. 1521
2443. Process Count - Terminated shows the number of processes that have been terminated because of a limit violation.
2444. 1523
2445. 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.
2446. 1525
2447. 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.
2448. 1527
2449. 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.
2450. 1537
2451. Received Packet Too Big is the number of received packets thatare larger than anticipated.
2452. 1539
2453. Received Membership Query is the number of packets received thatquery their membership to a group.
2454. 1541
2455. Received Membership Report is the number of packets received thatreport their membership to a group.
2456. 1543
2457. Received Membership Reduction is the number of packets received thatcancelled their membership to a group.
2458. 1545
2459. Received Router Solicit is the number of packets received thatsolicit the router.
2460. 1547
2461. Received Router Advert is the number of packets received thatadvert the router.
2462. 1549
2463. % Job object Details shows detailed performance information about the active processes that make up a Job object.
2464. 1551
2465. Received Neighbor Solicit is the number of packets received thatsolicit a neighbor.
2466. 1553
2467. Received Neighbor Advert is the number of packets received thatadvert a neighbor.
2468. 1555
2469. Sent Packet Too Big is the number of sent packets thatare larger than anticipated.
2470. 1557
2471. Sent Membership Query is the number of packets sent thatquery their membership to a group.
2472. 1559
2473. Sent Membership Report is the number of packets sent thatreport their membership to a group.
2474. 1561
2475. Sent Membership Reduction is the number of packets sent thatcancelled their membership to a group.
2476. 1563
2477. Sent Router Solicit is the number of packets sent thatsolicit the router.
2478. 1565
2479. Sent Router Advert is the number of packets sent thatadvert the router.
2480. 1567
2481. Sent Neighbor Solicit is the number of packets sent thatsolicit a neighbor.
2482. 1569
2483. Sent Neighbor Advert is the number of packets sent thatadvert a neighbor.
2484. 1571
2485. These counters track authentication performance on a per second basis.
2486. 1573
2487. This counter tracks the number of NTLM authentications processed per second for the AD on this DC or for local accounts on this member server.
2488. 1575
2489. This counter tracks the number of times that clients use a ticket to authenticate to this computer per second.
2490. 1577
2491. This counter tracks the number of Authentication Service (AS) requests that are being processed by the Key Distribution Center (KDC) per second. Clients use AS requests to obtain a ticket-granting ticket.
2492. 1579
2493. 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.
2494. 1581
2495. 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.
2496. 1583
2497. 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.
2498. 1585
2499. 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.
2500. 1587
2501. 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.
2502. 1589
2503. 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.
2504. 1591
2505. 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.
2506. 1593
2507. This counter tracks the number of Digest authentications that are being processed per second.
2508. 1595
2509. This counter tracks the number of Kerberos requests that a read-only domain controller (RODC) forwards to its hub, per second. This counter is tracked only on a RODC.
2510. 1597
2511. Offloaded Connections is the number of TCP connections (over both IPv4 and IPv6) that are currently handled by the TCP chimney offload capable network adapter.
2512. 1599
2513. TCP Active RSC Connections is the number of TCP connections (over both IPv4 and IPv6) that are currently receiving large packets from the RSC capable network adapter on this network interface.
2514. 1601
2515. TCP RSC Coalesced Packets/sec shows the large packet receive rate across all TCP connections on this network interface.
2516. 1603
2517. TCP RSC Exceptions/sec shows the RSC exception rate for receive packets across all TCP connections on this network interface.
2518. 1605
2519. TCP RSC Average Packet Size is the average size in bytes of received packets across all TCP connections on this network interface.
2520. 1621
2521. This counter tracks the number of armored Authentication Service (AS) requests that are being processed by the Key Distribution Center (KDC) per second.
2522. 1623
2523. This counter tracks the number of armored ticket-granting service (TGS) requests that are being processed by the Key Distribution Center (KDC) per second.
2524. 1625
2525. This counter tracks the number of Authentication Service (AS) requests explicitly requesting claims that are being processed by the Key Distribution Center (KDC) per second.
2526. 1627
2527. This counter tracks the number of service asserted identity (S4U2Self) TGS requests that are explicitly requesting claims. These requests are being processed by the Key Distribution Center (KDC) per second.
2528. 1629
2529. This counter tracks the number of constrained delegation (S4U2Proxy) TGS requests that are being processed by the Key Distribution Center (KDC) by checking classic type constrained delegation configuration per second. The classic type constrained delegation is restricted to a single domain and configures the backend services SPN on the middle-tier service?s account object.
2530. 1631
2531. This counter tracks the number of constrained delegation (S4U2Proxy) TGS requests that are being processed by the Key Distribution Center (KDC) by checking the resource type constrained delegation per second. The resource type constrained delegation can cross domain boundaries and configures the middle-tier?s account on the backend service?s account object.
2532. 1633
2533. This counter tracks the number of claims-aware ticket-granting service (TGS) requests that are being processed by the Key Distribution Center (KDC) per second. A claims-aware Kerberos client will always request claims during Authentication Service (AS) exchanges.
2534. 1671
2535. These counters track the number of security resources and handles used per process.
2536. 1673
2537. 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.
2538. 1675
2539. 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.
2540. 1677
2541. 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.
2542. 1679
2543. 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.
2544. 1681
2545. 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.
2546. 1683
2547. 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.
2548. 1685
2549. 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.
2550. 1687
2551. Long-Term Average Standby Cache Lifetime, in seconds. The average lifetime of data in the standby cache over a long interval is measured.
2552. 1747
2553. % Idle Time is the percentage of time the processor is idle during the sample interval
2554. 1749
2555. % 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.
2556. 1751
2557. % 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.
2558. 1753
2559. % 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.
2560. 1755
2561. 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.
2562. 1757
2563. 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.
2564. 1759
2565. 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.
2566. 1761
2567. Heap performance counters for must used heaps
2568. 1763
2569. Memory actively used by this heap (FreeBytes + AllocatedBytes)
2570. 1765
2571. Total virtual address space reserved for this heap (includes uncommitted ranges)
2572. 1767
2573. ReservedBytes minus last uncommitted range in each segment
2574. 1769
2575. Memory on freelists in this heap (does not include uncommitted ranges or blocks in heap cache)
2576. 1771
2577. Number of blocks on the list of free blocks >1k in size
2578. 1773
2579. 1/Average time per allocation (excluding allocs from heap cache)
2580. 1775
2581. 1/Average time per free (excluding frees to heap cache)
2582. 1777
2583. Number of uncommitted ranges in the reserved virtual address
2584. 1779
2585. Difference between number of allocations and frees (for leak detection)
2586. 1781
2587. Allocations/sec from heap cache
2588. 1783
2589. Frees/sec from heap cache
2590. 1785
2591. Allocations/sec of size <1k bytes (including heap cache)
2592. 1787
2593. Frees/sec of size <1k bytes (including heap cache)
2594. 1789
2595. Allocations/sec of size 1-8k bytes
2596. 1791
2597. Frees/sec of size 1-8k bytes
2598. 1793
2599. Allocations/sec of size over 8k bytes
2600. 1795
2601. Frees/sec of size over 8k bytes
2602. 1797
2603. Allocations/sec (including from heap cache)
2604. 1799
2605. Frees/sec (including to heap cache)
2606. 1801
2607. Total number of blocks in the heap cache
2608. 1803
2609. Largest number of blocks of any one size in the heap cache
2610. 1805
2611. (FreeBytes / CommittedBytes) *100
2612. 1807
2613. (VirtualBytes / ReservedBytes) * 100
2614. 1809
2615. Collisions/sec on the heap lock
2616. 1811
2617. Total number of dirty pages on the system cache
2618. 1813
2619. Threshold for number of dirty pages on system cache
2620. 1815
2621. Counters that report approximate memory utilization statistics per node on NUMA systems.
2622. 1817
2623. Total amount of physical memory associated with a NUMA node in megabytes.
2624. 1819
2625. Approximate amount of physical memory on the free and zero page lists for a NUMA node, in megabytes.
2626. 1821
2627. The Network Adapter performance object consists of counters that measure the rates at which bytes and packets are sent and received over a physical or virtual network connection. It includes counters that monitor connection errors.
2628. 1823
2629. Approximate amount of physical memory on the standby page list for a NUMA node, in megabytes. This counter is available only on 64-bit systems.
2630. 1825
2631. Approximate amount of physical memory available for allocation for a NUMA node, in megabytes. Computed as the sum of memory on the zeroed, free, and standby lists for a NUMA node. This counter is available only on 64-bit systems.
2632. 1827
2633. The number of SMB BranchCache hash V2 requests that were for the header only received by the server. This indicates how many requests are being done to validate hashes that are already cached by the client.
2634. 1829
2635. The number of SMB BranchCache hash V2 generation requests that were sent by SRV2 to the SMB Hash Generation service because a client requested hashes for the file and there was either no hash content for the file or the existing hashes were out of date.
2636. 1831
2637. The number of SMB BranchCache hash V2 requests that were received by the server.
2638. 1833
2639. The number of SMB BranchCache hash V2 responses that have been sent from the server.
2640. 1835
2641. The amount of SMB BranchCache hash V2 data sent from the server. This includes bytes transferred for both hash header requests and full hash data requests.
2642. 1837
2643. The amount of SMB BranchCache hash V2 requests that were served from dedup store by the server.
2644. 1847
2645. End Marker
2646. 1901
2647. The Telphony System
2648. 1903
2649. The number of telephone lines serviced by this computer.
2650. 1905
2651. The number of telephone devices serviced by this computer.
2652. 1907
2653. the number of telephone lines serviced by this computer that are currently active.
2654. 1909
2655. The number of telephone devices that are currently being monitored.
2656. 1911
2657. The rate of outgoing calls made by this computer.
2658. 1913
2659. The rate of incoming calls answered by this computer.
2660. 1915
2661. The number of applications that are currently using telephony services.
2662. 1917
2663. Current outgoing calls being serviced by this computer.
2664. 1919
2665. Current incoming calls being serviced by this computer.
2666. 2021
2667. Counters for the Windows Search Service Gatherer Project object
2668. 2023
2669. The number of add notifications.
2670. 2025
2671. The number of document additions per second.
2672. 2027
2673. The number of delete notifications.
2674. 2029
2675. The number of document deletes per second.
2676. 2031
2677. The number of modify notifications.
2678. 2033
2679. The number of modify notifications per second.
2680. 2035
2681. 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.
2682. 2037
2683. The number of documents in progress.
2684. 2039
2685. The number of documents on hold because a document with the same URL is currently in process.
2686. 2041
2687. The number of documents delayed due to site hit frequency rules.
2688. 2043
2689. The number of files (URLs) in the history list. This indicates the total size of your document corpus that was indexed.
2690. 2045
2691. The number of documents processed since the history has been reset.
2692. 2047
2693. The number of documents processed per second.
2694. 2049
2695. The number of successfully filtered documents.
2696. 2051
2697. The number of successfully filtered documents per second.
2698. 2053
2699. The number of filtered documents which returned an error.
2700. 2055
2701. The number of filtered documents which returned an error per second.
2702. 2061
2703. The number of file protocol errors received while getting documents.
2704. 2063
2705. The number of file protocol errors received per second.
2706. 2069
2707. The number of documents accessed via file system.
2708. 2071
2709. The number of documents accessed via file system per second.
2710. 2077
2711. The number of office documents filtered.
2712. 2079
2713. The number of office documents filtered per second.
2714. 2081
2715. The number of text documents filtered.
2716. 2083
2717. The number of text documents filtered per second.
2718. 2085
2719. Number of crawls in progress.
2720. 2087
2721. The Gatherer paused flag indicates if the Gatherer has been paused.
2722. 2089
2723. The recovery in progress flag indicates if recovery is currently in progress. Indexing will not be resumed until this flag is off.
2724. 2091
2725. The number of documents which were not filtered because no modification was detected since the last crawl.
2726. 2093
2727. The Iterating history in progress flag indicates if the Gatherer is currently iterating over the URL history.
2728. 2095
2729. Number of incremental crawls in progress.
2730. 2097
2731. The number of documents currently being filtered.
2732. 2099
2733. 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.
2734. 2101
2735. The total number of times a document access has been retried. Having this number high may indicate a problem with accessing the data.
2736. 2103
2737. The number of retries per second.
2738. 2111
2739. Documents incorrectly rejected by adaptive crawl
2740. 2117
2741. Documents which have changed since the last crawl
2742. 2119
2743. The number of Move/Rename notifications.
2744. 2121
2745. The number of document Moves and Renames per second.
2746. 2123
2747. Number of unique documents in the system. Documents are considered not unique if their contents is the same.
2748. 2125
2749. Percentage of the history recovery completed
2750. 2127
2751. Counters for the Windows Search Service Gathering service object
2752. 2129
2753. Currently connected external notification sources.
2754. 2131
2755. The total number of notifications received from all notification sources excluding file system.
2756. 2133
2757. The rate of external notifications received per second.
2758. 2135
2759. The number of currently connected administrative clients.
2760. 2137
2761. 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.
2762. 2139
2763. Displays one heartbeat every 10 seconds.
2764. 2141
2765. The total number of filtering threads in the system. This number is calculated based on your system resources.
2766. 2143
2767. The number of threads waiting for documents.
2768. 2145
2769. The number of document entries currently in memory. Zero means no indexing activity is going on.
2770. 2147
2771. Indicates the level of the amount of system resources that the Gatherer service is allowed to use.
2772. 2149
2773. The number of documents waiting for robot threads. If this number is not 0, all threads should be filtering.
2774. 2151
2775. The number of filtering processes in the system.
2776. 2153
2777. The maximum number of filtering processes that have existed in the system since startup.
2778. 2155
2779. 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.
2780. 2157
2781. The number of documents delayed due to site hit frequency rules.
2782. 2159
2783. The number of servers recently accessed by the system.
2784. 2161
2785. The number of times a new server object had to be created.
2786. 2163
2787. The number of filter objects in the system. Each filter object corresponds to a URL currently being filtered.
2788. 2165
2789. The number of times a filter object was created. This corresponds to the total number of documents filtered in the system since startup.
2790. 2167
2791. The number of documents filtered per second.
2792. 2169
2793. The total number of timeouts detected by the system since startup.
2794. 2171
2795. A server becomes unavailable when a number of requests to that server time out.
2796. 2173
2797. A server becomes unavailable when a number of requests to that server time out.
2798. 2175
2799. 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.
2800. 2177
2801. The number of threads waiting for plug-ins to complete an operation.
2802. 2179
2803. The number of documents successfully filtered.
2804. 2181
2805. The number of successfully filtered documents per second.
2806. 2183
2807. 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.
2808. 2185
2809. Number of available cached word breakers instances
2810. 2187
2811. Number of available cached stemmer instances. Too many may indicate a resource usage problem.
2812. 2189
2813. The total number of notifications received from all notification sources including file system.
2814. 2191
2815. The rate of external notifications received per second.
2816. 2193
2817. System IO (disk) traffic rate in KB/s detected by back off logic
2818. 2195
2819. 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.
2820. 2197
2821. The number of threads blocked due to back off event
2822. 2199
2823. Indexer PlugIn statistics
2824. 2201
2825. The level of the master index.
2826. 2203
2827. Number of Master Merges to Date
2828. 2205
2829. Master Merge Progress
2830. 2207
2831. Shadow Merge Levels
2832. 2209
2833. Shadow Merge Levels Threshold
2834. 2211
2835. Number of Persistent Indexes
2836. 2213
2837. Size of Index
2838. 2215
2839. Number of Unique Keys
2840. 2217
2841. Number of Documents Filtered
2842. 2219
2843. Number of invalidator work items that were created
2844. 2221
2845. Number of invalidator work items that were deleted
2846. 2223
2847. Number of clean WidSets
2848. 2225
2849. Number of dirty WidSets
2850. 2227
2851. Indicator if a master merge is going on.
2852. 2229
2853. Active Connections
2854. 2231
2855. Number of Queries
2856. 2233
2857. Number of Queries Failed
2858. 2235
2859. Number of Queries Succeeded
2860. 2237
2861. The number of L0 Indexes (Wordlists)
2862. 2239
2863. The number of L0 merges (flushes) in progress at any one moment.
2864. 2241
2865. The average value [documents/hour] computed for the speed of L0 merges (flushes) since the catalog has been loaded
2866. 2243
2867. The number of L0 merges (flushes) since the catalog was loaded
2868. 2245
2869. The last value [documents/hour] computed for the speed of L0 merges (flushes).
2870. 2247
2871. The number of L1 Indexes
2872. 2249
2873. The number of L1 merges in progress at any one moment.
2874. 2251
2875. The average value [documents/hour] computed for the speed of L1 merges since the catalog has been loaded
2876. 2253
2877. The number of L1 merges since the catalog was loaded
2878. 2255
2879. The last value [documents/hour] computed for the speed of L1 merges.
2880. 2257
2881. The number of L2 Indexes
2882. 2259
2883. The number of L2 merges in progress at any one moment.
2884. 2261
2885. The average value [documents/hour] computed for the speed of L2 merges since the catalog has been loaded
2886. 2263
2887. The number of L2 merges since the catalog was loaded
2888. 2265
2889. The last value [documents/hour] computed for the speed of L2 merges.
2890. 2267
2891. The number of L3 Indexes
2892. 2269
2893. The number of L3 merges in progress at any one moment.
2894. 2271
2895. The average value [documents/hour] computed for the speed of L3 merges since the catalog has been loaded
2896. 2273
2897. The number of L3 merges since the catalog was loaded
2898. 2275
2899. The last value [documents/hour] computed for the speed of L3 merges.
2900. 2277
2901. The number of L4 Indexes
2902. 2279
2903. The number of L4 merges in progress at any one moment.
2904. 2281
2905. The average value [documents/hour] computed for the speed of L4 merges since the catalog has been loaded
2906. 2283
2907. The number of L4 merges since the catalog was loaded
2908. 2285
2909. The last value [documents/hour] computed for the speed of L4 merges.
2910. 2287
2911. The number of L5 Indexes
2912. 2289
2913. The number of L5 merges in progress at any one moment.
2914. 2291
2915. The average value [documents/hour] computed for the speed of L5 merges since the catalog has been loaded
2916. 2293
2917. The number of L5 merges since the catalog was loaded
2918. 2295
2919. The last value [documents/hour] computed for the speed of L5 merges.
2920. 2297
2921. The number of L6 Indexes
2922. 2299
2923. The number of L6 merges in progress at any one moment.
2924. 2301
2925. The average value [documents/hour] computed for the speed of L6 merges since the catalog has been loaded
2926. 2303
2927. The number of L6 merges since the catalog was loaded
2928. 2305
2929. The last value [documents/hour] computed for the speed of L6 merges.
2930. 2307
2931. The number of L7 Indexes
2932. 2309
2933. The number of L7 merges in progress at any one moment.
2934. 2311
2935. The average value [documents/hour] computed for the speed of L7 merges since the catalog has been loaded
2936. 2313
2937. The number of L7 merges since the catalog was loaded
2938. 2315
2939. The last value [documents/hour] computed for the speed of L7 merges.
2940. 2317
2941. The number of L8 Indexes
2942. 2319
2943. The number of L8 merges in progress at any one moment.
2944. 2321
2945. The average value [documents/hour] computed for the speed of L8 merges since the catalog has been loaded
2946. 2323
2947. The number of L8 merges since the catalog was loaded
2948. 2325
2949. The last value [documents/hour] computed for the speed of L8 merges.
2950. 2327
2951. Database provides performance statistics for each process using the ESE high performance embedded database management system.
2952. 2329
2953. Pages Converted/sec is the number of times per second a database page is converted from an older database format. [Dev Only]
2954. 2331
2955. Pages Converted is the number of database pages that have been converted from an older format. [Dev Only]
2956. 2333
2957. Records Converted/sec is the number of times per second a database record is converted from an older database format. [Dev Only]
2958. 2335
2959. Records Converted is the number of database records that have been converted from an older format [Dev Only]
2960. 2337
2961. Defragmentation Tasks is the count of background database defragmentation tasks that are currently executing.
2962. 2339
2963. Defragmentation Tasks Pending is the count of background database defragmentation tasks that are currently pending.
2964. 2341
2965. Defragmentation Tasks Postponed is the count of background database defragmentation tasks that could not be registered for imminent execution, and have been persisted in a table for later execution. [Dev Only]
2966. 2343
2967. Defragmentation Tasks Scheduled/sec is the number of background database defragmentation tasks scheduled for execution per second. [Dev Only]
2968. 2345
2969. Defragmentation Tasks Completed/sec is the number of background database defragmentation tasks completing execution per second. [Dev Only]
2970. 2347
2971. Heap Allocs/sec is the number of memory allocations from the MP Heaps per second. [Dev Only]
2972. 2349
2973. Heap Frees/sec is the number of memory frees to the MP Heaps per second. [Dev Only]
2974. 2351
2975. Heap Allocations is the current number of memory allocations in the MP Heaps. [Dev Only]
2976. 2353
2977. Heap Bytes Allocated is the size of all memory allocations in the MP Heaps discounting heap managemnt overhead. [Dev Only]
2978. 2355
2979. Page Bytes Reserved is the size of all explicitly reserved virtual address space. [Dev Only]
2980. 2357
2981. Page Bytes Committed is the size of all explicitly committed virtual memory backing store (page file and physical memory). [Dev Only]
2982. 2359
2983. FCB Async Scan/sec is the number of cached schema records (FCBs) scanned during asynchronous schema record cleanup. These records are scanned to age out older schema definitions. [Dev Only]
2984. 2361
2985. FCB Async Purge/sec is the number of cached schema records (FCBs) purged during asynchronous schema record cleanup. These records are purged to age out older schema definitions. [Dev Only]
2986. 2363
2987. FCB Async 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]
2988. 2365
2989. FCB Async 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]
2990. 2367
2991. FCB Async Threshold Purge Failures (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]
2992. 2369
2993. FCB Async Threshold Purge Failures (In Use)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record being in use. [Dev Only]
2994. 2371
2995. FCB Async Threshold Purge Failures (Sentinel)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record being a sentinel record. [Dev Only]
2996. 2373
2997. FCB Async Threshold Purge Failures (Delete Pending)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record being pending delete. [Dev Only]
2998. 2375
2999. FCB Async Threshold Purge Failures (Outstanding Versions)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record having outstanding versions. [Dev Only]
3000. 2377
3001. FCB Async Threshold Purge Failures (LV Outstanding)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the LV of the record being outstanding. [Dev Only]
3002. 2379
3003. FCB Async Threshold Purge Failures (Index Outstanding)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the index of the record being outstanding. [Dev Only]
3004. 2381
3005. FCB Async Threshold Purge Failures (Active Tasks)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record having active tasks. [Dev Only]
3006. 2383
3007. FCB Async Threshold Purge Failures (Callbacks)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record having callbacks. [Dev Only]
3008. 2385
3009. FCB Async Threshold Purge Failures (Other)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to other reasons. [Dev Only]
3010. 2387
3011. FCB Async Purge Failures (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]
3012. 2389
3013. FCB Async Purge Failures (In Use)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record being in use. [Dev Only]
3014. 2391
3015. FCB Async Purge Failures (Sentinel)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record being a sentinel record. [Dev Only]
3016. 2393
3017. FCB Async Purge Failures (Delete Pending)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record being in pending delete state. [Dev Only]
3018. 2395
3019. FCB Async Purge Failures (Outstanding Versions)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record having outstanding versions. [Dev Only]
3020. 2397
3021. FCB Async Purge Failures (LV Outstanding)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the LV of the record being outstanding. [Dev Only]
3022. 2399
3023. FCB Async Purge Failures (Index Outstanding)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the index of the record being outstanding. [Dev Only]
3024. 2401
3025. FCB Async Purge Failures (Active Tasks)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record having active tasks. [Dev Only]
3026. 2403
3027. FCB Async Purge Failures (Callbacks)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to the record having callbacks. [Dev Only]
3028. 2405
3029. FCB Async Purge Failures (Other)/sec is the number of failed purge attempts on cached schema records (FCBs) during asynchronous schema record cleanup due to other reasons. [Dev Only]
3030. 2407
3031. FCB Sync Purge/sec is the number of cached schema records (FCBs) being synchronously purged each second. [Dev Only]
3032. 2409
3033. FCB Sync Purge Stalls/sec is the number of stalls encountered while waiting for exclusive ownership of cached schema records (FCBs) in order to synchronously purge them. [Dev Only]
3034. 2411
3035. 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]
3036. 2413
3037. 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]
3038. 2415
3039. FCB Cache % Hit is the percentage of schema records (FCBs) opened directly from the schema record cache. No file operations were required. [Dev Only]
3040. 2417
3041. No text
3042. 2419
3043. 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]
3044. 2421
3045. FCB Cache Maximum is the absolute maximum number of the schema records (FCBs) that can exist in the cache. [Dev Only]
3046. 2423
3047. FCB Cache Preferred is the preferred maximum number of the schema records (FCBs) that should exist in the cache. [Dev Only]
3048. 2425
3049. FCB Cache Allocated is the number of cached schema records (FCBs) currently allocated. [Dev Only]
3050. 2427
3051. FCB Cache Allocated/sec is the number of cached schema records (FCBs) currently allocated per second. [Dev Only]
3052. 2429
3053. 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]
3054. 2431
3055. FCB Attached RCEs is the number of revision control entries (RCEs) attached to cached schema records (FCBs) [Dev Only]
3056. 2433
3057. Sessions In Use is the number of database sessions currently open for use by client threads.
3058. 2435
3059. Sessions % Used is the percentage of database sessions currently open for use by client threads.
3060. 2437
3061. No text
3062. 2439
3063. Resource Manager FCB Allocated indicates the amount of memory in Bytes of allocated FCBs [Dev Only]
3064. 2441
3065. Resource Manager FCB Allocated Used indicates the amount of memory in Bytes of allocated and used FCBs [Dev Only]
3066. 2443
3067. Resource Manager FCB Quota indicates the maximum amount of memory in Bytes for FCBs [Dev Only]
3068. 2445
3069. Resource Manager FUCB Allocated indicates the amount of memory in Bytes of allocated FUCBs [Dev Only]
3070. 2447
3071. Resource Manager FUCB Allocated Used indicates the amount of memory in Bytes of allocated and used FUCBs [Dev Only]
3072. 2449
3073. Resource Manager FUCB Quota indicates the maximum amount of memory in Bytes for FUCBs [Dev Only]
3074. 2451
3075. Resource Manager TDB Allocated indicates the amount of memory in Bytes of allocated TDBs [Dev Only]
3076. 2453
3077. Resource Manager TDB Allocated Used indicates the amount of memory in Bytes of allocated and used TDBs [Dev Only]
3078. 2455
3079. Resource Manager TDB Quota indicates the maximum amount of memory in Bytes for TDBs [Dev Only]
3080. 2457
3081. Resource Manager IDB Allocated indicates the amount of memory in Bytes of allocated IDBs [Dev Only]
3082. 2459
3083. Resource Manager IDB Allocated Used indicates the amount of memory in Bytes of allocated and used IDBs [Dev Only]
3084. 2461
3085. Resource Manager IDB Quota indicates the maximum amount of memory in Bytes for IDBs [Dev Only]
3086. 2463
3087. 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.
3088. 2465
3089. No text
3090. 2467
3091. 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.
3092. 2469
3093. 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.
3094. 2471
3095. Table Open Pages Read/sec is the number of database pages read without using cached schema information per second. If this rate is too high, the table cache size may be too small. [Dev Only]
3096. 2473
3097. Table Open Pages Preread/sec is the number of database pages pre-read without using cached schema information per second. If this rate is too high, the table cache size may be too small. [Dev Only]
3098. 2475
3099. Table Opens/sec is the number of database tables opened per second.
3100. 2477
3101. Table Closes/sec is the number of database tables closed per second.
3102. 2479
3103. Tables Open is the number of database tables opened.
3104. 2481
3105. Log Bytes Write per second is the rate bytes are written to the log.
3106. 2483
3107. Log Bytes Generated per second is the rate at which data is added to the log. This is different from Log Bytes Write per second in that each byte is generated only once whereas each byte may be written many times.
3108. 2485
3109. Log Buffer Bytes Used is the amount of bytes in the log buffers that have not yet been flushed to the logs. [Dev Only]
3110. 2487
3111. Log Buffer Bytes Free is the amount of free space available in the log buffers. [Dev Only]
3112. 2489
3113. Log Buffer Bytes Committed is total number of committedbytes of log buffer. [Dev Only]
3114. 2491
3115. 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.
3116. 2493
3117. 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]
3118. 2495
3119. 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]
3120. 2497
3121. Log Checkpoint Maintenance Outstanding IO Max represents how aggressive, in terms of outstanding IOs, the database engine will be to maintain the preferred checkpoint. This is a function of how far the checkpoint has fallen behind. [Dev Only]
3122. 2499
3123. 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]
3124. 2501
3125. User Read/Write Transaction Commits to Level 0 (Durable)/sec is the count of fully committed transactions started by the calling process that modify data stored in the database engine. [Dev Only]
3126. 2503
3127. User Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of transactions started by the calling process and committed to log buffer. [Dev Only]
3128. 2505
3129. User Wait All Transaction Commits/sec is the count of signals to flush all pending transactions started by the calling process that modify data stored in the database engine. [Dev Only]
3130. 2507
3131. User Wait Last Transaction Commits/sec is the count of signals to flush a specific sessions pending transactions. [Dev Only]
3132. 2509
3133. 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]
3134. 2511
3135. 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]
3136. 2513
3137. 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]
3138. 2515
3139. 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]
3140. 2517
3141. 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]
3142. 2519
3143. System Read/Write Transaction Commits to Level 0 (Durable)/sec is the count of fully committed transactions started internally that modify data stored in the database engine. [Dev Only]
3144. 2521
3145. System Read/Write Transaction Commits to Level 0 (Lazy)/sec is the count of internal transactions committed to log buffer. [Dev Only]
3146. 2523
3147. 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]
3148. 2525
3149. 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]
3150. 2527
3151. 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]
3152. 2529
3153. 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]
3154. 2531
3155. Recovery stalls for Readonly transactions is the number of times recovery had to pause to allow an older read-only transaction to complete. [Dev Only]
3156. 2533
3157. Recovery long stalls for Readonly transactions is the number of times recovery had to pause for an extended time to allow an older read-only transaction to complete. [Dev Only]
3158. 2535
3159. Total time for Recovery stalls for Readonly transactions (ms) is the total amount of time (in milliseconds) recovery had to pause to allow an older read-only transaction to complete. [Dev Only]
3160. 2537
3161. Recovery Throttles For IO Smoothing is the number of times recovery had to pause to not recover a file faster than it was generated. [Dev Only]
3162. 2539
3163. Total Time For Recovery Throttles For IO Smoothing (ms) is the total amount of time (in milliseconds) recovery had to pause to not recover a file faster than it was generated. [Dev Only]
3164. 2541
3165. 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]
3166. 2543
3167. Database Page Allocation File Extension Stalls/sec is the rate of attempts to extend the database file that stall. [Dev Only]
3168. 2545
3169. Database Page Allocation File Shrink Stalls/sec is the rate of attempts to shrink the database file that stall. [Dev Only]
3170. 2547
3171. Log Records/sec is the count of records written to the database log buffers per second. [Dev Only]
3172. 2549
3173. 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]
3174. 2551
3175. 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]
3176. 2553
3177. Log Buffer Flushes Skipped/sec is the count of times the database log buffers were intended to be flushed, but we skipped it due to the desired log data already having been flushed. [Dev Only]
3178. 2555
3179. Log Buffer Flushes Blocked/sec is the count of times the database log buffers were intended to be flushed, but we skipped it due to the log buffer being locked for and being flushed by another thread. [Dev Only]
3180. 2557
3181. Log Buffer Flushes/sec is the count of times the database log buffers must be flushed per second. [Dev Only]
3182. 2559
3183. 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.
3184. 2561
3185. Log Full Segment Writes/sec is the number of times full log segments are written to the log file(s) per second. [Dev Only]
3186. 2563
3187. Log Partial Segment Writes/sec is the number of times that a log segment that is only partially full of data is written to the log file(s) per second. [Dev Only]
3188. 2565
3189. Log Bytes Wasted/sec is the number of bytes wasted by not reusing a partially flushed sector (and instead fill it up with NOPs). [Dev Only]
3190. 2567
3191. 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.
3192. 2569
3193. Version Buckets Allocated is the total number of version buckets allocated.
3194. 2571
3195. Total number of version buckets allocated for FlagDelete RCEs [Dev Only]
3196. 2573
3197. 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]
3198. 2575
3199. Average length of bookmark in RCE [Dev Only]
3200. 2577
3201. 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]
3202. 2579
3203. Number of times per second a version store clean task is dispatched asynchronously to be performed [Dev Only]
3204. 2581
3205. Number of times per second a version store clean task is performed synchronously [Dev Only]
3206. 2583
3207. Number of times per second a version store clean task was discarded due to load concerns [Dev Only]
3208. 2585
3209. Number of times per second a dispatched version store cleanup task fails [Dev Only]
3210. 2587
3211. Record Inserts/sec is the rate at which records are being inserted into database tables. [Dev Only]
3212. 2589
3213. Record Deletes/sec is the rate at which records in database tables are being flagged for deletion. [Dev Only]
3214. 2591
3215. Record Replaces/sec is the rate at which records in database tables are being updated. [Dev Only]
3216. 2593
3217. 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]
3218. 2595
3219. 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]
3220. 2597
3221. Record Escrow-Updates/sec is the rate at which records in database tables are being escrow-updated. [Dev Only]
3222. 2599
3223. Secondary Index Inserts/sec is the rate at which entries are being inserted into indexes of database tables. [Dev Only]
3224. 2601
3225. Secondary Index Deletes/sec is the rate at which entries in indexes of database tables are being flagged for deletion. [Dev Only]
3226. 2603
3227. 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]
3228. 2605
3229. 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]
3230. 2607
3231. 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]
3232. 2609
3233. Record Separated Long-Values Added/sec is the rate at which separated long-values are normally added to records of database tables. [Dev Only]
3234. 2611
3235. 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]
3236. 2613
3237. 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]
3238. 2615
3239. 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]
3240. 2617
3241. 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]
3242. 2619
3243. Separated Long-Value Seeks/sec is the rate at which seeks for a separated long-value in a database table are performed. [Dev Only]
3244. 2621
3245. Separated Long-Value Retrieves/sec is the rate at which retrievals of a separated long-value in a database table are performed. [Dev Only]
3246. 2623
3247. Separated Long-Value Creates/sec is the rate at which new separated long-values are added to a database table. [Dev Only]
3248. 2625
3249. Long-Value Maximum LID is the largest LID that has been used by the database engine. [Dev Only]
3250. 2627
3251. Separated Long-Value Updates/sec is the rate at which existing separated long-values in a database table are modified. [Dev Only]
3252. 2629
3253. Separated Long-Value Deletes/sec is the rate at which separated long-values in a database table are flagged for deletion. [Dev Only]
3254. 2631
3255. Separated Long-Value Copies/sec is the rate at which existing separated long-values in a database table are copied. [Dev Only]
3256. 2633
3257. 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]
3258. 2635
3259. 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]
3260. 2637
3261. Separated Long-Value Chunk Appends/sec is the rate at which chunks are appended to separated long-values of database tables. [Dev Only]
3262. 2639
3263. Separated Long-Value Chunk Replaces/sec is the rate at which existing separated long-value chunks in a database table are replaced. [Dev Only]
3264. 2641
3265. 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]
3266. 2643
3267. Separated Long-Value Chunk Copies/sec is the rate at which existing separated long-value chunks in a database table are copied. [Dev Only]
3268. 2645
3269. B+ Tree Append Splits/sec is the count of times a page is appended to a database B+ Tree per second. [Dev Only]
3270. 2647
3271. B+ Tree Right Splits/sec is the count of times a page is split right in a database B+ Tree per second. [Dev Only]
3272. 2649
3273. 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]
3274. 2651
3275. B+ Tree Vertical Splits/sec is the count of times a page is split vertically in a database B+ Tree per second. [Dev Only]
3276. 2653
3277. 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]
3278. 2655
3279. B+ Tree Empty Page Merges/sec is the count of empty pages removed from a database B+ Tree per second. [Dev Only]
3280. 2657
3281. 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]
3282. 2659
3283. 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]
3284. 2661
3285. B+ Tree Left Merges/sec is the count of pages removed from a database B+ Tree per second by moving all its records to the previous page to the left. [Dev Only]
3286. 2663
3287. B+ Tree Partial Left Merges/sec is the count of pages where some of its records are moved to a page on the left in a database B+ Tree per second. [Dev Only]
3288. 2665
3289. B+ Tree Page Moves/sec is the count of B+ Tree pages per second where all the records are moved to a new page. [Dev Only]
3290. 2667
3291. B+ Tree Merges/sec is the count of pages merged in a database B+ Tree per second. [Dev Only]
3292. 2669
3293. 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]
3294. 2671
3295. 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]
3296. 2673
3297. B+ Tree Opportune Preread