Wizard to trouble shoot ASP.NET and EPiServer web sites that performs less than expected.
Locate the problem
The easiest problem (but very often missed) is to locate where the problem occurs with simple tools such as Task manager or
process explorer.
Log files to get when troubleshoot an EPiServer installation
1) A network log from the client
2) An EPiServer log
3) The IIS log
4) A SQL-server trace
5) The application event log for the application server
IIS xrash/restarts
IIS crash - The IIS restart without any explainable reason
High CPU usage on the client
This is probably caused by a client script is consuming a lot of CPU to examine what can cause the issue:
1) If you are using FireFox, stop fire-bug it can use a lot of CPU and hang a browser.
2) Turn of java script in the browser, if that solve your issue debug the scripts.
3) Turn off the browsers "Add-ons" one by one and see if the high CPU hang is gone between each "add-on" to locate the problem.
High CPU usage on the server
Look how much CPU that is used on all the machines that is used on your website. If one of the servers has 80% CPU usages it can be a strong candidate of a high CPU usage issue.
If the database server has a high CPU usages go to
Troubleshoot a high CPU usage in the database.
If one of the application servers has a high CPU usages go to
Troubleshoot a high CPU usage of an .NET application server.
Low CPU hang
A low CPU hang means that the application is waiting on something and not deliver as good as it should.
Low CPU hang on the client
To be written…
Time To First Byte is long
An excellent tool to examine the loading of web pages is
Fire-Bug for FireFox. If you click on the net tab all the requests to the server is listed. If you hover over one of the bars the first information is how long time the browser has to wait until the first byte is read. If the time is over two seconds you have to
Examine a long time to first byte.
Low CPU hang on the .NET application server
To be written…