In my report i am using a cross-tab with toggle visibility option - though it behaves as expected but it slows down the performance of report at least 10 times when I integrate .trdx file in my application. My cross-tab has 2 groups and i am applying toggle visibility to parent group to show/hide child group.
As soon as i remove toggle visibility from crosstab, report render 10 times faster - I have same action set up for graph and it works fine with no performance issues with graph. Can you please guide me if it's some know issue or is there some setting that's needed
7 Answers, 1 is accepted
If you use the HTML5 Viewer, there can be a slow down on the first collapse/expand operation, as the Report REST Service stores the new state of the report in the cache storage. If you repeat the operation with the same elements of the report, you will notice it is much faster.
Other reasons can be the number of HTML elements rendered on the page - HTML Output. Test reducing the amount of data per page by filtering and grouping data.
If you are using other viewer, please specify it. Also let us know the number of data records processed in the report, and the layout of the report.
Telerik by Progress
For report viewer, we are using telerik report viewer.
My report has 1 graph and one crosstab both using same data source, both graph and crosstab has expand/collapse option. Graph has a primary and secondary y-axes and 04 series i.e., 2 bar and 2 line. crosstab has 2 groups year and month.
Our report right now has 1 row for every day for the first 4 months of 2017, and in crosstab and graph we are grouping it by year and month to get monthly averages - It doesn't look like that data issue -
Expand/collapse option when used in graph doesn't seem to impact performance at all. The the report gets noticeably faster just by removing expand and collapse option from the crosstab,
I also noticed that it re-renders all over again and sends a call to storedprocedure every time I hit expand and collapse button in crosstab or graph and almost take same time to re-render, so it doesn't seems that it is using caching for this feature, however when report has multiple pages, it doesn't re-render and use cache to upload next page.
Please let me know if you need any other information regarding this
Please post a screenshot of the used Report Viewer control in order to check if it is the old ASP.NET WebForms ReportViewer or the HTML5 Viewer, or else.
Also test the following:
- Open the report in the Standalone Report Designer and pull the same data as in the custom application. Check the response time on toggling the visibility of rows of the Crosstab item;
- Load the same report, with the same data in a Report Viewer and perform the same test. Compare the response times on toggling the visibility of elements.
- While the report is loaded in the Report Viewer, test to collapse and expand one row. Then repeat the same operation with the same row and compare the response times.
If possible, upgrade to the latest available Telerik Reporting R1 2017 SP2 version and check if the performance is better.
Telerik by Progress
please see attached screenshot of report viewer control.
For other recommendations:
1. in standalone report designer it is not re-rendering on expand/collapse and response time is pretty quick.
2. when loading same report in report viewer, it takes at-least 5 times longer than original time and always re-render and sends a request to sql to run procedure - I can see the requests being sent in sql profiler
3. I am testing expand/collapse one row at a time and it gives me same issue.
For now to resolve performance issue we have removed expand/collapse option as client's priority is quicker report than an other options but i don't think so we can rely on this strategy for very long.
For upgrading to newer version of Telerik, we are not very comfortable as we will have to QA our report all over again. Last time when we upgraded in November we ran into issues, first for expand/collapse icon that turned out to be known issue and was resolved with subsequent release by Telerik, but we are still facing issue with expand/collapse functionality. But if you are recommending that upgrading will resolve the issue on hand, only then we can try it out in our test environment.
The slow down in the HTML5 Viewer is expected as the Reporting REST service stores the state of the report and the way it is rendered. If you request the same layout later, the operation will be executed faster.
Please test the local examples installed under C:\Program Files (x86)\Telerik\Reporting <VERSION>\Examples\CSharp\ReportLibrary\Crosstab, and let us know if you observe the same behavior. Also let us know which version of Telerik Reporting is used in the project.
Telerik by Progress