You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Divesh Dutta (JIRA)" <ji...@apache.org> on 2010/04/14 11:36:08 UTC

[jira] Updated: (OFBIZ-3697) setLastInventoryCount Service should not be called hourly due to performance issues.

     [ https://issues.apache.org/jira/browse/OFBIZ-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Divesh Dutta updated OFBIZ-3697:
--------------------------------

    Attachment: OFBiz-3697.patch

This patch solves the following problem:

1) Now setLastInventoryCount service will run as EECA (on InventoryItemDetail entity, such that availableToPromiseDiff != 0) and updates lastInventoryCount for products available in facility in ProductFacility entity

2) So setLastInventoryCount service will only run for products whose ATPs are changed, not for all the products in every one hour. So definitely this will improve the performance of the server. 

3) Also lastInventoryCount value is updated according to facility.  

> setLastInventoryCount Service should not be called hourly due to performance issues.
> ------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-3697
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3697
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Divesh Dutta
>             Fix For: SVN trunk
>
>         Attachments: OFBiz-3697.patch
>
>
> 1) In case of large database, when there are so many products into the system, then setLastInventoryCount service consider all the products and update records for them.
> 2) So it will keep server busy for some time in every one hour. This logic should be improved. 
> 3) Also setLastInventoryCount service does not take facilityId into the account while setting last inventory count in ProductFacility entity. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira