Large Report Problems

[SergeyB]

When we run a large report (2500 pages) we see two main problems - Render method takes many minutes to execute (minimum of 5 minutes, sometimes as long as 15). Memory for the process that is rendering jumps by 2 GB in the process. Neither issue is an acceptable one for our clients. Any suggestions are appreciated.

Thank you.

[HighAley]

Hello.

When we run a large report (2500 pages) we see two main problems - Render method takes many minutes to execute (minimum of 5 minutes, sometimes as long as 15). Memory for the process that is rendering jumps by 2 GB in the process. Neither issue is an acceptable one for our clients. Any suggestions are appreciated.

It seems that you should optimize your report.
Could you send us your report template with sample data to reproduce the issue for analysis?

Thank you.

[SergeyB]

I do not think it has anything to do with one report or another. I simplified this report to just have flat printout of about 5 columns of data. The issue is that the dataset has 200000 rows, so report is about 6000 pages long. Just create the same scenario, and you will see that the report takes 3 minutes and over 1 GB or RAM. If I add some summary pages, then the reports takes 5 minutes and 2 GB or RAM.
Thank you.

[HighAley]

Hello.

We are working on the optimization of our algorithms. We made some improvements that way. Please, check our next release build that will be available today.

Thank you.

[SergeyB]

Thanks, Aleksey.
On a related note, did your improvements affect PDF generation? We have exact same problem with PDF generation of reports that are very large, 10,000 pages or more. The server just dies during those operations, running out of RAM.

[HighAley]

Hello.

We need more information about your issue to help you with optimization.
Could you send us a report template with data to reproduce the issue?

Thank you.