Dear support,
I have a report in WinForm environment. After the report object was built and it was loaded into Reportviewer by:
Dim frm As New Reportviewer(report)
frm.Show(Me)
It takes nearly 3 mins to generate 140 pages to screen and when I click "export to pdf" from "Reportviewer", it takes nearly another 3 mins. The speed is not too slow, but SLOW. I assume it only takes 5seconds because the process is in RAM.
Any enhancement is planned in this area.
My version is 2.0.1.0.
Benson.
I have a report in WinForm environment. After the report object was built and it was loaded into Reportviewer by:
Dim frm As New Reportviewer(report)
frm.Show(Me)
It takes nearly 3 mins to generate 140 pages to screen and when I click "export to pdf" from "Reportviewer", it takes nearly another 3 mins. The speed is not too slow, but SLOW. I assume it only takes 5seconds because the process is in RAM.
Any enhancement is planned in this area.
My version is 2.0.1.0.
Benson.
10 Answers, 1 is accepted
0
Hi Benson,
As you have noticed correctly every time the report is previewed or exported through the viewer it is processed and rendered from scratch. Obviously, this is not the best way to do this but we still lack any caching mechanism.
One thing that probably can speed up the report processing is the data source initialization. If you use the Report Wizard or the Data Source and connect to a database, the wizards adds a code to fill the typed data set in the report's constructor. This can significantly decrease the report instantiation time especially if it takes longer to retrieve the data from the database. If you move all code that creates and fills the dataset outside the report and then pass this data set to the Report.DataSource property, I suppose you will see some better performance..
Our current goal is to cover the basic reporting functionality and then we will move to the performance optimizations and productivity. Anyway, this task is already in our TODO list and I hope we soon will have the chance to work on it.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
As you have noticed correctly every time the report is previewed or exported through the viewer it is processed and rendered from scratch. Obviously, this is not the best way to do this but we still lack any caching mechanism.
One thing that probably can speed up the report processing is the data source initialization. If you use the Report Wizard or the Data Source and connect to a database, the wizards adds a code to fill the typed data set in the report's constructor. This can significantly decrease the report instantiation time especially if it takes longer to retrieve the data from the database. If you move all code that creates and fills the dataset outside the report and then pass this data set to the Report.DataSource property, I suppose you will see some better performance..
Our current goal is to cover the basic reporting functionality and then we will move to the performance optimizations and productivity. Anyway, this task is already in our TODO list and I hope we soon will have the chance to work on it.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0

Dragoljub
Top achievements
Rank 1
answered on 16 Apr 2008, 10:02 AM
I'm also experiencing this extreme slowness. I've got a report with about 100 pages, but the rows in the report are not condensed as much as they could have been (there was a datetime column which was not formatted so it took two rows to display the complete date and time).
Anyway, I tested the SQL query, and it returned the results immediately in management studio and also in the "preview data" dialog in the dataset designer. So I don't see data loading as the problem in my case.
I've only tested in the preview pane of the report designer, but that's probably the same thing.
The question is what can we do to speed up report generation?
0
Hello Dragoljub,
By default the TextBox item which displays the data has no formatting applied to it. The developer who creates the report is responsible to set the appropriate format according to type of data displayed and the desired output. Moreover the generated output depends on the report definition (this is the Telerik.Reporting.Report derived object that you create through the Report Designer inside Visual Studio or programmatically by hand) and of course of the selected media. For more information please see Design Considerations for Report Rendering.
There are different reasons for the slow report rendering. Usually the large amount of data together with complex grouping and any other calculations that are performed in the report slows down the rendering. The new version Q1 2008 that we just released yesterday has some improvements in the Image/PDF/print rendering extension that can speed up the process with about 30%.
There are lots of things to be done and we will continue working on the performance issues and I hope the next version will behave even better.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
By default the TextBox item which displays the data has no formatting applied to it. The developer who creates the report is responsible to set the appropriate format according to type of data displayed and the desired output. Moreover the generated output depends on the report definition (this is the Telerik.Reporting.Report derived object that you create through the Report Designer inside Visual Studio or programmatically by hand) and of course of the selected media. For more information please see Design Considerations for Report Rendering.
There are different reasons for the slow report rendering. Usually the large amount of data together with complex grouping and any other calculations that are performed in the report slows down the rendering. The new version Q1 2008 that we just released yesterday has some improvements in the Image/PDF/print rendering extension that can speed up the process with about 30%.
There are lots of things to be done and we will continue working on the performance issues and I hope the next version will behave even better.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0

