Recently, we assisted a customer who was facing slowness issues with their classic ASP web application. However, we encountered some unusual behavior. Despite detecting a slowdown of over 15 seconds in the IIS logs, the Failed Request Tracing logs did not generate any data for the "Time taken" field. To identify the root cause of the issue, we collected Perfview ETW for the classic ASP application, allowing us to load all the events and identify the modules and events that were taking the longest time to load during the problem.
Here are the steps we followed :
Note: Do not run this trace for more than 1-2 minutes:
Once we open the events section of the perfview we could see these ASP events are captured :
Once we open the above-highlighted events, we could see much more detailed information about the requests :
In case , we are not able to capture the etw via the perfview UI , then we could use the command line as well :
PerfView.exe "/DataFile:PerfViewData.etl" /BufferSizeMB:256 /StackCompression /CircularMB:1000 /KernelEvents:ThreadTime /Providers:"IIS: Active Server Pages (ASP)::Verbose,Microsoft-Windows-IIS" /NoGui collect
Happy Troubleshooting 😊
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.