odoo/upgrade#8447

Created by Upgrade, Carsten Wolff (cawo)

Blocked

label
odoo-dev:master-imp_parallel_iter_browse-cawo
head
7165744431f543f09c4888584d0c9a4a8711378c
odoo/upgrade odoo/upgrade-util
master #8447 missing r+ #320 missing r+

[IMP] {account,mrp}/saas~13.4: make use of // util.iter_browse

see odoo/upgrade-util#320

[IMP] mrp/saas~13.4.2.0: make use of // util.iter_browse

Basically, this moves the implementation of the parallel workorder creation into the util in a more generic way, making it thus available to other scripts, too.

Performance of this script with UPG_PARALLEL_ITER_BROWSE set instead of ODOO_UPG_14_PARALLEL_WORKORDER_CREATION does not change, as expected.

Tested using:
upg-3171223

[IMP] account/saas~13.4.1.1: make use of // util.iter_browse

see odoo/upgrade-util#320

Similar to the parent commit that uses the new implementation of parallelism in util.iter_browse.__attr__(), this change makes use of the new implementation of parallelism in util.iter_browse.create(), as well as the new possibility to pass a query that yields values instead of a list of value-dicts.

Tested using:
upg-3137540

Before:

2025-09-20 18:24:31,547 24 INFO db_3137540 odoo.upgrade.account.saas-13.4.end-09-payment-refactoring: Creating 2478497 moves for draft statement lines
2025-09-21 07:09:24,246 24 INFO db_3137540 odoo.upgrade.util: [99.88%] 826/827 chunks processed in 12:44:52.699482 (total estimated time: 12:45:48.259651)

After:

2025-10-09 10:55:28,077 26 INFO cawo_3137540_15.0 odoo.upgrade.account.saas-13.4.end-09-payment-refactoring: Creating moves for draft statement lines 
2025-10-09 12:25:04,315 26 INFO cawo_3137540_15.0 odoo.upgrade.util.orm: [100.00%] 4/4 env['account.move'].create([:640000]) processed in 1:29:11.870029 (total estimated time: 1:29:11.870029) 

> Warning Please follow and check the relevant boxes for your PR, otherwise the review may take longer.

For a PR that adds a new upgrade script (for the Odoo's master branch or one of the RR versions):
- [ ] I've added the references to the Enterprise and/or Community PRs in the commit message, even if they are already merged.
- [ ] I've added an overall description of the changes made in the Community/Enterprise branches.

For a PR that fixes an issue on an already existing upgrade script:
- [x] I've added a clear description of the issue including information on how to reproduce it.
- [x] I've tested the fix and included references of upgrade requests where this fix will be applicable in the form of upg-<request_number>.
- [ ] I've included references to the OPW, if applicable, in the form of opw-<ticket_number>.
- [ ] I've tested this fix on other DBs, not just the ones with the issue.

For all PRs:
- [x] My commit's title follows the right format.
- [x] My commit's body includes information about the changes.
- [x] I've added odoo/upgrade as a reviewer.
- [x] I've read and understood this list.
- [x] I will ensure all the CI checks are green.

> Note More info can be found in the wiki.