Article: Improved Caching in ASP.NET
New caching feature
included in ASP.NET 2.0, improves the performance and scalability of ASP.NET
applications. The ASP.NET 2.0 framework includes a number of significant new
enhancements that make it easier to take advantage of caching in
applications.The new DataSource
controls include properties that make it easy to cache database data in memory.
By taking advantage of the DataSource controls, database data can be
retrieved and cached without writing a single line of code.The new support for SQL Cache
Invalidation enables to automatically reload database data in the cache whenever
the data is modified in the underlying database. This feature provides all the
performance benefits of caching, without the worries of stale data.Finally, the new
Substitution control enables more easily mix dynamic content in a cached
page. The Substitution control gives an island of dynamic content in an
cached page.You can find more details in
below URL:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/CachingNT2.asp
Regards,
Mitesh Mehta
Monday, July 12, 2004
Article: Improved Caching in ASP.NET
Subscribe to:
Post Comments (Atom)
1 comment:
Hi,
ASP.NET has three kinds of caching that can be used by Web applications
Output caching: It caches the dynamic response generated by a request.
Fragment caching: It caches portions of a response generated by a request.
Data caching: This caches arbitrary objects programmatically.
Output caching is useful when the contents of an entire page can be cached. On a heavily accessed site, caching frequently accessed pages for even a minute at a time can result in substantial throughput gains. While a page is cached by the output cache, subsequent requests for that page are served from the output page without executing the code that created it.
Sometimes it is not practical to cache an entire page - perhaps portions of the page must be created or customized for each request. In this case, it is often worthwhile to identify objects or data that are expensive to construct and are eligible for caching. Once these items are identified, they can be created once and then cached for some period of time. Additionally, fragment caching can be used to cache regions of a page's output.
In some cases the data might be refreshed at regular intervals or the data is valid for a certain amount of time. In these cases, the cached items can be given an expiration policy that causes them to be removed from the cache when they have expired. Code that accesses the cached item simply checks for the absence of the item and recreates it, if necessary.
Check out these links. Very informative.
ASP.NET Caching
http://www.ondotnet.com/pub/a/dotnet/2002/12/30/cachingaspnet.html
http://www.c-sharpcorner.com/asp/Articles/CachingInASPDPL.asp
http://samples.gotdotnet.com/quickstart/aspplus/doc/cachingoverview.aspx
http://support.microsoft.com/?kbid=307225
Use ASP.NET caching to optimize your Web applications
http://builder.com.com/5100-6387-1049869.html
Happy Coding.
Post a Comment