I am running a rest interface(using ApiController class) using the ASP.NET 4.6 and IIS 7.5. The rest interfaces are making a WCF asynch call out to a web service to log all the incoming and outgoing request and response strings for tracking purposes. The C# code is accessing an Oracle database using the ODP.net 4.112.3.0.
Under normal load everything works fine on the site in production. However, when a huge spike in traffic comes (14k requests within 10 minutes) we start to see long response times from the initial request/response logging web service we have and then we see database timeouts. The database team sees no connection issues on the db server. I know the async logging WCF calls get pushed to the CLR threads to be run. My question is are the threads in IIS that are being used to make the outbound wcf asynch web service call the same threads that are used to access the database and thus causing the database timeouts? If so how can I determine what the max threads are on each machine and how to optimize the usage of the threads?
</div> </div>