Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0018313Openbravo ERPA. Platformpublic2011-08-18 13:522011-10-12 01:58
0018313: Bad performance of the partner selector having arround 100.000 partners
In an application with arround 100.000 partners, the partner selector takes long to show the information, and also so filter data.
-Enter 100.000 partners with location on the partner table. (you can use idl or a database script.
-Go to sales invoice.
-Create a new invoice
-Open de partner selector.
*It takes long to show and filter the data.
No tags attached.
related to defect 00181073.0MP4 closed alostale several minutes the CPU to 100 % when the table "product_price" has got a big number of records 
Issue History
2011-08-18 13:52egoitzNew Issue
2011-08-18 13:52egoitzAssigned To => alostale
2011-08-18 13:52egoitzModules => Core
2011-08-18 13:54egoitzResolution time => 1315951200
2011-08-29 13:06alostaleRelationship addedrelated to 0018107
2011-08-29 13:07egoitzTarget Version2.50MP33 => 3.0RC4
2011-08-29 13:08egoitzTarget Version3.0RC4 => 3.0MP4
2011-09-15 13:44jonalegriaesarteAssigned Toalostale => marvintm
2011-09-15 13:45jonalegriaesartePriorityurgent => immediate
2011-09-19 11:47hgbotCheckin
2011-09-19 11:47hgbotNote Added: 0041061
2011-09-19 11:47hgbotStatusnew => resolved
2011-09-19 11:47hgbotResolutionopen => fixed
2011-09-19 11:47hgbotFixed in SCM revision => [^]
2011-09-21 12:19egoitzNote Added: 0041192
2011-09-21 12:19egoitzStatusresolved => closed
2011-09-21 12:19egoitzFixed in Version => 3.0MP4
2011-10-12 01:58hudsonbotCheckin
2011-10-12 01:58hudsonbotNote Added: 0041672

2011-09-19 11:47   
Repository: erp/devel/pi
Changeset: 7e3fb4e2e7d47d19406164738be63882fb51bde2
Author: Antonio Moreno <antonio.moreno <at>>
Date: Mon Sep 19 11:46:47 2011 +0200
URL: [^]

Fixed issue 18313. Performance of the Business partner selector has been improved.
A big improvement has been made by removing the count which (obviously) included retrieving all the selected records. However, although the selector is now usable, performance is still not ideal. To further improve it, separating the selector into multiple ones (ie. not having a business partner/business partner location/ business partner attributes selector) should be considered, because the custom query (which includes a 'distinct' operator) is what is currently killing performance.

M modules/org.openbravo.service.datasource/src/org/openbravo/service/datasource/
M modules/org.openbravo.userinterface.selector/src/org/openbravo/userinterface/selector/
2011-09-21 12:19   
2011-10-12 01:58   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: [^]

Maturity status: Test