Shulou(Shulou.com)06/02 Report--

This article mainly explains "how to optimize ASP.NET pipeline and process". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to optimize ASP.NET pipeline and process".

ASP.NET 2.0 contains a lot of secrets, and when you discover it, it can bring greater performance and scalability improvements to your program. For example, knowing the secret bottlenecks hidden in Membership and Profile provider providers can easily solve authentication problems and speed up authorization operations.

In addition, the ASP.NET HTTP pipeline is designed to avoid blocking the necessary code to be executed for each request. Not only that, the ASP.NET worker process can push its limitations and achieve higher performance. The output cache of page fragments on the browser side (not on the server side) can significantly save download time for interviewees. Downloading according to the user interface on demand can make your site feel fast and smooth.

* the proper use of content delivery networks and HTTP cache headers can make your site surprisingly fast. In this article, you will learn about these techniques that enable your ASP.NET applications to achieve higher performance, better scalability, and can be implemented on any ASP.NET site, especially those that apply ASP.NET 2.0 Membership and Profile provider.

ASP.NET pipeline optimization

Many of the ASP.NET 's default HttpModules located in the request pipeline are used to intercept every request made by the client. For example, SessionStateModule intercepts each request, parses the corresponding session cookie, and then loads the appropriate session in HttpContext. Real-time proof that not all modules is necessary.

For example, if you don't use Membership and Profile provider providers, then you don't need FormsAuthentication module. If you need to use Windows authentication for your users, then you don't need WindowsAuthentication. These modules located in the pipeline simply execute some unnecessary code each time the request arrives.

The default modules is defined in the machine.config file (located in the $WINDOWS$\ Microsoft.NET\ Framework\ $VERSION$\ CONFIG directory).

< httpModules > < add name= "OutputCache" type= "System.Web.Caching.OutputCacheModule" / > < add name= "Session" type= "System.Web.SessionState.SessionStateModule" / > < add name= "WindowsAuthentication" type= "System.Web.Security.WindowsAuthenticationModule" / > < add name= "FormsAuthentication" type= "System.Web.Security.FormsAuthenticationModule" / > < add name= "PassportAuthentication" type= "System.Web.Security.PassportAuthenticationModule" / > < add name= " UrlAuthorization "type=" System.Web.Security.UrlAuthorizationModule "/ > < add name=" FileAuthorization "type=" System.Web.Security.FileAuthorizationModule "/ > < add name=" ErrorHandlerModule "type=" System.Web.Mobile.ErrorHandlerModule System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a "/ > < / httpModules >

You can delete these default modules by adding nodes to your site application in the site's web.config file. For example:

< httpModules >

Share To

Weibo Tencent Renren QQZone Douban More

Weibo Tencent Renren QQZone Douban Yixin