From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Sundeep KOKKONDA <Sundeep.Kokkonda@windriver.com>,
Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org, randy.macleod@windriver.com
Subject: Re: [OE-core] [PATCH] rust: Enable parallel-frontend-threads
Date: Thu, 12 Mar 2026 13:21:28 +0000 [thread overview]
Message-ID: <40e36e02008319799f4d32b9d08df585f4ec70b7.camel@linuxfoundation.org> (raw)
In-Reply-To: <8a0c93d3-d8ce-4ee0-bb08-fbda7e5f1883@windriver.com>
On Thu, 2026-03-12 at 18:41 +0530, Sundeep KOKKONDA wrote:
> >
> > I'd suggest we don't hardcode a number, but rather set to
> > oe.utils.cpu_count()
> > (grep oe-core for examples).
> >
> I choose 8 here as there is no noticeable difference between 8/16.
> Also, the rust blog says
> (https://blog.rust-lang.org/2023/11/09/parallel-rustc/) -
>
> We recommend eight threads because this is the configuration we have
> tested the most and it is known to give good results. Values lower
> than eight will see smaller benefits, but are appropriate if your
> hardware has fewer than eight cores. Values greater than eight will
> give diminishing returns and may even give worse performance.
That sounds like min(oe.utils.parallel_make(), 8) then?
Cheers,
Richard
prev parent reply other threads:[~2026-03-12 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 4:07 [PATCH] rust: Enable parallel-frontend-threads sundeep.kokkonda
2026-03-12 9:02 ` [OE-core] " Alexander Kanavin
2026-03-12 12:13 ` Richard Purdie
2026-03-12 13:11 ` Sundeep KOKKONDA
2026-03-12 13:21 ` Richard Purdie [this message]
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=40e36e02008319799f4d32b9d08df585f4ec70b7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
/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