Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0020339 | Openbravo ERP | I. Performance | public | 2012-04-24 16:46 | 2012-04-26 12:07 | |||||||
Reporter | egoitz | |||||||||||
Assigned To | marvintm | |||||||||||
Priority | immediate | Severity | major | Reproducibility | always | |||||||
Status | closed | Resolution | duplicate | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | 3.0MP10 | |||||||||||
Target Version | 3.0MP12 | Fixed in Version | ||||||||||
Merge Request Status | ||||||||||||
Review Assigned To | ||||||||||||
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 | 0020339: Linked items takes longs to be loaded when the tables fin_orig_payment_schedule and fin_orig_paym_scheddetail had arround 15000 | |||||||||||
Description | When the tables fin_orig_payment_schedule and fin_orig_paym_scheddetail had arround 15000 rows the linked items need a lot to be calculated. There are two tabs using the view fin_orig_payment_sched_v wich also use the previously explained tables. On this case when executing linked items on a sales order it takes long to find the tabs. | |||||||||||
Steps To Reproduce | -On an environment with 9000 rows at fin_orig_payment_schedule table and 17000 on fin_orig_paym_scheddetail table, open linked items sections. It needs a lot to be opened. The problem is that if this table increases the performance of the application could be affected. Also notice that on view used for the tabs referenced there are used many tables that have not indexes. A list of possible needed indexes (these thas not solve the problems but has sense to analyze it could be included) CREATE INDEX fin_orig_paym_schdet_fpsd ON fin_orig_paym_scheddetail USING btree (fin_payment_scheduledetail_id); CREATE INDEX fin_payment_scheduledetail_fpd ON fin_payment_scheduledetail USING btree (fin_payment_detail_id); CREATE INDEX fin_payment_detail_fp ON fin_payment_detail USING btree (fin_payment_id); CREATE INDEX fin_orig_paym_schdet_fps ON fin_orig_paym_scheddetail USING btree (fin_orig_payment_schedule_id); | |||||||||||
Proposed Solution | ||||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2012-04-24 16:46 | egoitz | New Issue | ||||||||||
2012-04-24 16:46 | egoitz | Assigned To | => marvintm | |||||||||
2012-04-24 16:46 | egoitz | Modules | => Core | |||||||||
2012-04-24 16:47 | egoitz | Priority | urgent => immediate | |||||||||
2012-04-26 12:07 | egoitz | Relationship added | duplicate of 0020358 | |||||||||
2012-04-26 12:07 | egoitz | Status | new => closed | |||||||||
2012-04-26 12:07 | egoitz | Resolution | open => duplicate |
There are no notes attached to this issue. |