Re: Async Pages and Thread Pools

Kevin

Many thanks for the response.

"Kevin Spencer" <unclechutney@localhost> wrote in message
news:ux9hP0kaIHA.536@xxxxxxxxxxxxxxxxxxxxxxx
The advantage of Asynch ASP.Net pages is seen when the number of
concurrent requests exceeds the number of available request-processing
threads in the thread pool. The size of the thread pool is limited, and if
exceeded, successive requests can be delayed, or if there are enough
requests, some may eventually time out waiting for a thread, resulting in
a "503 Server Unavailable" error from the server. Asynch ASP.Net pages
return the request-processing thread to the thread pool immediately, using
another thread to do the actual processing. When the processing is
completed, another request-processing thread is grabbed to return the
Response to the client.

So, if we have an IIS thread pool size of 25 and 25 requests are made that
involve intensive IO, other requests (for inexpensive resources that
*should* be served very quickly) will not be served until at least one of
the other threads is freed up. If we use asynchronous page processing, we
hand off processing of the intensive IO operations to threads outside the
IIS thread pool, thus freeing up threads from the IIS thread pool to service
other requests.

What I don't understand is what benefit using asynchronous page processing
has over simply increasing the number of threads in the IIS thread pool. Why
does it matter whether threads are taken from the IIS thread pool or not?

[..]

http://msdn.microsoft.com/msdnmag/issues/05/10/WickedCode/

A useful resource, thanks.

--
Regards

Chris Marsh


.

Relevant Pages

  • Re: Async Pages and Thread Pools
    ... Microsoft MSDN Online Support Lead ... concurrent requests exceeds the number of available request-processing ... threads in the thread pool. ...
    (microsoft.public.dotnet.framework)
  • Re: Heap fragmentation caused by .NET remoting (TcpServerSocket)
    ... > I'm looking at a remote call to my server and the buffer is pinned until ... > thread pool is overloaded and the server requests are being starved. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: How to make time-costing web service Asynchronous?
    ... I once configured to implement it as Asynchronous webmethod. ... Well, one solution would be to create your own thread pool, independent from the main application thread pool, and use that to service your requests. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: BizTalk 2004 SOAP Adapter Tuning, ThreadPool
    ... Search BizTalk documentation for "HTTP Adapter Configuration and Tuning ... all HTTP requests are consuming threads from the same thread pool. ... HTTP requests does not refer only to HTTP adapter requests, ...
    (microsoft.public.biztalk.general)
Loading