Long server response time for Web Server and ASP.NET APIs
Hello,
I am seeing high response times for my web requests and dT is showing that its time spent in either the Web Server or ASP.NET API component.
Can dT tell me why so much time is spent on either one of these tiers??
For the dT session I attached, it takes 26.9 seconds, and the response was only 52KB. Our response times at the 90th percentile have tripled on this request since our latest release.
Atlas-QA-slowdownloaddocument2.dts
Here's a session of one call that spends 26.9 seconds on the ASP.NET API tier. I'm pulling my hair out trying to figure out why 
**fr000383.xml (Failed Request Trace for this session says its only taking 8736ms) Why does dT report 26.9 seconds?
I would think it's safe to say that this is on some document retrieval call to a backend service like Documentum actually holding the images/docs whatever. Why? Because it is only these types of transactions which seem to be slow. Maybe someone else can look at the session you've attached and give more insight.
Rick B
Sorry, two of your examples had long time in .NET and one had long time in Web Server, but by your Method Hotspots it looks like it's overwhelmingly by ASP.NET. Looks like the URLs are doing some document retrieval, is it possible these are just large files and this is standard performance? The PurePaths you've shown so far last about 2-3 seconds. Can you export a slow PurePath and attach it here?
Rick B
Hi Richard,
I've enabled FRT on one of my PROD web servers and for most of the requests, there is almost no time spent in any of the IIS modules at all. Example attachment below. When I look at response time hotspots, I see that most of the time is spent on the ASP.NET API. And the methods that are slow are all .NET framework methods. How can I figure out why these methods are slow??
Hi Melanie,
Looks like others have had success in looking at the IIS Failed Request Tracing data to understand why time was spent in the Web Server.
