From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: docs <docs@lists.yoctoproject.org>
Subject: Fwd: [bitbake-devel] [PATCH] doc/user-manual: Add BB_LOADFACTOR_MAX
Date: Thu, 11 Apr 2024 13:27:00 +0100 [thread overview]
Message-ID: <ff0e2a74b5fa86ebd92c6dff32f4e97d972683d7.camel@linuxfoundation.org> (raw)
In-Reply-To: 17C5395EDB80122A.4467@lists.openembedded.org
[-- Attachment #1: Type: text/plain, Size: 52 bytes --]
Sharing with the docs list too...
Cheers,
Richard
[-- Attachment #2: Forwarded message — [bitbake-devel] [PATCH] doc/user-manual: Add BB_LOADFACTOR_MAX --]
[-- Type: message/rfc822, Size: 12605 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 1421 bytes --]
Document BB_LOADFACTOR_MAX which was recently added.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
.../bitbake-user-manual-ref-variables.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
index d3936935cd..00faeea686 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
@@ -432,6 +432,15 @@ overview of their function and contents.
``ConfigParsed`` event can set the variable to trigger the re-parse.
You must be careful to avoid recursive loops with this functionality.
+ :term:`BB_LOADFACTOR_MAX`
+ Setting this to a value will cause bitbake to check the system load
+ average before executing new tasks. If the load average is above the
+ the number of CPUs multipled by this factor, no new task will be started
+ unless there is no task executing. A value of "1.5" has been found to
+ work reasonably. This is helpful for systems which don't have pressure
+ regulation enabled, which is more granular. Pressure values take
+ precedence over loadfactor.
+
:term:`BB_LOGCONFIG`
Specifies the name of a config file that contains the user logging
configuration. See
--
2.40.1
[-- Attachment #2.1.2: Type: text/plain, Size: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16070): https://lists.openembedded.org/g/bitbake-devel/message/16070
Mute This Topic: https://lists.openembedded.org/mt/105461244/1686473
Group Owner: bitbake-devel+owner@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [richard.purdie@linuxfoundation.org]
-=-=-=-=-=-=-=-=-=-=-=-
parent reply other threads:[~2024-04-11 12:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <17C5395EDB80122A.4467@lists.openembedded.org>]
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=ff0e2a74b5fa86ebd92c6dff32f4e97d972683d7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=docs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).