David
Sun Jun 22 22:32:10 CDT 2008
On Jun 19, 2:13=A0am, "Anish Mackan" <anish mac...@SYNLOG.CO.UK> wrote:
> Hi, got an ASP.NET 2.0 application, that evry so often, causes the number=
of
> threads used by a w3wp process to rapidly ncrease to over 150!!
>
> I have configured the site with 3 worke process (web garden). Server is t=
win
> Dual core 3GHZ with 4GB Ram running W2K3R2
> When we find that that the threads have gone over 50-60, we also notice t=
hat
> the users experience slowness. If i recycle the app pool service the site=
,
> after about 2 mins it runs fine, until the next time.
>
> Any ideas where to look.
>
> Thanks
Look for the problem within your application. Your observation of
thread-count is merely a symptom, and recycling is a temporary
bandaid.
You can use a debugger to determine at the time of many threads, what
each of them are doing. That can give clues to what to do next.
You can also use Visual Studio's F1 Profiler to tune hot paths to
lower contention and speed things up, but you have to first identify
the hot paths.
Simplify the problem by removing the web garden (use # worker process
at 1).
I suspect you have both a performance and scalability problem, and you
tried to get around the performance bottleneck with Web Garden but
that's not the solution as you still have issues. Now you really need
to solve your performance bottleneck.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//