Re: [yocto-patches] [auh][PATCH 2/3] modules/steps.py: refactor compile() to use parallel per-machine builds

On Fri, 2026-04-24 at 16:04 +0200, Alexander Kanavin via lists.yoctoproject.org wrote:
> I understand the idea, but unfortunately I do not think we can put
> this (and the following patch) on the Yocto autobuilder. The
> expectation for the builder jobs is that they are expected to run
> only
> one Yocto build at a time, and the autobuilder will:
> 
> - configure each builder to use carefully adjusted limited resources
> for that one build (via the fragment in oe-core)
> - start several builders on each worker machine to parallelize large
> builds (e.g. a-full), but no more than a certain upper limit, and
> queue them if the limit is reached on all workers
> 
> This patch breaks that expectation, as auh build is not using an
> exclusive worker for itself, and shares workers with other builds.
> 
> It also isn't clear how this patch was tested and benchmarked. Did
> you
> run a substantial upgrade job with it? Did you see a significant
> speedup?

Whilst we do need to be mindful of this, I suspect there is some room
to parallelise a bit. How much parallelism is this expected to have?
Some existing jobs like oe-selftest do run a lot in parallel already so
this could be not that much different to that...

Cheers,

Richard