Telerik Reporting uses a dedicated session state management system to store and cache
rendered pages and some large resources such as images on an external storage. This session state management system
is utilized by all report viewers automatically as shown in the following illustration:
 Note | |
The Telerik Reporting session state should not be confused with the ASP.NET session
state. Telerik Reporting session state is used by all report viewers, regardless of the underlying application
technology. In case of an ASP.NET web application, the Telerik Reporting session state is used to offload some large
objects from the ASP.NET session state, such as rendered report pages and images, which often leads to an improved
performance and a significantly reduced memory footprint for the application.
|
Session State Management
Such session state management implementation offers the following key benefits:
- Reduced memory footprint – since the rendered pages and resources are cached on an external storage
rather than being kept in memory, the viewers can handle very large reports with thousands of pages and images without increasing the
memory consumed by the application too much.
- Improved performance – the caching mechanism implemented by the session state management system can lead to improved
performance of the viewers in certain scenarios.
- Improved scalability – web farms can be configured to cache rendered reports on a dedicated database
server. This allows subsequent requests to the same report to be served by different machines in the web farm leading to better load
balancing. Only the database storage is shared between all machines in the farm, as shown in the following illustration:
See Also