On 27 Nov 2024, at 16:33, Jörg Sommer via lists.openembedded.org
<joerg.sommer=navimatix...@lists.openembedded.org> wrote:
>
> From: Jörg Sommer <joerg.som...@navimatix.de>
>
> 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.
192 seems like it was arbitrarily chosen as “more than your current system”: if
we’re doing that then we should just remove the maximum cap by reverting the
commit that added it in the first place.
The point of the default is to be reasonable, and in my benchmarking on a
system with 128 cores going beyond 64 only gives you more chance of OOMs, I/O
contention, and other users of the presumably shared machine being angry.
If you have a powerful server that only does a single build then you’re welcome
to set PARALLEL_MAKE = “-j128” in your build environment to take full advantage
of it.
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#207990):
https://lists.openembedded.org/g/openembedded-core/message/207990
Mute This Topic: https://lists.openembedded.org/mt/109808873/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
