Project:
View Revisions: Issue #33015 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0033015: Performance Improvements in Product Selector | ||
Revision | 2016-05-20 14:38 by caristu | ||
Description | The Product (by Price and Warehouse) selector has performance problems in environments with big amount of data, specially in those with a lot of records in the following tables: m_product, m_product_price, m_warehouse, m_storage_detail and m_storage_pending. Together with this, some improvements can be applied to selectors in general, in order to have a better performance: 1) Apply default filtering criteria for FK using ID 2) Retrieve just the necessary properties for the selector drop-down requests 3) Unnecessary query is performed in the selector datasource when sending the targetRecordId parameter with null value. 4) If possible, apply inner join instead of left join for those properties used for sorting the results returned by the datasource. Project Link: http://wiki.openbravo.com/wiki/Projects:Selector_Performance_Improvements [^] |
||
Revision | 2016-05-20 11:27 by caristu | ||
Description | The Product (by Price and Warehouse) selector has performance problems in environments with big amount of data, specially in those with a lot of records in the following tables: m_product, m_product_price, m_warehouse, m_storage_detail and m_storage_pending. Together with this, some improvements can be applied to selectors in general, in order to have a better performance: 1) Apply default filtering criteria for FK using ID 2) Retrieve just the necessary properties for the selector drop-down requests 3) Unnecessary query is performed in the selector datasource when sending the targetRecordId parameter with null value. 4) If possible, apply inner join instead of left join for those properties used for sorting the results returned by the datasource. |
Copyright © 2000 - 2009 MantisBT Group |