Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0044611
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Retail Modules] Mobile Warehouse operationsmajoralways2020-07-14 19:522020-08-21 09:25
ReportergsuarezView Statuspublic 
Assigned ToRetail 
PriorityhighResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0044611: Bad performance into the selector on Lookup Process

DescriptionThe customer had been have several performance problem when they trying to filter into this selector into the lookup process over a warehouse with a lot of tasks rows (this around to 1.800.000). After apply the filter, the response take more than3 minutes to provide the results.

We detect the problem into the query used to filter where this try to compare the filter condition in different entities at the same time (Product, Bin and Attribute Set Instance) using the OR operator. We execute this query by each entity and we get a better performance activity in each case.
Steps To ReproducePrepare an environment with a lot of data to apply the filter (you can use the environment test of customer).
open the Mobile Warehouse Operation
open the selector where you pick the products into the lookup process.
Search for any product.
Proposed SolutionAs workaround we change the behavior of the query and we restrict the use of the filter only by BIN.
TagsNo tags attached.
Attached Filesdiff file icon Inventory.diff [^] (1,301 bytes) 2020-07-14 19:53 [Show Content]

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0121452)
gsuarez (reporter)
2020-07-14 19:55

We modified the next java class as workaround to this.

modules/org.openbravo.warehouse.advancedwarehouseoperations/src/org/openbravo/warehouse/advancedwarehouseoperations/mobile/datasources/Inventory.java
(0122106)
guilleaer (manager)
2020-08-17 18:48

modules/org.openbravo.warehouse.advancedwarehouseoperations/src/org/openbravo/warehouse/advancedwarehouseoperations/mobile/datasources/Inventory.java

Above servlet is ready to manage contains preference but it is not ready to use strict preference

http://wiki.openbravo.com/wiki/Modules:Advanced_Warehouse_Operations#Device_Search_Mode [^]

Solution should consist on create strict preference and take it into account while query is executed.
(0122230)
marvintm (manager)
2020-08-21 09:25

We have changed this issue to design defect. In the end, the only solution we have for these kinds of problems is to refactor the selector so that the user specifies which property he wants to filter by, like we did in the WebPOS with the customer or receipt selectors.

This change however is not trivial, and that's why we changed it to design defect.

- Issue History
Date Modified Username Field Change
2020-07-14 19:52 gsuarez New Issue
2020-07-14 19:52 gsuarez Assigned To => Retail
2020-07-14 19:52 gsuarez Resolution time => 1596492000
2020-07-14 19:52 gsuarez Triggers an Emergency Pack => No
2020-07-14 19:53 gsuarez File Added: Inventory.diff
2020-07-14 19:55 gsuarez Note Added: 0121452
2020-08-17 18:48 guilleaer Note Added: 0122106
2020-08-21 09:25 marvintm Resolution time 1596492000 =>
2020-08-21 09:25 marvintm Note Added: 0122230
2020-08-21 09:25 marvintm Type defect => design defect


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker