10 tips for writing high-performance Web applications

Tips

Author: Rob Howard
This article discusses
& #8226; common ASP. NET performance difficulties

& #8226; useful performance tips and tips for ASP. NET

& #8226; database usage suggestions in ASP. NET

& #8226; use ASP. NET for caching and background processing




This article uses the following technologies:
ASP. NET,. NET Framework, and IIS
Content on this page
Data Layer performance
Tip 1: return multiple result sets
Tip 2-paging data access
Tip 3-connection pool
Tip 4-ASP. NET cache API
Tip 5-cache per request
Tip 6-background processing
Tip 7-page output cache and proxy server
Tip 8-run IIS 6.0 (for Kernel Cache only)
Tip 9-use Gzip for compression
Tip 10-server control view status
Summary
The simplicity of using ASP. NET to write Web applications is unbelievable. Because it is so simple, many developers will not spend time designing the structure of their applications to achieve better performance. In this article, I will introduce 10 tips for writing high-performance Web applications. However, I will not limit these suggestions to ASP. NET applications, because these applications are only part of Web applications. This article does not serve as an authoritative guide to adjust the performance of Web applications-I am afraid this issue cannot be easily explained throughout this book. Please take this article as a good start point.
I used to like rock climbing before I became a workaholic. Before conducting any large-scale rock climbing activities, I will first carefully check the routes in the guide and read the suggestions made by previous visitors. However, no matter how good the guide is, you need a real rock climbing experience before you can try a particularly challenging climb. Similarly, you can only learn how to write high-performance Web applications when you are faced with performance problems or a high-throughput website.
My personal experience comes from ASP. NET department as the infrastructure program manager experience, during which I run and manage www. ASP.. NET helps design the structure of the Community Server. The Community Server is a few famous ASP.. NET applications (ASP. NET Forums ,. text and nGallery ). I'm sure some of the skills that have helped me in the past will certainly help you.
You should consider dividing your application into several logical layers. You may have heard of the term 3 (or n) physical architecture. These are usually well-defined architectures that physically separate functions between processes and/or hardware. When the system needs to be expanded, more hardware can be easily added. However, there will be a performance drop related to processes and Machine jumps, so we should avoid this. Therefore, if possible, try to run ASP. NET pages and related components in the same application.