Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0009241 | Openbravo ERP | 09. Financial management | public | 2009-05-29 12:53 | 2009-06-30 00:00 |
|
Reporter | networkb | |
Assigned To | dalsasua | |
Priority | immediate | Severity | major | Reproducibility | always |
Status | closed | Resolution | duplicate | |
Platform | | OS | 30 | OS Version | |
Product Version | 2.40MP3 | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | OBPS |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0009241: The general ledger journal gets very slow when lots of journal are in the system. |
Description | The general ledger journal gets very slow when lots of journal are in the system. |
Steps To Reproduce | -Go to a application with lots of journal
-Enter filters to show all the informatino of the journal
-Print de report
-It takes many time to show the report. |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | duplicate of | defect | 0009560 | | closed | eduardo_Argal | The background process goes to a infinite loop when the partner has not a account on the accoounting tab. | related to | defect | 0009242 | | closed | dalsasua | When entering in the Generl Ledger Journal report the report shouldn't be executed automatically | depends on | backport | 0009337 | | closed | dalsasua | The general ledger journal gets very slow when lots of journal are in the system. |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2009-05-29 12:53 | networkb | New Issue | |
2009-05-29 12:53 | networkb | Assigned To | => rafaroda |
2009-05-29 12:53 | networkb | OBNetwork customer | => Yes |
2009-05-29 16:10 | rafaroda | Note Added: 0016771 | |
2009-05-29 16:10 | rafaroda | Assigned To | rafaroda => dalsasua |
2009-06-01 08:41 | dalsasua | Note Added: 0016786 | |
2009-06-01 08:41 | dalsasua | Status | new => feedback |
2009-06-02 22:51 | azabaleta | Note Added: 0016892 | |
2009-06-02 22:51 | azabaleta | Issue Monitored: azabaleta | |
2009-06-03 08:41 | pnuding | Status | feedback => new |
2009-06-04 16:40 | dalsasua | Status | new => scheduled |
2009-06-04 16:40 | dalsasua | fix_in_branch | => pi |
2009-06-16 12:33 | rafaroda | Note Edited: 0016771 | |
2009-06-26 14:45 | dalsasua | Relationship added | related to 0009242 |
2009-06-26 14:47 | dalsasua | Note Added: 0017616 | |
2009-06-29 19:41 | networkb | Relationship added | duplicate of 0009560 |
2009-06-29 19:41 | networkb | Status | scheduled => closed |
2009-06-29 19:41 | networkb | Note Added: 0017651 | |
2009-06-29 19:41 | networkb | Duplicate ID | 0 => 9560 |
2009-06-29 19:41 | networkb | Resolution | open => duplicate |
2009-06-30 00:00 | anonymous | sf_bug_id | 0 => 2814264 |
Notes |
|
(0016771)
|
rafaroda
|
2009-05-29 16:10
(edited on: 2009-06-16 12:33) |
|
David,
Could you please determine whether this issue has to be assigned to Performance team?
Thank you.
|
|
|
|
It's needed that reporter specifies what does "lots" mean: one hundred, one thousand, a hundred thousand, one million, one thousand millions, one trillion? Moreover, if the problem is to have "lots" of rows in the fact_acct table (so number of entries -posted documents- in the system), if the problem is that "lots" of rows must be shown in the report (so length of the report), or if the problem is other one?
Thanks. Regards. |
|
|
|
5 million entries in fact_Acct table.
There are 2 different problems.
1.- When clicking in the menu on General Ledger Journal, the report is executed. It shouldnt. It should show the filters, and the user should execute it when wanted.
2.- Once the filters are selected, it is still very slow although only shows +-journals in the first page of the report. Showing that should be instantaneous.
Regards. |
|
|
|
|
|
|
it was not a performance issue but an issue related to the accounting background process |
|