5 Answers, 1 is accepted
The Silverlight ReportViewer displays content provided by the Reporting WCF service, where by default resources are saved in-memory. You can configure the service's project to use other storage for resources like file, database to reduce the usage of memory - Cache Management.
The linked articles elaborates on the viewer's cache and how it can be managed.
I hope this information is helpful.
Regards,
Stef
Telerik
Rank 1
Hi Stef,
Thats great - can I turn it off?
regards
Richard
The short answer is no. Viewers need to store some resources for reports and by default they use the memory. If you switch to the HTML5 Viewer, you can cause it to invalidate its cache on each call to the Reporting REST service by applying proper cache timeout settings (available as of Q3 2015 v9.2.15.930).
We will appreciate it if you elaborate on the reason for your request.
Regards,
Stef
Telerik
Rank 1
Hi Stef,
Thanks for coming back to me on this. I have an application that has numerous reports in a tabbed manner using the Silverlight version.
My hands are pretty tied in terms of the version as we have tried to upgrade but its so old and the techniques have changed that its causing a fair few issues to get through the upgrade.
HOWEVER - during testing - many reports were generated - some of them can be 100 pages long and in a tabbed window environment we were getting crashes. When I looked at what might be causing the crashes - hanging on to a bunch of memory seemed to be an early suspect.
I do not understand why when I have finished with a report (which is configurable) - the memory for that specific report isn't released.
It doesn't seem to make much sense to me really.
Richard
A possible cause may be a SIlverlight limitation in the number of simultaneously rendered XAML elements. In general, reports are rendered in XAML format on the server and delivered to the client through the Reporting WCF service.
If XAML elements exceed certain amount, there might be an out of memory error. In such case, you will need to reduce the amount of XAML elements In case only reports cause the problem, reduce the amount of loaded XAML elements by filtering the data in report or using the viewer in PrintPreview mode (it will display only a page at a time).
Other possible reason for such error is not enough memory, as viewers keep resources in memory. This can be resolved by configuring the service's project to use other cache storage like File or database. Or the service's project can be hosted on multiple machine (web farm).
About upgrading the application, this will require update of both Telerik Reporting and Telerik UI for Silverlight as they are synchronized on major releases. The dependencies are listed in the Upgrade Path articles. Also as of Q1 2014 Telerik Reporting uses only implicit styles for the Silverlight/WPF ReportViewer controls - How to: Add report viewer to a Silverlight application.
Regards,
Stef
Telerik