Ando Ramahavalisoa
Top achievements
Rank 1
Rank 1
Ando Ramahavalisoa
asked on 15 Oct 2013, 12:37 PM
Hello there,
We have just downloaded recently a trial version of Telerik Reporting, its Q3 version released.
And before buying the product, our project manager asked us to make some test, essentially some "performance" tests...
Actually, I produced a report with 500 lines from database. Those lines will be grouped by two columns, and of course : the rendered table contains some agregate value (Sum).
Curiously, the RenderReport() took about 1 minute to render these 500 lines, no matter what the output format is (pdf, mhtml, xls, ...) :-(
Notice that I have put many debug breakpoints to check exactly where the performance lack resides, and thus; found that it occured when I call the RenderReport() method. In other words, the problem is not related to database access.
I tryied to remove the agregate cells, but it didn't change nothing. By the same way, I removed the grouping column, and of course, the report took about 40 seconds to be rendered, but I think it's not normal at all, cause we treated actually 500 lines, and in the future; we surely will need to produce more than 1000 lines inside one report.
Is there any known issue to avoid this performance trouble ? I just want to add eventually that the old report engine that we used was oracle-report, and we plan to go with some other third party technologies like Telerik. But with oracle-report, the same report was rendered after about 10 seconds, on the same machine, accessing the same database, with the same code architecture (asp.net mvc)
Thanks in advance
We have just downloaded recently a trial version of Telerik Reporting, its Q3 version released.
And before buying the product, our project manager asked us to make some test, essentially some "performance" tests...
Actually, I produced a report with 500 lines from database. Those lines will be grouped by two columns, and of course : the rendered table contains some agregate value (Sum).
Curiously, the RenderReport() took about 1 minute to render these 500 lines, no matter what the output format is (pdf, mhtml, xls, ...) :-(
Notice that I have put many debug breakpoints to check exactly where the performance lack resides, and thus; found that it occured when I call the RenderReport() method. In other words, the problem is not related to database access.
I tryied to remove the agregate cells, but it didn't change nothing. By the same way, I removed the grouping column, and of course, the report took about 40 seconds to be rendered, but I think it's not normal at all, cause we treated actually 500 lines, and in the future; we surely will need to produce more than 1000 lines inside one report.
Is there any known issue to avoid this performance trouble ? I just want to add eventually that the old report engine that we used was oracle-report, and we plan to go with some other third party technologies like Telerik. But with oracle-report, the same report was rendered after about 10 seconds, on the same machine, accessing the same database, with the same code architecture (asp.net mvc)
Thanks in advance
2 Answers, 1 is accepted
0
Dev
Top achievements
Rank 1
Rank 1
answered on 17 Oct 2013, 03:39 PM
which type of telerik report had you used ? you should use telerik report designer as possible ( reports are in trdx format).
we've also noticed that issue still occur despite of a little improvement but not signifiant.
For that reason we gave up on Telerik and used MS Report.
we've also noticed that issue still occur despite of a little improvement but not signifiant.
For that reason we gave up on Telerik and used MS Report.
0
Hi Ando,
Handling reports (be it with large data or large number of report items) usually requires additional resources in terms of powerful CPUs, and enough memory to handle all the operations. As far as the processing time 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.
If you are dealing with a large data sets, perhaps in your specific scenario another component such as our RadGrid control might be more appropriate, moreover our RadGrid control offers several export options.
Another option is to use Report Parameters in order to render only a part of your data and not all of it. A result set can be based on id range or date range for example and this way your user would select only the data he needs. More suggestions are listed in our Performance Considerations help article.
If you need further help, please open a support thread and send us a sample project illustrating your scenario that we can profile at our side.
Regards,
Peter
Telerik
Handling reports (be it with large data or large number of report items) usually requires additional resources in terms of powerful CPUs, and enough memory to handle all the operations. As far as the processing time 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.
If you are dealing with a large data sets, perhaps in your specific scenario another component such as our RadGrid control might be more appropriate, moreover our RadGrid control offers several export options.
Another option is to use Report Parameters in order to render only a part of your data and not all of it. A result set can be based on id range or date range for example and this way your user would select only the data he needs. More suggestions are listed in our Performance Considerations help article.
If you need further help, please open a support thread and send us a sample project illustrating your scenario that we can profile at our side.
Regards,
Peter
Telerik
Have you tried the new visualization options in Telerik Reporting Q2 2013? You can get them from your account.