Hi everyone,
I've tried it a thousand ways and there's no way.
When I load a large report, it consumes 1GB of memory in sever.
This memory is never released(liberate).
In a day can get to occupy 23gb.
I tried in the html5 report viewer, with all type of cache and nothing.
Is there something for when I close the report, free this report memory?
Thank you
1 Answer, 1 is accepted
0
Hi ,
If you are using the HTML5 Viewer, you need a Reporting REST service. The Reporting REST service storage can be configured in the ReportsControllerBase implementation or via configuration settings - How To: Implement the ReportsController in an application.
The REST service can use the file system, database or a Redis instance - REST Service Storage, where the cache is cleared automatically on creating a new client (registering a new viewer with the service), where the requests removes cache entries of viewer's with expired ClientSessionTimeout at that moment.
Please check Cache Management.
CPU and memory are used only on processing the report with the retrieved data. Which resources must be disposed automatically. If the machine has issues to process the report with a given amount of data, please consider filtering data on retrieval for the web preview of the report. For more suggestions, check Performance Considerations.
In case you use the old.ASP.NET WebForms ReportViewer, resources are kept in the ASP.NET Session, and they will remain there until the session ends. You can configure the viewer's cache to place some resources in physical files or in a database - Configure old viewer's cache.
If you need further help, please elaborate on the used viewer, Telerik Reporting version and cache settings. Include details how data is visualized in the report (via band report or you use a Table, List, Crosstab or SubReport item).
Regards,
Stef
Telerik by Progress
If you are using the HTML5 Viewer, you need a Reporting REST service. The Reporting REST service storage can be configured in the ReportsControllerBase implementation or via configuration settings - How To: Implement the ReportsController in an application.
The REST service can use the file system, database or a Redis instance - REST Service Storage, where the cache is cleared automatically on creating a new client (registering a new viewer with the service), where the requests removes cache entries of viewer's with expired ClientSessionTimeout at that moment.
Please check Cache Management.
CPU and memory are used only on processing the report with the retrieved data. Which resources must be disposed automatically. If the machine has issues to process the report with a given amount of data, please consider filtering data on retrieval for the web preview of the report. For more suggestions, check Performance Considerations.
In case you use the old.ASP.NET WebForms ReportViewer, resources are kept in the ASP.NET Session, and they will remain there until the session ends. You can configure the viewer's cache to place some resources in physical files or in a database - Configure old viewer's cache.
If you need further help, please elaborate on the used viewer, Telerik Reporting version and cache settings. Include details how data is visualized in the report (via band report or you use a Table, List, Crosstab or SubReport item).
Regards,
Stef
Telerik by Progress
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items