Posted by ShineIT make your business SHINE on 24 Apr 2012 /
A client of us recently reported that PostgreSQL was running 100% CPU on their OpenERP server when they tried to ‘Compute Mrp Scheduler’, and the computation process wasn’t finished after the server had roared for 3 days.
The client is an e-commerce company who uses Mangento system as the front-end, the sale order status and inventory info on the Magento will then synchronise with the back-end OpenERP system. When thousands of sales orders imported into OpenERP through OpenERP-Mangento connector, OpenERP hence generated large amount of procurement orders correspondingly. We examined the code of mrp scheduler and found that the existing code will search through those procurement orders with sorting on an un-indexed field: planned_date, and thus the latency caused.
Further investigation found that the sorting is not really needed, simply remove it and added a condition to streamline the search returns. The result turn out great, the mrp calculation finished in 1 hour now. We also commit the transaction for every 500 procurements processed, so that the memory usage will also be in efficient. Our changes were accepted by the editor and merged into stable and trunk code base:
The release policy scheme is the following :
The release policy is based on an LTS release every 18 months, and a stable version every 6 months (ie. two stable releases...
Indeed. Shine IT don't need yet another badge or certificate to prove its capability of doing OpenERP project, as all the team members here have more than 4 years' hands-on experience with OpenERP and are the driving...
Every day, executives at small and midsize companies make critical business decisions based on uncoordinated information from a variety of sources: opinions from peers and colleagues; a personal sense...