Last post May 05, 2014 05:38 AM by Ericzh
Apr 29, 2014 10:34 AM|doodar|LINK
We have an issue with a .net2 asmx web service running on Windows 2008 R2 SP1, IIS7.5, x64.
Calls to the web service take 15-17 seconds to complete for EACH AND EVERY request. In test the same calls take 1-2 seconds. When called from localhost the web service returns in 1-2 seconds.
Network and SQL trace captures appear to have ruled out these as the cause and a data collector set that is tracing the asp.net events appears to be backing this up indicating that the delay is incurred during the mapping of the handler and then again during
the execution of the handler.
The exact same symptoms are present for all instances of the web services on the machine.
Here are the results of a SOAP POST to the .asmx captured in a Data Collector Set that is tracing asp.net events. See delay in mapping the handler. I removed some class identifiers:
A very similar delay is experienced on each and every visit to the .asmx page through a browser too. I set up a test virtual dir on the same box and enabled tracing (localOnly=false) and this is what it is capturing (on every request):
and here is the Data Collector Trace for the GET request through a browser which shows delays at the same events but also a little more information in teh Execution event, although the delay has already occurred at that point:
Could anyone suggest a configuration setting that could be causing this delay? Such as caching or recompile?
Are there any counters or other data collector event traces that would shed light?
May 05, 2014 05:38 AM|Ericzh|LINK
It seems that eight seconds startup is pretty standard for the first request at application start.
You may wish to look into
ASP.NET Precompilation which may help you. Besides, you could also refer to: