Thad,
Look at it this way: the output is telling you, that for the timeframe you logged, your Fast Threads are waiting, on average, 1.1 seconds between calls. and your List Threads are all waiting about 2.5 seconds. now, there are periods of time when the system is really crunching, and there's very little idle time (the MIN values). but, for the most part (the AVG), they're acting like they've got all the time in the world (if you live in a world of nanoseconds as CPU's do.). Not knowing anything else about your system (like how long of a snapshot this covered, how many users were logged in, how many CPUs do you use, how much RAM, and several other factors), I'd say that it is a healthy system. However, as I just pointed out, there are other factors that weigh into that, which are, to us, the peanut gallery, an unknown. So, long story short. the AVG is what I'd really watch. :-) (although, if you note the MIN times on the List threads, you'll note that 6 of the 8 went through a period of time where the calls to them were right on top of each other (0.0000 MIN Idle Time = no rest for the wicked!), so it might be worth looking at the API and SQL logs in detail to see what was pinging them so heavily during that timeframe. Good luck! Matt R. _____ From: Thad Esser [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 30, 2007 1:17 PM To: [email protected] Subject: ARLogAnalyzer output ** Hello, I haven't had much occasion to use the log analyzer very much, and I want to make sure I'm interpreting the results correctly as part of thread tuning. In determining if I need to increase my threads, which column is more important, the "AVG Idle Time" or the "MIN Idle Time"? I can see it either way and was hoping someone would share their experience. Thanks, Thad API STATISTICS BY THREAD ID Queue Thread Count Gaps MIN Idle Time MAX Idle Time AVG Idle Time Total Idle Time ---------- ---------- ------- ------- -------------- -------------- -------------- --------------- Admin 001772 83 83 0.0150 46:01.6220 55.6344 1:16:57.6600 Fast 000744 4,015 4,014 0.0150 17.8430 1.1034 1:13:49.3890 Fast 001432 3,977 3,976 0.0160 19.1870 1.1128 1:13:44.7590 Fast 001784 3,988 3,987 0.0160 12.8110 1.1131 1:13:57.9920 Fast 001956 3,868 3,867 0.0000 13.4830 1.1428 1:13:39.5520 Fast 002264 3,970 3,969 0.0160 12.8280 1.1217 1:14:12.0360 Fast 003660 3,983 3,982 0.0150 19.5150 1.1154 1:14:01.7290 Fast 003832 3,950 3,949 0.0160 12.8120 1.1145 1:13:21.3690 List 001284 1,478 1,477 0.0310 19.9840 2.6610 1:05:30.3070 List 001508 1,684 1,683 0.0000 14.8270 2.4314 1:08:12.1150 List 001580 1,384 1,383 0.0620 14.4050 2.6266 1:00:32.6020 List 001616 1,523 1,522 0.0000 16.1870 2.4974 1:03:21.1640 List 001732 1,519 1,518 0.0000 13.9830 2.5307 1:04:01.7340 List 001752 1,454 1,453 0.0000 13.0150 2.5978 1:02:54.6550 List 001924 1,499 1,498 0.0000 14.2340 2.5749 1:04:17.3310 List 001952 1,565 1,564 0.0000 14.4370 2.4932 1:04:59.4360 ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
