Performance Improvement in ASP.NET USING CACHING

xiaoxiao2021-03-06  15

Performance Improvement in ASP.NET USING CACHING

Authordate of SubmissionUser Levelharikishan & Giresh02 / 01 / 2005Intermediate

The challenge in building high-performance, scalable Web applications is the ability to store items, whether data objects, pages, or parts of a page, in memory the initial time they are requested. You can store these items on the Web server or other software in the request stream, such as the proxy server or browser. This allows you to avoid recreating information that satisfied a previous request, particularly information that demands significant processor time or other resources.ASP.NET provides caching at several levels for you to leverage and improve the responsiveness of your application by storing the page output or application data across HTTP requests and reuse it. This allows the web server to take advantage of processing the request without recreating the information and thus saving time and resources.Caching Opportunities in ASP. NET Web PageSASP.NET Supports Both Page (or portion of a page) Caching and Also Caching Data from A Backend Data Source and Storing There Individual Objects in Memory.to Achieve this Following Features Are Provided in Asp.net

Page Output Caching Page Fragment Caching Data Caching

Page Output Caching Page Fragment Caching Data Caching

Page Output Caching Page Fragment Caching Data Caching

Page output caching Page fragment caching Data cachingPage Output CachingDynamically generated .aspx pages can be cached for efficiency instead of re-generating each .aspx page for identical requests, the pages are cached. Page Output caching can be achieved in the following 3 ways.1 ) This can be achieved by specifying the @OutputCache directive at the top of the ASP.Net page. It controls the caching duration (in seconds) .Dynamically generated .aspx pages can be cached for efficiency instead of re-generating each .aspx page for identical requests, the pages are cached. Page Output caching can be achieved in the following 3 ways.1) This can be achieved by specifying the @OutputCache directive at the top of the ASP.Net page. It controls the caching duration (in Seconds). <% @ outputcache duration = "3600" VarybyParam = "none"%>