Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Not fun.</p> <p>Many root causes share common symptoms which makes it difficult to diagnose without getting dirty with the application. :) Pardon if some of these steps were implied.</p> <p>Some next steps might be:</p> <ul> <li>Review the IIS logs of each site looking for things like: <ul> <li>HTTP response codes (5xx,4xx,3xx)</li> <li>Request response times </li> </ul></li> <li>Review Windows Event Logs <ul> <li>How often are application pools cycling?</li> <li>Application errors, etc. </li> </ul></li> <li>Verify processModel settings as suggested by @vinayc to make sure predecessor didn't get 'tricky'</li> <li>Install <a href="http://www.microsoft.com/download/en/details.aspx?displaylang=en&amp;id=24370" rel="nofollow">DebugDiag</a>, its a surprisingly good tool for some basic analysis of memory and crash related problems.<br> <ul> <li>This can also help you capture memory snaps to diagnose later. </li> <li>Tess Ferrandez <a href="http://blogs.msdn.com/b/tess/" rel="nofollow">blog</a> can help make heads/tails of memory snap analysis. </li> </ul></li> <li>Understand how many web applications are running in each AppPool. </li> <li>Investigate using a 'web garden' to possibly help minimize number of users impacted by 'slow down' </li> <li>Is a virus scanner enabled? Is it running? If so, verify exclusions.</li> <li>Are application teams available to help troubleshoot? Identify if they have any custom application instrumentation that might help diagnose problem.</li> </ul> <p>Is the behavior 'new'? Or has it always been there? If 'new', can you track down which deployment might have caused the new behavior?</p> <p>Could the the description given of the 'slow down' behavior be attributed to an apppool recycle and resulting jitting of the application again? ala - the first request syndrome.</p> <p>Reviewing the logs helps understand how the sites/applications are being used, which can be especially important if you don't own the codebase. <a href="http://www.microsoft.com/download/en/details.aspx?displaylang=en&amp;id=24659" rel="nofollow">Logparser</a> is an excellent tool for doing some IIS log analysis (as well as other formats).</p> <p>Good luck!</p> <p>Z</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload