Geeks With Blogs

Scott Kuhl Warning: I may have no idea what I am talking about!
Reduce the chances of generating the dreaded 503 error—"Site Too Busy"—by implementing asynchronous processing with ASP.NET 2.0.
I measured the effects of tying up a thread by creating a test client that issued 50 simultaneous requests to an ASP.NET page that, in turn, called a Web Service. The average response time for those 50 requests was more than eight seconds as new requests waited for threads tied up by old requests to become available.
The solution is to implement asynchronous processing. Doing so means your page's thread is returned to the thread pool, so another page can use it while your own code waits for results. When the remote server returns its results, a new thread picks up from where your page left off. The average response time for a new set of 50 calls by the client fell to less than two seconds when I switched my test page to asynchronous processing.

Read Build More Scalable Sites

Posted on Thursday, August 31, 2006 5:43 AM ASP.NET , Architecture | Back to top


Comments on this post: Build More Scalable Sites

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Scott Kuhl | Powered by: GeeksWithBlogs.net