Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0039387 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Modules] Multi-Dimensional Profit And Loss | major | always | 2018-10-02 09:44 | 2020-01-20 14:06 | |||||||
Reporter | JONHM | View Status | public | |||||||||
Assigned To | Triage Omni OMS | |||||||||||
Priority | high | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Regression date | ||||||||||||
Regression introduced by commit | ||||||||||||
Regression level | ||||||||||||
Review Assigned To | ||||||||||||
Regression introduced in release | ||||||||||||
Summary | 0039387: Performance issue on multi-dimensional profit and loss report | |||||||||||
Description | Performance issue on multi-dimensional profit and loss report. When running report for 4 months of data, the process takes too long and the server gets overloaded. | |||||||||||
Steps To Reproduce | Run multi-dimensional profit and loss report *Org: * *General Ledger: A general ledger with lots of data *Year: Current year *Period from: Feb *Period to: May *Column: Organization, Business Partner *Row: Product | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0107563) dmiguelez (developer) 2018-10-25 10:12 |
This is not an Issue. Based on the volumes of data of the client, it is impossible to do the CrossJoin they are proposing. 70 organizations * 35.048 bpartners * 31.975 products * 5.298.609 records in the fact table = 4,15 * 10^17 Mondrian itself is raising this problem: 'ResourceLimitExceededException: Mondrian Error: Size of CrossJoin result (21,974,101) exceeds limit (5,000,000)' In this case the filters must be used to reduce the amount of data calculated and shown. It would be nice if the application itself raises this problem to the user before attempting to launch the query. The design defect that can be solved is to count the amount of records that each dimension is going to cross and, if it is higher than 100, raise an error forcing the user to select a filter. |
Issue History | |||
Date Modified | Username | Field | Change |
2018-10-02 09:44 | JONHM | New Issue | |
2018-10-02 09:44 | JONHM | Assigned To | => Triage Finance |
2018-10-02 09:44 | JONHM | Resolution time | => 1540245600 |
2018-10-02 11:28 | martinsdan | Issue Monitored: martinsdan | |
2018-10-23 09:37 | JONHM | Resolution time | 1540245600 => 1541458800 |
2018-10-25 10:03 | JONHM | Steps to Reproduce Updated | View Revisions |
2018-10-25 10:12 | dmiguelez | Note Added: 0107563 | |
2018-10-25 10:12 | dmiguelez | Type | defect => design defect |
2020-01-20 14:06 | ngarcia | Resolution time | 1541458800 => |
Copyright © 2000 - 2009 MantisBT Group |