The performance of the
site is related to the user experience, allowing the site to support more users and keeping each user short of time is our goal. Performance improvements are based on database optimizations, efficient HTML code rendering, and content caching. Here are some rules for improving the performance of your web site:
optimizes the database design
The rational use of
Index, the efficient use of the SQL statement, reduce the full table scan of the database table, just return the necessary data, these are very effective ways of database optimization, database is often the performance bottleneck of a web site, you need to continue to optimize the database, improve the performance of every point are not worth mentioning, cumulative will bring a qualitative change.
uses Store Procedure to communicate data between the database and the business layer of the web site
The execution efficiency of
Procedure (Store) is much higher than that of the dispersed SQL statement. As long as your database supports Store Procedure, you should use it as the data communication channel for the web site business logic end and the database side.
paging returns the records in the database without using the paging
of the business layerWhen
returns a large number of data records, should use pagination page by page and display the data in the database, you need the paging terminal, paging in the business layer will result in a large number of duplicate data from the data layer and business layer, resulting in a performance bottleneck.
uses mature optimized Web page rendering techniques
, ASP.NET, PHP, JSP, Ruby, and CGI can act as HTML rendering engines for the web presentation layer, and you can choose the right platform for your own needs. Note that the platform such as the ASP.NET, in order to meet the needs of the vast majority of applications and users as much as possible to reduce the amount of code, use a lot of technology can reduce performance, such as View State, you can turn off these functions in order to improve the execution efficiency and the rendering of the page. In fact, we used the Direct Render approach in Comsharp CMS, and cast aside the ASP.NET page life cycle model, rendering HTML code directly to generate web pages, and achieved very desirable performance.