From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: yocto@lists.yoctoproject.org, alex.kanavin@gmail.com
Cc: raj.khem@gmail.com, steven.monsees@baesystems.us
Subject: Re: [yocto] Parallel builds under yocto
Date: Thu, 15 Aug 2024 09:16:56 +0300 [thread overview]
Message-ID: <Zr2dWMCbY4deHsfI@nuoska> (raw)
In-Reply-To: <CANNYZj8OMoGL5h9nGfht0w=KizX-FZuY6kFhGFb8Qv1dFAwM4w@mail.gmail.com>
Hi,
On Wed, Aug 14, 2024 at 09:36:05PM +0200, Alexander Kanavin via lists.yoctoproject.org wrote:
> Also there are sensible defaults for both, which use autodetection for
> how many cores a system cpu has. Generally you need to start tweaking
> these settings only when defaults aren't working well (e.g. if the
> system doesn't have enough RAM to support that many instances of gcc).
And when RAM becomes the limiting factor, one rule of thumb is to follow
CPU thread count until each thread has at least 2 Gb of physical RAM available.
On complex builds with lots of C++ (qt and friends) this seems to be a good
upper limit.
Less than 2 Gb per CPU thread results in OOM killer actions during building/linking
steps.
If one tracks builds CPU, memory, local disk and networking load with Performance Co-Pilot
or similar tools, it can be deduced that builds are CPU bound only some of the time
and a lot of time they are actually memory and local disk IO bound. Thus reducing
disk writes helps.
http://events17.linuxfoundation.org/sites/events/files/slides/elce-2016-mario-goulart-mikko-rapeli.pdf
and slides 49 and 50, for one setup.
Cheers,
-Mikko
next prev parent reply other threads:[~2024-08-15 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MADEUP.17EBAE4E6A437742.17352@lists.yoctoproject.org>
2024-08-14 19:24 ` [yocto] Parallel builds under yocto Khem Raj
2024-08-14 19:36 ` Alexander Kanavin
2024-08-15 6:16 ` Mikko Rapeli [this message]
2024-08-15 10:18 ` Monsees, Steven C (US)
[not found] ` <MADEUP.17EBDF92AD5AE264.10875@lists.yoctoproject.org>
2024-08-15 10:24 ` Alexander Kanavin
2024-08-15 10:37 ` Monsees, Steven C (US)
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=Zr2dWMCbY4deHsfI@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=alex.kanavin@gmail.com \
--cc=raj.khem@gmail.com \
--cc=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.