I am developing an ASP.NET web forms that will talk to IIS 7.0 (WAS & application pool). I read that if the IIS receive requests and the WCF service is busy with a previous request, it will start up another worker thread to process the user request so that the user do not have to wait for a long time and time out..
How do I configure or code the IIS to get a good acceptable timing response? what is an acceptable time response? Beside buying load balance hardware and software, can I just configure the IIS to instantiate up to a max number of additiona worker thread of that popular WCF service in the application pool to process all the requests to avoid the request just sitting in the queue for too long?
Any help is greatly appreciated...
View Complete Post