RE: threads
- From: smarty <smarty@xxxxxxxxxxxxx>
- Date: Sat, 9 Dec 2006 04:08:00 -0800
Hi Steven,
I am looking to monitor similar thread counters for a web service and HTTP
application. For these I would like to know how many threads are being used
by each application and how many are still available.
This will allow me to see if any thread blocking is affecting performance
and if the thread pool needs to be increased.
"Steven Cheng[MSFT]" wrote:
Hello smarty,.
As for the "web service" you mentioned, is it an ASP.NET web application or
webservice application or a native IIS web service?
For the two questions you mentioned, here are my understanding and
suggestion:
Q1. What is the difference between process:inetinfo:thread count and
process:w3wp:thread count?
==================================
Inetinfo.exe is the IIS service's main process, however, for ASP.NET
application, it is always hosted in another process. For IIS5, its
aspnet_wp.exe, for IIS6, it is w3wp.exe
Q2. Is this the right counter to measure threads in use?
===================================
Do you want to get the thread numbers available for processing the ASP.NET
requests or the total threads number in the ASP.NET's worker process?
for ASP.NET request processing, the runtime will always use pooled thread
from .NET CLR's managed thread pool( rather than normal thread) to process
client requests. the "process" counter's thread count is the total
operating thread number. Here is a very good article introducing ASP.NET
threading model:
#Microsoft ASP.NET Threading
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/en/tra
nscripts/wct060503.asp
Also, you can create a custom counter for pickup the ASP.NET managed thread
pool status:
#How To: Monitor the ASP.NET Thread Pool Using Custom Counters
http://msdn2.microsoft.com/en-us/library/ms979194.aspx
Hope this helps.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
- Follow-Ups:
- RE: threads
- From: Steven Cheng[MSFT]
- RE: threads
- References:
- RE: threads
- From: Steven Cheng[MSFT]
- RE: threads
- Prev by Date: Re: performance of dual core processors for .NET
- Next by Date: RE: threads
- Previous by thread: RE: threads
- Next by thread: RE: threads
- Index(es):
Relevant Pages
|
Loading