I just started using telerik reporting and I'm wondering about this scenario. Basically, I created a business object based report with two levels of grouping. I'm accessing it through the web viewer and I'm sending it a list of Ienumerable<object>. There are about 24000 rows in the inenumerable. The report gets it, but it takes almost 2 minutes to render (it takes 2 seconds to get the data). The report winds up being 1900 pages. I'm wondering, are the pages loaded on demand? Is there some kind of way to speed this up by loading a page at a time?
3 Answers, 1 is accepted
0
Hello Jason,
The current version of the reporting tool would experience performance problems when the datasource contains a lot of rows and the layout of the report predisposes the creation of reports with huge amounts of pages.
Here are a few things you can try:
We recommend to avoid using PageCount because it requires an additional pass to count all pages before the actual report rendering (i.e. it renders the report in the memory in order to count all pages). Another option is to reconsider the size of the data you need to display at once (by using parameters and/or filters rather than to show all the raw data from the data source). In contrast to Grid controls, where usually a small subset of data records are displayed, the reporting engines need all the data to layout the pages depending on the selected media (output format). So if your main goal is to show this data for web presentation only, we can suggest a web grid control instead, moreover our RadGrid control exposes API for pdf, csv, word, excel exporting.
Reviewing the Performance Considerations KB article for other optimizations is highly recommended.
The good news is that we're working on major performance improvements for the Q1 2010 scheduled for beginning of March, which would introduce a new data engine (using declarative datasources) along with faster processing of report using styles - more info is available in our RoadMap.
So in short we hope that this change would improve drastically the performance (and partly memory) problems.
Greetings,
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.
The current version of the reporting tool would experience performance problems when the datasource contains a lot of rows and the layout of the report predisposes the creation of reports with huge amounts of pages.
Here are a few things you can try:
We recommend to avoid using PageCount because it requires an additional pass to count all pages before the actual report rendering (i.e. it renders the report in the memory in order to count all pages). Another option is to reconsider the size of the data you need to display at once (by using parameters and/or filters rather than to show all the raw data from the data source). In contrast to Grid controls, where usually a small subset of data records are displayed, the reporting engines need all the data to layout the pages depending on the selected media (output format). So if your main goal is to show this data for web presentation only, we can suggest a web grid control instead, moreover our RadGrid control exposes API for pdf, csv, word, excel exporting.
Reviewing the Performance Considerations KB article for other optimizations is highly recommended.
The good news is that we're working on major performance improvements for the Q1 2010 scheduled for beginning of March, which would introduce a new data engine (using declarative datasources) along with faster processing of report using styles - more info is available in our RoadMap.
So in short we hope that this change would improve drastically the performance (and partly memory) problems.
Greetings,
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.
0
Levi
Top achievements
Rank 1
Rank 1
answered on 12 Jul 2010, 08:38 PM
With the major improvements you mentioned for your latest release what is the max amount of rows before you start seeing the reports slowing down?
0
Hello Levi,
My last post was referring to the Q1 release, which would be replaced with Q2 later today. Anyway we have not made purposeful performance tests of this release, but judging by the improvement in the demo reports we provide, you should expect improvement with at least 15% or more depending on the structure of your report. Just to note, it is not only the number of database rows that matters when it comes to performance, but the number of report pages created is also crucial.
We strongly suggest you go ahead and try our product and if you have any specific problems - let us know.
Sincerely yours,
Steve
the Telerik team
My last post was referring to the Q1 release, which would be replaced with Q2 later today. Anyway we have not made purposeful performance tests of this release, but judging by the improvement in the demo reports we provide, you should expect improvement with at least 15% or more depending on the structure of your report. Just to note, it is not only the number of database rows that matters when it comes to performance, but the number of report pages created is also crucial.
We strongly suggest you go ahead and try our product and if you have any specific problems - let us know.
Sincerely yours,
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