You have an ASP.NET Web application that displays charts that are generated daily from data in a Microsoft SQL Server database.
Each chart is implemented as a user control that displays data retrieved from the database.
Data retrieval and chart generation consume a significant amount of resources.
Users of the Web application generate unique reports that contain one or more chart controls.
Each chart is common to many reports.
You need design a solution to improve the performance of the Web server.
Which approach should you recommend?
A.
Use page caching.
B.
Use fragment caching.
C.
Use the application cache.
D.
Use SQL cache dependency.
Explanation:
Caching Pages and Fragments
The best way to improve the server performance of an ASP.NET application is to partially or completely eliminate the ASPX rendering process. ASP.NET provides two types of output caching:
– Page caching ASP.NET caches an entire page and returns it for subsequent requests for the same page. Page caching caches the entire contents of a page, including any user controls.
-Fragment caching ASP.NET caches one or more user controls and inserts the cached output into an ASP.NET page. You can use fragment caching to cache a user control and then insert that cached output into different pages.