Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0024430 | Openbravo ERP | A. Platform | public | 2013-07-29 18:35 | 2014-03-18 09:24 |
|
| Reporter | egoitz | |
| Assigned To | eduardo_Argal | |
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | Sandrahuguet |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0024430: The ReportGeneralLedger report take long to be printed with big amount of data and consumes a lot of resources |
| Description | The ReportGeneralLedger report take long to be printed with big amount of data, and while the report is being executed the server can not be used because a lot of resources are being consumed by the report.
When taking from fact_acct 500000 recoreds it takes 40 seconds to execute the select but 6 minutes to execute fillREport method on Httpsecureappservlert and 1,5 minutes to execute exportreporttopdf.
|
| Steps To Reproduce | -Execute a report on an environment with a arround 5.000.000 rows on the fact_acct for a interval where 500.000 rows are get. |
| Proposed Solution | http://stackoverflow.com/questions/15875199/jasperreports-fillreport-too-slow-and-resource-consuming [^]
http://community.jaspersoft.com/questions/536842/jasperreports-too-slow [^]
http://stackoverflow.com/questions/472522/jasperreport-taking-too-much-resources [^] |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0030694 | | closed | AtulOpenbravo | The ReportInvoiceDiscountJR report consume many resources when printing big amount of data. |
|
| Attached Files |  1MProducts.jrxml (2,545) 2013-10-06 16:09
https://issues.openbravo.com/file_download.php?file_id=6439&type=bug
 issue24430.diff (1,284) 2013-10-06 16:09
https://issues.openbravo.com/file_download.php?file_id=6440&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2013-07-29 18:35 | egoitz | New Issue | |
| 2013-07-29 18:35 | egoitz | Assigned To | => AugustoMauch |
| 2013-07-29 18:35 | egoitz | Modules | => Core |
| 2013-07-29 18:35 | egoitz | Triggers an Emergency Pack | => No |
| 2013-07-31 14:01 | alostale | Target Version | => 3.0MP27 |
| 2013-08-30 14:22 | AugustoMauch | Target Version | 3.0MP27 => 3.0MP28 |
| 2013-09-23 08:27 | alostale | Target Version | 3.0MP28 => 3.0MP29 |
| 2013-10-06 16:09 | iperdomo | File Added: 1MProducts.jrxml | |
| 2013-10-06 16:09 | iperdomo | File Added: issue24430.diff | |
| 2013-10-06 16:11 | iperdomo | Note Added: 0061556 | |
| 2013-10-06 16:20 | iperdomo | Note Added: 0061557 | |
| 2013-10-06 16:33 | iperdomo | Note Added: 0061558 | |
| 2013-10-07 13:10 | iperdomo | Note Added: 0061575 | |
| 2013-10-16 11:28 | egoitz | Description Updated | bug_revision_view_page.php?rev_id=5112#r5112 |
| 2013-10-28 10:36 | alostale | Assigned To | AugustoMauch => eduardo_Argal |
| 2013-10-28 16:51 | egoitz | Target Version | 3.0MP29 => 3.0MP30 |
| 2013-11-26 23:46 | jonalegriaesarte | Note Added: 0062390 | |
| 2013-11-26 23:46 | jonalegriaesarte | Type | defect => design defect |
| 2013-11-26 23:46 | jonalegriaesarte | Target Version | 3.0MP30 => |
| 2014-03-18 09:24 | Sandrahuguet | Review Assigned To | => Sandrahuguet |
| 2014-03-18 09:24 | Sandrahuguet | Note Added: 0065249 | |
| 2014-03-18 09:24 | Sandrahuguet | Status | new => closed |
| 2014-03-18 09:24 | Sandrahuguet | Resolution | open => fixed |
| 2015-08-28 12:53 | egoitz | Relationship added | related to 0030694 |
|
Notes |
|
|
|
|
Some of the links in the proposed solutions are related to XML parsing when using XML documents as datasource. This is not the case for the ReportGeneralLedger |
|
|
|
|
I have created a simple Product list to check if the problem is when building the data for the report, or the report generation itself.
The proposed way for handling large reports is using "report virtualizers"
http://community.jaspersoft.com/wiki/support-large-reports [^]
With 1M products in the database and different JVM options I measured some parts of the reports generation.
## JVM OPTS: -Xms256M -Xmx4096M -XX:MaxPermSize=512M
(no virtualizer)
fillReport: 258370 ms
exportReportToPdfFile: 52614 ms
Memory: 2.4 GB allocated / 1.9 GB used
Total: 312284 ms (5.20 min)
Using virtualizer (maxSize = 2)
fillReport: 255363 ms
exportReportToPdfFile: 60546 ms
Memory: 2.0 GB allocated / 1.6 GB used
Total: 317217 ms (5.28 min)
Using virtualizer (maxSize = 4)
fillReport: 263196 ms
exportReportToPdfFile: 62446 ms
Memory: 2.0 GB allocated / 1.5 GB used
Total: 326966 ms (5.44 min)
Using virtualizer (maxSize = 6)
fillReport: 264471 ms
exportReportToPdfFile: 58343 ms
Memory: 2.2 GB allocated / 1.5 GB Used
Total: 324134 ms (5.40 min)
## JVM OPTS = -Xms256M -Xmx2048M -XX:MaxPermSize=256M
Using virtualizer (maxSize = 6)
fillReport: 259962 ms
exportReportToPdfFile: 58842 ms
Memory: 1.3 GB allocated / 892 MB used
Total: 320106 ms (5.40 min)
## JVM OPTS = -Xms128M -Xmx1024M -XX:MaxPermSize=256M
Using virtualizer (maxSize = 6)
fillReport: 268572 ms
exportReportToPdfFile: 62131 ms
Memory: 1018 MB allocated / 808 MB used
Total: 331975 ms (5.53 min)
Conclusion? It seems that using JRFileVirtualizer helps the process to use less memory without impacting too much in the overall generation time |
|
|
|
|
I would suggest that the large memory usage is also related to the way the report is built. By loading all the records in memory, and then calculating totals group.
As you can see just printing 1M products, takes ~6min.
As the issue description states, the problem to tackle is the 40min report generation. |
|
|
|
|
The process of generating data can be split per account and/or group, generating a pdf document. After the parts can be concatenated.
The class PrintController has code showing how to contatenate different PDFs documents. |
|
|
|
|
|
Moved to design defect, because we need to analyze in depth the behavior of the report |
|
|
|
|
|