Bug 7494 - AUH: Parallelize running bitbake inside AUH script
Summary: AUH: Parallelize running bitbake inside AUH script
Status: RESOLVED OBSOLETE
Alias: None
Product: Automated Update Handler
Classification: Yocto Project Subprojects
Component: Automatic Update Handler (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.6
Assignee: Alexander Kanavin
QA Contact: Apoorv
URL:
Whiteboard:
Depends on: 7488
Blocks:
  Show dependency tree
 
Reported: 2015-03-19 22:38 UTC by Aníbal Limón
Modified: 2018-05-07 04:31 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aníbal Limón 2015-03-19 22:38:07 UTC
Make a mechanism to spawn multiple bitbake environments to take advantage of SMP machines for handle multiple large builds.
Comment 1 Aníbal Limón 2016-02-19 22:45:52 UTC
Move to 2.2 due to my current load in QA transition.
Comment 2 Aníbal Limón 2017-06-28 16:42:55 UTC
Moving to 2.4 M3, now focused on oe-selftest threaded runs.
Comment 3 Alexander Kanavin 2018-04-24 09:15:24 UTC
I'm not entirely sure that's useful? Bitbake itself is heavily parallelized, and caches everything. From my observations of AUH it is already largely I/O bound, and running multiple bitbakes (e.g. to build an updated recipe for several architectures at the same time) would only saturate the disk, and risk going into swap thrashing (with building multiple webkits at the same time, for instance, that's bound to happen). It also has to operate over a single git tree, and so certain things (e.g. running devtool over a set of recipes and then attempting to build every item in the set) have to be done iteratively.