This is a migrated thread and some comments may be shown as answers.

Report generation taking so much time with large data.

22 Answers 1580 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

22 Answers, 1 is accepted

answered on 27 Jul 2010, 05:29 PM

Hi guys,

As far as the processing time and consumed memory is concerned, the complexity of the report layout, the complexity of the data calculations (aggregates, conditional formatting), the rendering media, the size of the generated document (in pages), and the capabilities of the underlying machine are crucial.

We would appreciate your thorough explanation of your scenario and a runnable sample project so we can give appropriate advise. That is why we would appreciate if you send us a sample application that we can run on our end and observe the problems you've elaborated on. Once we review it, we would be able to provide you with more info.

@Janusz - how many rows of data do you have and do you render them directly in the report or you use Table/CrossTab item?

All the best,
Steve
the Telerik team

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 Public Issue Tracking system and vote to affect the priority of the items

answered on 28 Jul 2010, 04:32 PM

Are you restricting your SQL query to retrieve only the data you need for the report (i.e. just returning the 5000 of 60,000 rows from the database)? If you are just using Telerik reporting to filter the rows, then what is happening is all 60,000 rows are being returned to Telerik reporting and then it has to go through each returned row doing the filtering.

For example, let us say you have just want records for a certain date range, you need to add something like this to your SQL query to retrieve the data:

WHERE RowDate>=@MinRequestedDate AND RowDate<@MaxRequestedDate

this would filter the returned data down to rows on or after MinRequestedDate (inclusive of the limit) but before MaxRequestedDate (exclusive of the limit)

You have to explicitly make this change to your query.

answered on 29 Jul 2010, 01:52 PM

Hi Janusz,

As you can see from our Q2 release notes, the observed behavior should be the opposite i.e. the table rendering performance should be better rather than worse compared to the Q1 release and that is why your claim has baffled us.
That is why we would appreciate if you send us a sample runnable application/report that we can use on our end for testing. Once we review it, we would be able to provide you with more info.

As to your multivalue inquiry - as far as the SqlDataSourceParameters are concerned, the current implementation is based on ADO.NET and does not allow you to pass a collection of values (set, array). Thus, the SqlDataSourceParameter accepts only single values corresponding to the SqlDataSourceParameter.DbType property. Although this is a known limitation of ADO.NET, we're currently researching on possible solution for it.

Kind regards,
Steve
the Telerik team

answered on 11 Feb 2014, 10:33 PM

I can report that the Telerik suite does work. I am, like you, a customer of theirs who is delivering solutions to my customers. As part of my day to day duties I code solutions using c# and the Telerik suite. Amongst the many reports I have written, I have one which is part of a local municipalities monthly billing process. An average cycle prints out around 880 pages. While I personally consider it a HUGE waste of paper they still actually print the critter. The report contains customer information, totals by service, totals by customer, and totals by report. This report takes around 1.5 minutes of SQL query time and about 2 minutes to render. Exporting to Adobe, in the attempt to save trees, takes around 2.5 minutes. Exports to Excel are pretty much instant and render reports in the 18-24000 rows range.

While this sample might be larger than you are needing it should give you an idea that what you are looking for is possible.

answered on 17 Feb 2014, 06:00 PM

Hello Kiran,

We reviewed the provided project and sent you several suggestions to test at your side. This is a quote from my response:
"You can find attached the modified project - we added manually 250 rows to the data source of the report and it produced 36 pages for less than 10 seconds.

Based on the provided report definition, test the following at your side:

There are 10 static groups in the report, which can be merged into a single static group - this will save unnecessary calculations for unneeded sections;
Instead of arranging the layout manually, use a Table/List item with static rows and columns and place the TextBox items in the cells - the arrangement matters for the speed of measuring the items in the rendering media;
Move the logic from the code behind logic into expressions. For example if a TextBox.Format will depend on a field, use the built-in functions and custom functions to bind the property. Use conditional formatting to set colors based on field's running value;
Move the logic where the user selects the fields to be displayed and the report modifications outside events. For example when you instantiate the report, you can get a whole section and its Items or specific item. Then set items' Value properties. Consider the example in the Access items from report, calling application and Table(Access items from calling application) article.

"

Please, let us continue the discussion in your support ticket.

Regards,
Stef
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.

answered on 23 Aug 2019, 11:08 AM

Hello Solange,

Do you preview the report in the Standalone Report Designer (Visual Studio Report designer) or it is integrated into the application? If it is displayed through any of the HTML5 Report Viewers, you can inspect through the dev tools of the browser. You can also enable Trace Listener to the Standalone designer or to Visual Studio (refer to Visual Studio Problems article) to check for any errors in the generated log file. The reporting engine performance depends on numerous factors, so without looking at the report definition I'm unable to give a suggestion about the problem. In addition, which is the version of Telerik Reporting?

Try to open our Product Sales demo which contains about 120 000 rows of data. You can also check the Performance Consideration article that elaborates on the subject.

Regards,
Neli
Progress Telerik

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