From: Randy MacLeod <randy.macleod@windriver.com>
To: "Martin Hundebøll" <martin@geanix.com>
Cc: "Li, Changqing" <changqing.li@windriver.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: Yocto builds and job server?
Date: Thu, 2 Oct 2025 17:51:30 -0400 [thread overview]
Message-ID: <8daca69a-82ae-45af-8a04-b15ffd4aa2c7@windriver.com> (raw)
In-Reply-To: <3124209f7210c9e39608a9717fa6abc7f1c4bf8b.camel@geanix.com>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On 2025-09-29 8:54 a.m., Martin Hundebøll wrote:
> Hi Randy,
>
> On Tue, 2025-09-23 at 15:43 -0400, Randy MacLeod wrote:
>> Hi Martin,
>>
>> Do you keep your job server patch up to date?
>> If so, can you push it to poky-contrib or share it some other way?
>>
>> Now that we're closer to stabilizing the fall release, I'd like to
>> work on and help get that merged early in the next development cycle.
>>
> Yeah, just today, one of our internal shared builders with 16 cores /
> 32 threads ran with a load of "204,19, 170,18, 106,53", so it
Yikes, are you using BB_PRESSURE_* or limiting builds using
the threads/jobs variables at all?
https://docs.yoctoproject.org/dev-manual/speeding-up-build.html
> definitely makes sense to dig out the jobserver patches.
>
> I will give it a spin in one of the coming weeks. Thanks for reminding
> me!
I'll be waiting with bells on!
../Randy
>
> // Martin
>
>
>>
>> Context for those interested:
>>
>> https://lore.kernel.org/openembedded-core/9844556f-5016-47fa-a3ac-ceaaca1e7d57@windriver.com
>> /
>>
>>
>> ../Randy
>>
>>
>> --
>> # Randy MacLeod
>> # Wind River Linux
>>
--
# Randy MacLeod
# Wind River Linux
[-- Attachment #2: Type: text/html, Size: 2554 bytes --]
next prev parent reply other threads:[~2025-10-02 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 19:43 Yocto builds and job server? Randy MacLeod
2025-09-29 12:54 ` Martin Hundebøll
2025-10-02 21:51 ` Randy MacLeod [this message]
2025-10-03 8:14 ` [yocto] " Antonin Godard
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=8daca69a-82ae-45af-8a04-b15ffd4aa2c7@windriver.com \
--to=randy.macleod@windriver.com \
--cc=changqing.li@windriver.com \
--cc=martin@geanix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox