Skip to content

[WIP][FWD][17.0][PERF] mrp: optimize move_finished_ids update to improve backorder creation performance for serial-tracked production#1114

Open
viinbot wants to merge 1 commit into17.0from
fwd-from-pr-1113-to-17.0
Open

[WIP][FWD][17.0][PERF] mrp: optimize move_finished_ids update to improve backorder creation performance for serial-tracked production#1114
viinbot wants to merge 1 commit into17.0from
fwd-from-pr-1113-to-17.0

Conversation

@viinbot
Copy link

@viinbot viinbot commented Jul 1, 2025

https://github.com/odoo/odoo/pull/216537
Previously, all move_finished_ids in non-done state were updated regardless of whether their date or date_deadline values actually changed. This led to unnecessary write operations and potential slowdowns, especially in serial-tracked production where each finished product line generates a separate stock.move.

This update improves the performance of completing manufacturing orders that produce serial-tracked finished products.


I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: #1113

creation performance for serial-tracked production

Previously, all move_finished_ids in non-done state were updated
regardless of whether their date or date_deadline values actually
changed. This led to unnecessary write operations and potential
slowdowns, especially in serial-tracked production where each finished
product line generates a separate stock.move.

This update improves the performance of completing manufacturing orders
that produce serial-tracked finished products.

Forward-Port-Of: #1113
@viinbot
Copy link
Author

viinbot commented Jul 1, 2025

@phamgiang2510 cherrypicking of PR #1113 failed, failed with output:

Auto-merging addons/mrp/models/mrp_production.py
CONFLICT (content): Merge conflict in addons/mrp/models/mrp_production.py
error: could not apply 0f2da4a8700... [PERF] mrp: optimize move_finished_ids update to improve backorder
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

You must resolve the conflicts on the PR manually (and push to this branch).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants