|
Alternatives to slow requests that are saturating the thread pool: msg#00099windows.devel.dotnet.web
Hi I have slow request that are saturating the thread pool because these request are invoking a slow web service too. To try resolve it I have read that there are two solutions: 1) I could change the upper limit of the thread pool. I'm understand it. 2) Using asynchronous handlers. Create my own thread pool, allocate distinct threads to service them, freeing up the original thread pool thread to service additional requests. I don't understand well this second solution. Where is the advantage with the first one? It seems poor because there is a more code to execute. Thanks in advance Javier =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: When a request arrive to aspnet which kind of thread is used?: 00099, Adam Tuliper |
|---|---|
| Next by Date: | Re: Alternatives to slow requests that are saturating the thread pool: 00099, Ian Griffiths |
| Previous by Thread: | Re: When a request arrive to aspnet which kind of thread is used?i: 00099, Adam Tuliper |
| Next by Thread: | Re: Alternatives to slow requests that are saturating the thread pool: 00099, Ian Griffiths |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |