Contributors mailing list archives
contributors@odoo-community.org
Browse archives
RE: stock.picking very slow and some are not validating
byMD
My apologies I spoke too soon. Just had a look at what we do and all we do is
- On button submit, instead of processing on the users screen we submit a background task that runs every minute and then effectively runs the submit logic
- We split out invoice create ( we have a module which creates the draft supplier invoice) as a separate task.
We have found that when you add lots or serial numbers (which means stock.move.line records) things slow down considerably.
It would be possible to extend our module to handle each stock move line as a separate commit – looking at our largest customer the longest background task has taken 5 minutes
Regards Kevin
From: MD Tanzilul Hasan Khan <ponkhi403@gmail.com>
Sent: Thursday, 13 February 2020 5:48 PM
To: Contributors <contributors@odoo-community.org>
Subject: Re: stock.picking very slow and some are not validating
Did you create automated action for move lines?
As we are using track by lots (can be unique or use existing), how are you managing the lot creation or update? Won’t it create 400 backorders if you are validating one by one ?
Thanks
On Feb 13, 2020 at 1:51 AM, <Kevin McMenamin> wrote:
We have had similar – we have a client receiving ~400 lines on a PO. There are issues around average cost calculation. Our solution was to make the receipting a background process and receipt line by line – that way if anything happens to a product during the receipt cycle you don’t get a full roll back.
Contact me below if you would like to discuss further.
Regards
Kevin McMenamin
ERP Capability Manager, Solnet
+64 22 651 3753 | +64 9 977 5805 | Visit our blog | Connect on LinkedIn
From: MD Tanzilul Hasan Khan <ponkhi403@gmail.com>
Sent: Monday, 3 February 2020 8:02 PM
To: Contributors <contributors@odoo-community.org>
Subject: stock.picking very slow and some are not validating
Hello Contributors,
We are using Odoo 11 for a retail chain. They have over 60 POS locations (and increasing across the country) and over 17000 products (also increasing).
Recently, for past two months, we are facing strange problem. The retail chain do purchase order once in a month to the vendor and the PO contains over hundreds of products. They are using lot based tracking. When we are receiving products with lot number it takes forever to validate. Even some pickings are stuck and can't be validated. We tried all the possible workarounds but still no luck. There are no errors too.
The instance is running on AWS with RDS. RDS configuration:
PostgreSQL - 10.10
4 vcpu x 16 GB RAM
100 GB SSD
IOPS: 100 * 3 = 300
How can we validate the stock.pickings? Any idea or thoughts appreciated.
Best Regards,
MD. Tanzilul Hasan Khan
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribeAttention: This email may contain information intended for the sole use of the original recipient. Please respect this when sharing or disclosing this email's contents with any third party. If you believe you have received this email in error, please delete it and notify the sender or postmaster@solnetsolutions.co.nz as soon as possible. The content of this email does not necessarily reflect the views of Solnet Solutions Ltd.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List:
https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe:
https://odoo-community.org/groups?unsubscribe
Reference
-
stock.picking very slow and some are not validating
byponkhi403-
RE: stock.picking very slow and some are not validating
byKevin McMenamin -
RE: stock.picking very slow and some are not validating
byKevin McMenamin
-