| Summary: | AUH: Parallelize running bitbake inside AUH script | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Automated Update Handler | Reporter: | Aníbal Limón <anibal.limon> |
| Component: | Automatic Update Handler | Assignee: | Alexander Kanavin <alex.kanavin> |
| Status: | RESOLVED OBSOLETE | QA Contact: | Apoorv <apoorv.sangal> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, jose.perez.carranza, juan.m.cruz.alcaraz, leonardo.sandoval.gonzalez, richard.purdie, sgw |
| Version: | unspecified | ||
| Target Milestone: | 2.6 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 7488 | ||
| Bug Blocks: | |||
|
Description
Aníbal Limón
2015-03-19 22:38:07 UTC
Move to 2.2 due to my current load in QA transition. Moving to 2.4 M3, now focused on oe-selftest threaded runs. 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. |