Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0033569Openbravo ERPA. Platformpublic2016-07-29 15:132016-12-07 09:36
lorenzofidalgo 
NaroaIriarte 
urgentmajoralways
closedno change required 
5
main 
 
alostale
Google Chrome
Core
No
0033569: [RR16Q3][HighVol] Product selector is pretty slow in a Store Server configuration
Trying to get product values is slow (approximately 32 seconds). I have reproduced this situation in a Store server configuration with two store servers and one central server. One of the tests executed killed Chrome tab waiting for Product Selector. (Check attached videos and screenshot).
[1] https://drive.google.com/a/openbravo.com/file/d/0Bz1bUfkEffVIbDJZczl4di03SmM/view?usp=sharing [^]
[2] https://drive.google.com/a/openbravo.com/file/d/0Bz1bUfkEffVIUzlEUE5CRERteVk/view?usp=sharing [^]
0-Using a Store server configuration with two store servers and one central server login Store server as Openbravo.
1-Using "The White Valley Group Admin" as Role, go to "Sales Order" window.
2-Click create new record button and fill the record with the following data:
--
Organization: Vall Blanca Store
Transaction Document: VBS POS Order
Business Partner: Arturo Montoro
--
Save that record.
3-Go to "Lines" tab and press Ctrl + i to create a new record
4-In Product field, click magnifier. Realise this query takes too much time.
5-After, approximately, 32 seconds, values will be shown. Now click Clear Filters button and wait. Realise, again, it takes too long.
Performance
related to feature request 0033015 closed caristu Performance Improvements in Product Selector 
png ProductKillsOB.png (241,590) 2016-07-29 15:13
https://issues.openbravo.com/file_download.php?file_id=9658&type=bug
png
Issue History
2016-07-29 15:13lorenzofidalgoNew Issue
2016-07-29 15:13lorenzofidalgoAssigned To => platform
2016-07-29 15:13lorenzofidalgoFile Added: ProductKillsOB.png
2016-07-29 15:13lorenzofidalgoWeb browser => Google Chrome
2016-07-29 15:13lorenzofidalgoModules => Core
2016-07-29 15:13lorenzofidalgoTriggers an Emergency Pack => No
2016-07-29 15:14lorenzofidalgoTag Attached: Performance
2016-11-11 10:22lorenzofidalgoNote Added: 0091380
2016-11-11 10:22lorenzofidalgoWeb browserGoogle Chrome => Google Chrome
2016-11-11 10:22lorenzofidalgoPrioritynormal => high
2016-11-30 10:16NaroaIriarteAssigned Toplatform => NaroaIriarte
2016-11-30 10:16NaroaIriarteStatusnew => acknowledged
2016-11-30 10:17NaroaIriarteStatusacknowledged => scheduled
2016-12-01 13:17alostalePriorityhigh => urgent
2016-12-07 09:33NaroaIriarteStatusscheduled => acknowledged
2016-12-07 09:33NaroaIriarteStatusacknowledged => scheduled
2016-12-07 09:35NaroaIriarteReview Assigned To => alostale
2016-12-07 09:35NaroaIriarteNote Added: 0092158
2016-12-07 09:35NaroaIriarteStatusscheduled => closed
2016-12-07 09:35NaroaIriarteResolutionopen => no change required
2016-12-07 09:36NaroaIriarteRelationship addedrelated to 0033015

Notes
(0091380)
lorenzofidalgo   
2016-11-11 10:22   
This issue is still reproducible in RR16Q4
(0092158)
NaroaIriarte   
2016-12-07 09:35   
A vacuum full and an analyze has been executed in the database and now, the selector performs correctly.