Developing High Performance ASP.NET Websites(1st)
The following days I'm going to write a series of blog articles about developing high performance ASP.NET websites.
Almost no clever or technically challenging concepts in these articles, because the premise behind the ideas presented in these posts are that they must be:
Dang Near Effortless Require Very Little Expertise Leverage Built-In .NET Features or Tools Easy to Maintain Offer Decent Bang For Your Buck
n Improving query performance
Carefully designing the database; for example, having indexes on the columns used in
table joins significantly improves query performance.
A basic understanding of Sql Server Indexes should be known by all to help you in your development. Adding the proper indexes to your tables can help keep your application performing well long after hundreds and thousands of records have been added to the tables. Use Query Analyzer to display the execution plans of your most active queries and stored procedures so you can tune Sql Server and create the indexes wisely. Best to wait and add indexes toward the latter part of the project after you have a feel for the way the data is queried and consistently tune and reindex your application after you make new enhancements.
n Speeding Up ASP.NET Pages
A good user interface and business layer that eliminate excessive round trips between other tiers in your applications.
To speed up you ASP.NET Pages, you want to look at a minimum of 3 things: 1) Reducing Page Processing, 2) Reducing Page Sizes, and 3) Faster Page Rendering. Much of the page processing time can be reduced using tricks we mentioned before, such as caching, eliminating chatty interfaces, and preferring HTML tags over ASP.NET web controls. Page sizes can be reduced by reducing the file sizes of HTML, images, javascript, and the ASP.NET ViewState. For faster page rendering, use CSS to eliminate tables to improve performance.
n Page Tracing to profile your ASP.NET pages
For more see:http://davidhayden.com, Author:David Hayden
By injecting custom Trace.Write or Trace.Warn messages into your page code, you can get finely grained performance information on specific tasks occuring during the lifecycle of the page as well as measure the impact of caching and various other performance techniques.
n A Good User Interface and Business Layer