6 Answers, 1 is accepted
OutOfMemory exception usually indicates that the memory taken during the report generation has reached its limit.
Report processing and rendering are memory intensive operations. During the report generation, besides the retrieved data there are newly generated resources by the report which are held in memory and each item takes time and memory to be rendered in the report.
A lot of factors will influence the report's performance: machine capabilities, number of report items, amount of data, report's complexity and rendering format.
It is recommended to go through Performance Considerations help article (Performance factors in the developer’s control) that is suggesting how the report performance can be optimized.
You might consider narrowing the amount of data that needs to be retrieved by using data source parameters - filtering data on data retrieval.
When data source parameters are mapped to report parameters the end user can control what amount of data needs to be displayed in the report - Using Parameters with the SqlDataSource component(Binding SQL Query Parameters to Report Parameters).
I hope this will help.
What if I could not retrieve all the data?
Reduce the amount of information. To reduce the size of how much will be enough 1GB, 2GB, ..
Or is this a limitation for you to call the report?
No problem Or do you have a better way to reduce the amount of information? Please tell me
I would like to retrieve all information. I do not want to reduce the amount of information you offer.
Tell me Please.
Hello Admin Telerik,
No one can answer me. ?!!
The suggestions we can offer for optimizing report's performance are provided in Performance Considerations help article.
In case, all the data needs to be in the report you can consider upgrading the machines where reports are generated. For data- and layout-intensive reports it is recommended a minimum of a dual core processor with at least 2 GB of RAM. Network traffic bandwidth also impacts performance.
I use 16 GB RAM, it is still a problem .... OutOfMemoryException!!.
Do you have another way? To fix it for us.
Tell me Please.
You might consider narrowing the amount of data in the report by using data source parameters, e.g. filtering data on data source level. When data source parameters are mapped to report parameters the end user can control the amount of data displayed in the report - SqlDataSource component(Binding SQL Query Parameters to Report Parameters).
More suggestions can be found in Performance Considerations help article (Performance factors in the developer’s control).