Thread Pool

[Guest]

Hi,

In ASP.NET applications, the .NET framework maintains a thread pool to
process user requests by default this value is 25.

1) Whether this pool is managed by IIS? If we increase the size to 30 what
impact it will cause on IIS?

2) Suppose if I create three threads from my ASP.NET application and whether
these three threads invoke three threads in IIS?

My major concern is creating a custom thread pool a step before the .NET
framework thread pool to handle asynchronous calls where the processing time
is not known is a good idea or not?

Please suggest...

Thanks,
Abhishek

 

[Lloyd Dupont]

--
Regards,
Lloyd Dupont
NovaMind Software
Mind Mapping at its best
www.nova-mind.com

 

[Lloyd Dupont]

In ASP.NET applications, the .NET framework maintains a thread pool to

process user requests by default this value is 25.

1) Whether this pool is managed by IIS? If we increase the size to 30 what
impact it will cause on IIS?

well if you have that may concureent queryr, it would just slow down the 1st
25 to execute the extra 5...

2) Suppose if I create three threads from my ASP.NET application and
whether
these three threads invoke three threads in IIS?

what is the question?
just in case let's the thread you will use are the one you created....

the scheduler don't care much about which process the thread is in...

My major concern is creating a custom thread pool a step before the .NET
framework thread pool to handle asynchronous calls where the processing
time
is not known is a good idea or not?

maybe you need to use non pooled thread?
a thread pool is good in case of many concurent and relatively homogeneous
query.

but if you want to run 100 short and 100 long concurent query all in the
same thread pool the long query might get executed first and then you've got
to wait for the short queries.

so when you know you are going to have a long query create a thread
explicitely for it.

 

[Guest]

Thanks for your reply...

Non pooled thread is a good option to handle user requests, create an
individual thread for every request, but is there any limitiation to the
number of threads that I can create in an application or it can grow as many
as i want.

One thing i noticed in the non thread pool approach is the CPU consumption
grows near upto 100%. Is there any way so that I can reduce it...

Please suggest...

Thanks,
Abhishek