Website Problem

Just an initial demo map, so that you don't start with an empty map list ...

Get Started. It's Free
or sign up with your email address
Rocket clouds
Website Problem by Mind Map: Website Problem

1. Site slow

1.1. Check Web server

1.1.1. CPU > 80%

1.1.1.1. w3wp.exe is taking high CPU

1.1.1.1.1. Check IIS log for long running pages

1.1.1.2. Some other process is taking high CPU

1.1.1.2.1. SQL Server and IIS on same box

1.1.1.2.2. Some other app is taking CPU

1.1.2. High Memory Usage

1.1.2.1. Certain .NET Process is consuming high memory

1.1.2.1.1. If Virtual Memory significantly high compared to Working Set?

1.1.2.2. Non .NET process consuming high memory

1.1.2.2.1. Find out who is the vendor and ask for suport

1.1.3. High Disk usage

1.1.3.1. Counter: Memory: Pages/Sec > 0

1.1.3.1.1. Check from task bar which process is taking most RAM

1.1.3.1.2. Is Page file size is smaller than 1.5 times the RAM? Then set it 1.5 times the RAM

1.1.4. Counter: Requests in Application Queue > 0

1.1.5. Counter: Request Execution Time is > 20 sec

1.1.5.1. You have some very slow pages or webservices that are consuming threads.

1.1.5.1.1. Increase threads in processModel in machine.config if CPU consumption is low.

1.1.5.1.2. If CPU consumption is high, then fix the code or get more servers and scale out

1.2. Check Database Server

1.2.1. Counter: SQL Server: Locks: Lock Timeout/Sec > 0

1.2.1.1. See Standard Reports: Top Transactions By Transaction Locks Count. Find the transaction that's blocking most of the transactions. Analyze the query and see why it takes so long. http://tinyurl.com/n8aow9

1.2.2. Counter: SQL Server: Access Methods: Full Scans/Sec > 100

1.2.2.1. Bad queries, not hitting index. Find them from Standard Reports: Top Transactions by Average IO. http://tinyurl.com/mhu77n

1.2.3. Counter: SQL Server: Access Methods: Table Lock Escalation/Sec > 20

1.2.3.1. Bad Queries, trying to read large amount of data and missing index. See from Standard Reports: Top Transactions by Average IO. http://tinyurl.com/mhu77n

1.2.4. SQL Server: Memory Manager: Target Server Memory > Total Server Memory

1.2.4.1. SQL Server needs more RAM. Add more RAM

1.2.5. SQL Server: Buffer Manager: Buffer Cache hit ratio < 85%

1.2.5.1. SQL Server needs more RAM. Add more RAM

1.2.5.2. You have queries that's reading data from random distant places from the database and SQL server has no clue what to cache

1.2.6. Memory: Pages/Sec > 4

1.2.6.1. You need to have at 40% RAM of the total database size. If your database size is 10 GB, have 4 GB RAM given to SQL Server

1.2.6.2. You have some other process running on database server that's taking RAM. Find such process and uninstall them.

1.2.7. Processor: % Processor Time > 70%

1.2.7.1. You have queries that's CPU intensive. http://tinyurl.com/mhu77n

1.3. Check Firewall and Load Balancer

2. Site down

2.1. Check Web server

2.1.1. CPU over 90%

2.1.2. Check IIS

2.1.2.1. Website stopped

2.1.2.1.1. Starting Web site fails to start

2.1.2.2. Application Pool Disabled

2.1.2.2.1. Check Error in Event Log entries in System Category

2.1.2.3. IIS Stopped

2.1.2.3.1. Start IIS fails

2.1.2.3.2. Check Event Log Entry

2.1.3. Check ASP.NET Performance Counters

2.1.3.1. Error: Too many unhandled exceptions

2.1.3.1.1. Bug in code, fix it!

2.1.3.1.2. Implement custom error handler http://tinyurl.com/2d7czl

2.1.3.2. Too many Application Restarts

2.1.3.2.1. Exception being thrown from background thread. http://support.microsoft.com/kb/911816

2.1.3.3. High number of Requests in Application Queue

2.1.3.3.1. Outbound calls are taking too long to finish. Lower down timeout or implement async pattern: http://tinyurl.com/omarPROXY

2.1.3.3.2. Database calls are taking too long to complete. Optimize queries to execute faster. http://tinyurl.com/omarWEB

2.2. Check Database Server

2.2.1. SQL Server service stopped

2.2.2. Database offline

2.2.3. SQL Server connection failing

2.2.4. SQL Server not executing query

2.3. Check Firewall and Load Balancer

3. Site sometimes comes

3.1. Check Web Server

3.1.1. High CPU

3.1.2. Check ASP.NET Perf Counters

3.2. Check Database Server

3.3. Check Firewall and Load Balancer

4. Randomly Requests fail