Anyone else notice this?
Seems like this would be an issue of loading an assembly or something, then once it's there, things are fast. This problem also exists in SSRS. It is not a good user experience though and I don't think it should be like this.
Is there anything to be done about this? I was thinking a poor man's solution would be to script something that does an export periodically behind the scenes, just to keep the code loaded up in memory or something.
12 Answers, 1 is accepted
I can't confirm the behavior that you observe. Is the same behavior observed with any other export format e.g. Excel? Have you checked what assemblies are being requested and loaded upon the first export operation? If the extra time is taken to load the assemblies that contain your reports into the current AppDomain, then the solution is as simple as referencing a single type from your report library like this:
The code snippet above relies on the Application_Start method in Global.asax and its only purpose is to force the .NET runtime to load the assembly where MyReportLibrary.Report1 type resides.
the Telerik team
The report is loaded into the ASP.Net report viewer control. Therefore the assembly, my .dll, containing the reports MUST have been loaded. Then the user selects to export. That is where the slowness occurs, the first time, indicating that there is something going on in the component, your .dlls, that gets loaded up and renders the report into PDF. I don't know what, only that the first run is slow, then any folllowing that are nearly instant.
It seems to take a long time to process this line:
Dim reportResults As Telerik.Reporting.Processing.RenderingResult = reportProcessor.RenderReport("PDF", instanceReportSource, Nothing)
My report does have a number of groups and conditional formatting. The report is only 31 pages.
An excel export is much faster.
Does this happen every time? If you were to run that code twice in succession, would the second time be faster?
Also, 600 pages in 15 seconds seems pretty good to me.
The "actual" report has about 10 columns, groups, etc, and that takes many minutes.
@Ed: We have tested to export programmatically approximately 100 pages and the result file is generated in approximately 8 seconds with slight improvements in any consecutive export. Please, open a support ticket and send us a runnable project illustrating the described export behavior if it is an issue for you.
@Peter: I believe we discussed your issue in a separate support ticket some time ago. What we said then was that we are aware of the performance of exporting large amounts of data and we have plans to revise that mechanism, but we should not forget that the main point in reporting BI solutions is displaying data in a human-readable format.
@Hans: Can you please elaborate to which issue you associate? If it is about the slow export, please check the Performance Considerations help article to see what can be done to fasten the export. You can also consider export to excel and csv where the export is faster due to the missing paging stage.
Let us know if you have any further questions or concerns.
the Telerik team
See what's new in Telerik Reporting Q1 2013. Register for the March 4 webinar to witness the impressive new visualizations in Telerik Reporting. Just for fun, 10 webinar attendees will be randomly selected to win a Telerik T-shirt and a $50 Gift Certificate to ThinkGeek. Register now! Seats are limited!