Hi, on some reports with over 3000 records and heavy grouping I'm getting out of memory exception errors (after I updated httpRuntime executionTimeout="240" in web.config to stop the timeout errors). I notice in another thread you recommend setting app pool to "A value of 300 Mb used memory and default value for virtual memory" would this still be your recommendation and is there anywhere you can point me to to optimise and reduce the memory footprint in the report design?
cheers
Martin
cheers
Martin
1 Answer, 1 is accepted
0
Hello Martin P,
You can create a WinForms application with the Win ReportViewer and use the same report in order to determine exactly how much memory it will take to process and render it completely. Afterwards you can adjust the memory for the application pool to that value. To check the memory usage you can use the Task Manager.
A possible way of optimizing the report might be to use SubReports with parameters and filters instead of groups. However, this improvement depends on what exactly you are trying to achieve.
Hope this helps.
Best wishes,
Chavdar
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
You can create a WinForms application with the Win ReportViewer and use the same report in order to determine exactly how much memory it will take to process and render it completely. Afterwards you can adjust the memory for the application pool to that value. To check the memory usage you can use the Task Manager.
A possible way of optimizing the report might be to use SubReports with parameters and filters instead of groups. However, this improvement depends on what exactly you are trying to achieve.
Hope this helps.
Best wishes,
Chavdar
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.