Re: nodejs do_compile eats all resources

Oliver Westermann <oliver.westermann@...>

Am Dienstag, 27. September 2022 10:50 schrieb Alexander Kanavin <alex.kanavin@...>:

Do keep in mind that PARALLEL_MAKE can and should be set per recipe, so you can make-limit only the worst items.

Yeah, I'm currently using

PARALLEL_MAKE = "-j ${@int(oe.utils.cpu_count() / 4)}"

In a .bbappend to limit it, but keep it dynamic.

One question out of curiosity or lack of understanding:
Bitbake offers BB_NUMBER_THREADS to limit (IMHO) the number of bitbake tasks, eg parallel do_compile() tasks. Each of these however spawn the compiler with several parallel threads oe.utils.cpu_count (PARALLEL_MAKE defaults to cpu_count()). Why isn't it more common that we end up in issues due to cpu_count^2 threads being spawned? Shouldn't (roughly) BB_NUMBER_THREADS * PARALLEL_MAKE fully load the CPU?

Best regards, a curious Olli

Join to automatically receive all group messages.