0022428: Performance problem when there is a large number of products

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0022428

Retail Modules

Web POS

public

2012-11-29 14:08

2012-12-20 13:58

Reporter

marvintm

Assigned To

adrianromero

Priority

normal

Severity

major

Reproducibility

always

Status

closed

Resolution

duplicate

Platform

OS Version

Product Version

Target Version

RMP18

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0022428: Performance problem when there is a large number of products

Description

There is a performance problem when there is a large number of products. The problem has been reproduced with 19000 products.

The problem happens even if there is a limit in the number of displayed products, and occurs due to the way the products are currently stored and rendered.

As the prices are currently stored in a separate table, we do a separate query and then iterate for all the prices until the product we want to set the price for is found. This is very costly in performance, and it scales poorly with the number of products and prices.

Also, the problem is exacerbated due to the fact that prices for all products in the defined pricelist are loaded, regardless of the existance of those products in the assortment. So, if an assortment of 5 products is defined, but there are 20000 products in the system, the initial renderization of the POS will still be very slow.

Steps To Reproduce

- Create a large number of products in the system, each with their price correctly defined in the pricelist.
- Create an assortment which contains all products. Notice that when doing login in the POS, the browser gets completely locked up for 15-20 seconds.
- Create an assortment of five products. Notice that basically the same thing happens (due to the fact that all prices were loaded regardless of the new assortment).

Proposed Solution

Both problems should be fixed:
- We should load only prices for the products in the current assortment.
- We shouldn't iterate through all the prices to find the correct price for a product.

Additional Information