Turn: Building a high-performance ASP. NET Site Chapter 5-Performance Tuning Overview (previous)

The topics in this chapter are as follows:

General performance tuning process

Analyze page loading information using analysis tools

Analyze performance bottlenecks using analysis tools

 

General performance tuning process

Before solving the performance problem, you must first confirm the problem. First, let's take a look at the general process of ensuring high performance:

1. Continuous Monitoring

2. Set performance goals

3. Continuous Improvement

 

　　1.Continuous monitoring

The website performance is generally affected by two factors:

I. What we can control, such as code;

2. What we cannot control, such as the number of users to access or the server itself

 

In particular, as the site's access volume increases, there may be no problems in the past. Now, the problems to be solved at different stages are also different. Therefore, it is necessary to continuously monitor the website and find out the reasons for the slow speed of the website as early as possible. Later in this article, the Department will introduce some monitoring services that we can use to help us do these things.

 

　　2.Set performance goals

The most intuitive feeling of website performance is the loading time of pages after the website is opened, which is also the most direct experience of visitors. A lot of optimization work (whether it is optimization at the front end or optimization at the back end) is to allow users to see the desired pages and information more quickly. This is often the purpose of our subsequent discussions.

First, you must understand the meaning of "fast": How fast is a website's response speed "? It takes a lot of time and effort to optimize the website. If the website itself is already very fast, for example, the time when the webpage is displayed to the user is millisecond-level, we can indeed spend more time making it faster, but the cost will be higher!

 

　3. Continuous Improvement

There are a lot of things involved in performance optimization, so we must confirm that the optimization measures have indeed improved the performance of the site. To achieve this purpose, there are several rules to follow:

1. Only one change is allowed for each optimization. If there are many changes, these changes may affect each other and finally lead to some strange phenomena. Sometimes these "optimization measures" have reduced the website performance. In addition, if one change is made multiple times, it is not conducive to measuring that the "optimization measures" are truly improving the performance of the website.

2. Continuous testing. After each so-called "optimization", you must test whether the "optimization" has actually improved the performance. If it has not been improved, roll back the operation.

The general optimization steps are as follows:

1. Record the performance index and related data of the current website (we will tell you how to obtain the performance index data later)

2. diagnose the performance fault point of the site. The performance of the site may be affected in several places. However, at this time, we only choose the one with the greatest impact for optimization.

3. Solve the identified performance fault point.

4. Test. Collect data and compare it with before optimization to see if it improves performance.

5. Repeat steps 1 to 4.

 

Although some rules have been proposed above, we can flexibly handle certain situations: when we look for problems that affect performance, we find multiple problems, and these problems will affect performance based on our experience, so we can modify them at the same time.

We use a flowchart to summarize the above optimization steps. As follows:

 

From: http://www.cnblogs.com/yanyangtian/archive/2011/02/09/1950201.html