"Performance Diagnostics" first, opening

In use. NET to quickly get started and develop the application, the next is likely to be the system performance tuning problems, especially the current system is mostly unusually large and complex, performance problems of diagnosis and tuning work more difficult to start. In general, the diagnostic tuning work requires extensive knowledge and experience, not just code or SQL experience, but also the business logic, System architecture design, application writing, operating system, network environment, a variety of detection and monitoring tools, hardware, etc., have a basic understanding of the complex system to find the crux of the problem.

Remember before, Microsoft's performance tuning file indicates the percentage of various elements: Prior experience 19%, the ability to solve problems 22%, whether there is a complete consulting services 16%, product familiarity 26%, computer-related knowledge 13%, Luck 4%, yes, even if you have super ability, there are 4% Opportunities are beyond our control.

Because I have done a period of full-time diagnostic optimization work, the performance of the process and the general analysis methods and tools to collate, share to everyone, is also a point, if there are shortcomings please forgive us.

After receiving feedback on the performance of the project site, I will first ask a few questions and have a cursory understanding of:

1. Is it a matter of integrity, or is there a problem with individual modules and functions?
2. Is the response time long or not responding (hangs)?
3. Is it all user feedback, or is it an individual user? What was the online user at that time?
4. Intermittent or continuous, what is the intermittent time interval? End of month/year?
5. From what time (or event) do you start? What is the report, the monthly knot, the network adjustment, the replacement of the hardware and so on

Based on the feedback from the site, I'll use (or let the field) different tools to collect performance data, the following is my performance Problem diagnostic Toolbox:

The General analysis process:

1. Using fiddler or the browser's own development tools to identify performance bottlenecks on the client side or on the server (or network)?

2, if the request response time is longer? Analysis from the application server or the network.

3, the application server side, the main analysis is there obvious SQL waiting, blocking? Identify bottlenecks in the application system or the database server?

4, if SQL blocking, the performance view of the analysis DB, AWR, the performance counters on the DB server, and so on.

5. If SQL does not have obvious blocking, use Redgate to analyze the application server thread or crawl dump using WinDbg analysis.

6, using the app and the performance counters on the DB server, collect CPU, memory, disk IO and other aspects of data.

7, if the above are not obvious problems, consider the network factors, you can use the Network Monitoring tool for packet capture analysis.

Follow-up I will separately on the single function, concurrency scenario, client, network and other aspects of performance issues are introduced, will also collate several typical real-combat project analysis process, drink saliva first.

"Performance Diagnostics" first, opening