[Original] building a high-performance ASP. Net Site Chapter 5-Performance Tuning Overview (previous)

Build high performanceASP. NETSite Chapter 5-Performance Tuning Overview (previous)

During this time, the seriesArticleI reorganized it. The previous introduction to performance optimization was not very clear. It can be said that starting from this article, it is the beginning of a complete series.

Links to articles:

Build high performanceASP. NETSite Opening

Build high performanceASP. NETOne site Analyze the page processing process (front-end)

Build high-performance ASP. Net Site 2 optimize HTTP requests (front-end)

Building a high-performance ASP. Net site depends on the three details

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

Design of large-scale high-performance ASP. NET System Architecture

Building a high-performance ASP. Net Site Chapter 5-Performance Tuning Overview (Part 1)

Building a high-performance ASP. Net Site Chapter 5-Performance Tuning Overview (Part II)

Building a high-performance ASP. Net Site Chapter 6-performance bottleneck diagnosis and preliminary optimization (Part 1)-identifying performance bottlenecks

Build a high-performance ASP. Net Site Chapter 6-performance bottleneck diagnosis and preliminary optimization (next article)-simple Optimization Measures

Building a high-performance ASP. Net Site Chapter 6-performance bottleneck diagnosis and preliminary optimization (next article)-reducing unnecessary requests

Building a high-performance ASP. Net Site Chapter 7 how to solve memory problems (previous article)-Managed Resource Optimization-in-depth analysis of the garbage collection mechanism

Building a high-performance ASP. Net Site Chapter 7 how to solve memory problems (previous article)-Managed Resource Optimization-monitor CLR Performance

 

 

 

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, suchCode;

II,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, Early detection of causes of website slowdown. 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 it will be more costly to do so.!

 

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 lead to some strange phenomena."Optimization Measures"This reduces the website performance. In addition, if one change is made multiple times, it is not conducive to measuring those"Optimization Measures"It is truly improving the performance of the website.

2.Continuous testing. The so-called"Optimization"After that, you must test this."Optimization"Whether the performance is actually improved. If the performance is not improved, roll back the operation.

The general optimization steps are as follows:

1.Record the current website performance index and related data(How to obtain the performance index data)

2.Diagnose the performance fault point of a site.The performance of the site may be affected in a few places. However, at this time, we only select the factor that has 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.Repeated1To4Step.

 

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:

 

 

OK. These will be released now. Next release: analyze performance bottlenecks using analysis tools.

 

I have not updated my blog for a while. Thank you for your consistent attention and support. In the new year, I will try to provide you with more blog posts, it's a feedback to friends. Thank you again! :)