Please read the original rationale for picking 64, and provide benchmarks that actually show better completion times with the new setting.
Alex On Wed 27. Nov 2024 at 17.33, Jörg Sommer via lists.openembedded.org <[email protected]> wrote: > From: Jörg Sommer <[email protected]> > > We have a system with 96 CPUs and 128 are not uncommon. The border of 64 > limits the number of parallel tasks make or ninja spawns, because the value > goes into `PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"`. If only a > single > recipe gets build (e.g. rust, due to dependencies) this leaves one third of > our CPUs idle. > > Signed-off-by: Jörg Sommer <[email protected]> > --- > meta/lib/oe/utils.py | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta/lib/oe/utils.py b/meta/lib/oe/utils.py > index c9c7a47041..354237b643 100644 > --- a/meta/lib/oe/utils.py > +++ b/meta/lib/oe/utils.py > @@ -251,7 +251,7 @@ def trim_version(version, num_parts=2): > trimmed = ".".join(parts[:num_parts]) > return trimmed > > -def cpu_count(at_least=1, at_most=64): > +def cpu_count(at_least=1, at_most=192): > cpus = len(os.sched_getaffinity(0)) > return max(min(cpus, at_most), at_least) > > -- > 2.45.2 > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#207937): https://lists.openembedded.org/g/openembedded-core/message/207937 Mute This Topic: https://lists.openembedded.org/mt/109808873/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
