All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Monsees, Steven C (US)" <steven.monsees@baesystems.us>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Parallel builds under yocto
Date: Wed, 14 Aug 2024 19:14:22 +0000	[thread overview]
Message-ID: <20240814191543.506DEC52D7F@smtp.lore.kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

Hello:
I am looking for some clarity with regards too parallel builds under Yocto...
I think I had a false assumption on setting PARALEL_MAKE...
To increase thread usage: You add following to your local.conf inside the build/conf directory. Replace x and y with your wanted configuration.
PARALLEL_MAKE = "-j x"

BB_NUMBER_THREADS = "y"

Is the following true ?

PARALLEL_MAKE defines how many threads should be used/dedicated when using make -j command during do_compile.

BB_NUMBER_THREADS defines number of threads dedicated for bitbake.

I set up like so:

There are 12 cores my board

Yocto supporters say threads should be 2 times the number of cores, but don't go above 20..., or just the number cores, also under 20... depending on what you read.

They also say, increasing PARALLEL_MAKE to higher values, increases your chance for a race condition.

Is the following true ?

PARALLEL_MAKE = "-j x"  # For do_compile

BB_NUMBER_THREADS = "y"  # For bitbake

PARALLEL_MAKEINST = "-j x"  # For do_install

If so, does this mean for 12 cores:

BB_NUMBER_THREADS="8", will this dedicate 8 cores just for bitbake to use ?

And does this dedicate the remaining 4 for do_compile and do_install ?

PARALLEL_MAKE="-j 2"
PARALLEL_MAKEINST="-j 2"

Thank you...

Steve


[-- Attachment #2: Type: text/html, Size: 9967 bytes --]

                 reply	other threads:[~2024-08-14 19:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240814191543.506DEC52D7F@smtp.lore.kernel.org \
    --to=steven.monsees@baesystems.us \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.