Research and discussion on optimizing asp.net application performance

This article discusses how to improve the performance of asp.net applications from page, data access, string manipulation, and provides several test tools for detecting asp.net Web site performance.
Keyword asp.net application performance optimization
The performance of a Web site is very important for asp.net developers. Although a good site has beautiful page design, perfect service function, but open the page has a long delay, the user will eventually unbearable. Especially for large e-commerce sites, there are tens of thousands of users per second access, no good site performance, simply can not meet the huge demand.
Asp. NET as a new generation of Dynamic Web page generation system, it has an essential improvement in platform performance compared with the original ASP. But on this basis to develop professional standards, meet the standards of production, user-welcome Web applications, but also need developers from a programmatic point of view in the page, data access and string processing and other aspects of the optimization process to improve the overall performance of the site.
In this paper, we will discuss several methods of performance optimization in asp.net and pay attention to the problems concerned.
Page Performance Optimization
1, the appropriate choice of session state
The HTTP protocol is a stateless communication protocol that cannot record and identify requests from different clients, but in practice the system maintains session state information between different requests from the client. Asp. NET solves this problem by storing session state information in a process, state server, or SQL Server database.
Saving session state information in the memory of a Web server has the best performance and speed, but lacks the ability of session state information to span multiple servers. To maintain session information between multiple Web servers, you can use a state server for storage, which increases the scalability and reliability of your system by deploying applications to multiple servers, but at the expense of performance. For extremely important session information, you need to use SQL Server storage to avoid losing important session information, but the resulting workload is much larger than the previous two.
If you do not consider the retention of state information and multiple server sharing, you should choose to save in the process of the server in order to get the best performance.
The way in which session state information is stored is selected through the Web.config file: