Dear Telerik experts
I am using Telerik.Reporting Q2 2013.
I have a WPF Report Viewer loaded in a Telerik WPF RadWindow.
1)
When i set the ReportSource as a ReportBook containing 3000 reports (of same type, containing a page header, page footer, report header containing a table, details containing 2 tables and one of them containing optional subtables) the whole UI goes into not responsive mode (showing busy mouse icon).
I have tried to show the Report Viewer with null ReportSource, and then wait for 10 seconds, before setting the ReportSource = ReportBook containing 3000 reports. The Report Viewer shows empty initially with the toolbar, then it goes into not responsive mode again...
I am expecting the Generating Report progress message to show, instead of being not responsive. I have tried to check the source code of Telerik Reporting. It is calling a separate thread, is not it?
2)
The not responsive mode goes for more than one hour and it is still remaining as it is. I put a break point in the report's NeedDataSource() but it was never called throughout the one hour.
Is there any advice i can try to overcome this?
Thanks
Michael
I am using Telerik.Reporting Q2 2013.
I have a WPF Report Viewer loaded in a Telerik WPF RadWindow.
1)
When i set the ReportSource as a ReportBook containing 3000 reports (of same type, containing a page header, page footer, report header containing a table, details containing 2 tables and one of them containing optional subtables) the whole UI goes into not responsive mode (showing busy mouse icon).
I have tried to show the Report Viewer with null ReportSource, and then wait for 10 seconds, before setting the ReportSource = ReportBook containing 3000 reports. The Report Viewer shows empty initially with the toolbar, then it goes into not responsive mode again...
I am expecting the Generating Report progress message to show, instead of being not responsive. I have tried to check the source code of Telerik Reporting. It is calling a separate thread, is not it?
2)
The not responsive mode goes for more than one hour and it is still remaining as it is. I put a break point in the report's NeedDataSource() but it was never called throughout the one hour.
Is there any advice i can try to overcome this?
Thanks
Michael
1 Answer, 1 is accepted
0
Hello Michael,
In general, Telerik Reporting is a general purpose reporting engine, which primary goal is to analyze data and represent it in a human-readable format that is also suitable for printing. During this process, certain complex layout and paging rules are applied, so the great flexibility offered by the reporting engine comes at a price: increased processing times and memory footprint.
The number of reports will affect the overall processing time and with 3000 reports it is even possible to run out of system resources. Consider changing your large and slow report book and create reports with Actions (drill down, drill-through) and Report Parameters (on-demand data). Besides being beneficial to the end-user, these features make the report faster and more efficient, lightening the reporting load by given only the current state of requested data.
You may also find useful the Performance Considerations help article, which covers possible reasons for performance degradation in detail.
Please keep in mind that the reporting tool is not specialized for processing and rendering such amount of reports in a report book and maybe another tool will be more suitable for your scenario.
Still the report processing is done within another thread and while the report is rendered we show indeterminate progress indicator. For example check out the demos that came with your Telerik Reporting installation. In this line of thoughts we are not sure why the report viewer is freezed on your end and we will appreciate if you send us a sample to review and profile on our end.
Regards,
Nasko
Telerik
In general, Telerik Reporting is a general purpose reporting engine, which primary goal is to analyze data and represent it in a human-readable format that is also suitable for printing. During this process, certain complex layout and paging rules are applied, so the great flexibility offered by the reporting engine comes at a price: increased processing times and memory footprint.
The number of reports will affect the overall processing time and with 3000 reports it is even possible to run out of system resources. Consider changing your large and slow report book and create reports with Actions (drill down, drill-through) and Report Parameters (on-demand data). Besides being beneficial to the end-user, these features make the report faster and more efficient, lightening the reporting load by given only the current state of requested data.
You may also find useful the Performance Considerations help article, which covers possible reasons for performance degradation in detail.
Please keep in mind that the reporting tool is not specialized for processing and rendering such amount of reports in a report book and maybe another tool will be more suitable for your scenario.
Still the report processing is done within another thread and while the report is rendered we show indeterminate progress indicator. For example check out the demos that came with your Telerik Reporting installation. In this line of thoughts we are not sure why the report viewer is freezed on your end and we will appreciate if you send us a sample to review and profile on our end.
Regards,
Nasko
Telerik
New HTML5/JS REPORT VIEWER with MOBILE AND TOUCH SUPPORT available in Telerik Reporting Q3 2013! Get the new Reporting version from your account or download a trial.