When we are looking to optimize the performance of web applications we should keep in mind about Memory Load, Processor Load and Network Bandwidth. Here are 50 best practices to improve the performance and scalability of ASP.NET applications. 1. Page.IsPostBack PropertyKeep code which only needs to be loaded once inside an IsPostBack block.if(!IsPostBack)
{
BindDropDownList();
LoadDynamicControls();
}As a result there will be no unnecessary database hits and server processing. 2. Enable BufferingA buffer is a region in main memory to store temporary data for input and output .Data retrival from memory is faster than data retrieval from disk. We should leave buffering on unless there is any specific reason to turn it off. By default buffering is enable. 3. Remove unused HttpModulesThere may be lot of HttpModules in Machine.Config that are not actually required for a particular application. In this scenario we should remove those unused HttpModules from application specific web.config file. 4. Trim Page SizesReduce page size by removing any unnecessary space and tab characters from the page. As a result network traffic will be reduced.5. Use a CDNNot a performance tip exclusive to ASP.NET but an important step in speeding up a site is to use a Content Delivery Network (CDN) . CDN’s minimize the latency site visitors experience when they request a larger file from a data center that is located geographically far away. CDN’s cache files at numerous edge locations around the world to minimize latency.
If you are using Azure consider using the Windows Azure CDN , Amazon’s CloudFront cheap and easy to integrate into a website (if you happen to have a WordPress blog you can integrate S3 and CloudFront into WordPress)
(more..)Read more: ASP NET 101
{
BindDropDownList();
LoadDynamicControls();
}As a result there will be no unnecessary database hits and server processing. 2. Enable BufferingA buffer is a region in main memory to store temporary data for input and output .Data retrival from memory is faster than data retrieval from disk. We should leave buffering on unless there is any specific reason to turn it off. By default buffering is enable. 3. Remove unused HttpModulesThere may be lot of HttpModules in Machine.Config that are not actually required for a particular application. In this scenario we should remove those unused HttpModules from application specific web.config file. 4. Trim Page SizesReduce page size by removing any unnecessary space and tab characters from the page. As a result network traffic will be reduced.5. Use a CDNNot a performance tip exclusive to ASP.NET but an important step in speeding up a site is to use a Content Delivery Network (CDN) . CDN’s minimize the latency site visitors experience when they request a larger file from a data center that is located geographically far away. CDN’s cache files at numerous edge locations around the world to minimize latency.
If you are using Azure consider using the Windows Azure CDN , Amazon’s CloudFront cheap and easy to integrate into a website (if you happen to have a WordPress blog you can integrate S3 and CloudFront into WordPress)
(more..)Read more: ASP NET 101