From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alex.kanavin@gmail.com, sundeep.kokkonda@windriver.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 12:13:40 +0000 [thread overview]
Message-ID: <50b8d821e3bd8e8ff7b3b2650c219415967e5108.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_D=9z-ZjjP2D+RqVUAF2Kq0a8cd62dqE5doHzSYdPQnA@mail.gmail.com>
On Thu, 2026-03-12 at 10:02 +0100, Alexander Kanavin via lists.openembedded.org wrote:
> On Thu, 12 Mar 2026 at 05:07, Sundeep KOKKONDA via
> lists.openembedded.org
> <sundeep.kokkonda=windriver.com@lists.openembedded.org> wrote:
> > Test Results:
> > A few tests ran by, with and without enabling this option.
> > - Avg. default build time (w/o this option) - 56m 50.104s
> > - Avg. build time with this option - 49m 17.224s
> > - Performance Difference - 7m 32.880s faster builds (≈ 13.3%)
> >
> > Tests were performed by setting thread count as 8 & 16 but no much difference is seen.
> > So, the parallel-frontend-threads = 8 is set.
>
> It would really help to provide specifics. What tests did you run, and
> how were the numbers obtained? How can these tests be reproduced? What
> CPU was used and how many cores it had?
>
> > + config.set("rust", "parallel-frontend-threads", "8")
>
> I'd suggest we don't hardcode a number, but rather set to oe.utils.cpu_count()
> (grep oe-core for examples).
oe.utils.parallel_make() might make more sense here?
Cheers,
Richard
next prev parent reply other threads:[~2026-03-12 12:13 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 [this message]
2026-03-12 13:11 ` Sundeep KOKKONDA
2026-03-12 13:21 ` Richard Purdie
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=50b8d821e3bd8e8ff7b3b2650c219415967e5108.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--cc=sundeep.kokkonda@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