Dragoljub
Top achievements
Rank 1
answered on 18 Apr 2008, 03:09 PM
Hello Telerik,
We didn't know a new version was out, so that's great news. We immediately downloaded them and installed them (after removing the old version).
Off course, as I expected according to what you said in your post, there isn't much improvement in the report generating speed. A report containing 5900 records is loaded with data end exported directly to pdf which is sent to client and displayed in browser as soon as it is received. The browser just shows the message "Waiting..." in the status bar for about 8 minutes, and then the pdf arrives in the iframe. (Grouping was not used)
Enough about that. I understand that generating a PDF is done using an API of some sort and you can't speed that up obviously, because it's not your job and you don't have the code (I suppose Adobe doesn't want to share their secrets). So what I'm saying is I understand it's not all up to you. For these special cases where more that 5000 records are involved, we display a message and ask the user if he wants to continue. And for even larger sets of data we'll make a simple HTML report (using a DataRepeater) or something like that.
I will use this opportunity to say something about the new version of Telerik Reporting. I only had time to see a few things, because of my assignments.
In the designer everything looks MUCH nicer, and The Nicest Feature Ever (also known as the "zoom feature") is now implemented so it's celebration time!
The right alignment on a textbox caused the rightmost letter to be cut off, and I heard and saw for myself that this bug is fixed also.
Now I'm looking forward to working with Telerik reports again to see what other improvements are there :)
We didn't know a new version was out, so that's great news. We immediately downloaded them and installed them (after removing the old version).
Off course, as I expected according to what you said in your post, there isn't much improvement in the report generating speed. A report containing 5900 records is loaded with data end exported directly to pdf which is sent to client and displayed in browser as soon as it is received. The browser just shows the message "Waiting..." in the status bar for about 8 minutes, and then the pdf arrives in the iframe. (Grouping was not used)
Enough about that. I understand that generating a PDF is done using an API of some sort and you can't speed that up obviously, because it's not your job and you don't have the code (I suppose Adobe doesn't want to share their secrets). So what I'm saying is I understand it's not all up to you. For these special cases where more that 5000 records are involved, we display a message and ask the user if he wants to continue. And for even larger sets of data we'll make a simple HTML report (using a DataRepeater) or something like that.
I will use this opportunity to say something about the new version of Telerik Reporting. I only had time to see a few things, because of my assignments.
In the designer everything looks MUCH nicer, and The Nicest Feature Ever (also known as the "zoom feature") is now implemented so it's celebration time!
The right alignment on a textbox caused the rightmost letter to be cut off, and I heard and saw for myself that this bug is fixed also.
Now I'm looking forward to working with Telerik reports again to see what other improvements are there :)
0

Dragoljub
Top achievements
Rank 1
answered on 18 Apr 2008, 03:18 PM
PS: I think there were about 250 pages in that report with 5900 records.
0
Hello Dragoljub,
We are very happy to hear that you like the new report designer and the rest of the new stuff that we've just released.
Regarding the performance, the truth is that the rendering is the slowest part and we have already started working on this. If everything goes as expected until the end of the year we will have a better performing rendering engine, which will exhibit much better results.
Once again thank you for the nice words and for the understanding of how complicated the rendering process as a whole is.
Regards,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We are very happy to hear that you like the new report designer and the rest of the new stuff that we've just released.
Regarding the performance, the truth is that the rendering is the slowest part and we have already started working on this. If everything goes as expected until the end of the year we will have a better performing rendering engine, which will exhibit much better results.
Once again thank you for the nice words and for the understanding of how complicated the rendering process as a whole is.
Regards,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0

JDP
Top achievements
Rank 1
answered on 05 Feb 2009, 12:45 PM
The link to Design Considerations for Report Rendering (ref. : http://www.telerik.com/community/forums/reporting/telerik-reporting/produce-output-in-windows-reportviewer-is-slow.aspx) is not functional.
0
Hello JDP,
The link must have got corrupted because we introduced new telerik.com site and some of the urls changed. We did add url forwarding for most but we might have missed some - anyway the link is now fixed.
All the best,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
The link must have got corrupted because we introduced new telerik.com site and some of the urls changed. We did add url forwarding for most but we might have missed some - anyway the link is now fixed.
All the best,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0

Rick Petersen
Top achievements
Rank 1
answered on 09 Jun 2009, 12:46 PM
The link is broken again.
I'm having a different issue but I'll post a separate thread for that... I just felt that this link may contain some info that would help me with my issue as well.
I'm having a different issue but I'll post a separate thread for that... I just felt that this link may contain some info that would help me with my issue as well.
0
Hi Rick,
Opening the Reporting help and using the search field to look for the Design Considerations for Report Rendering section should yield results. We make changes to our documentation all the time and cannot change obsolete links in the forums all the time.
Thank you for the understanding.
Kind regards,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Opening the Reporting help and using the search field to look for the Design Considerations for Report Rendering section should yield results. We make changes to our documentation all the time and cannot change obsolete links in the forums all the time.
Thank you for the understanding.
Kind regards,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.