From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] perl: use parallel build where possible
Date: Sat, 03 Mar 2018 08:53:53 +0000 [thread overview]
Message-ID: <1520067233.3436.34.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180302153220.16494-1-alexander.kanavin@linux.intel.com>
On Fri, 2018-03-02 at 17:32 +0200, Alexander Kanavin wrote:
> While the upstream just runs a number of make tasks hardcoded to a
> single thread
> in succession, we can add '-j n_threads' to a few of them. The
> benefit
> is real: on my machine the do_compile() time goes from 250 seconds to
> about 90.
>
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
> meta/recipes-devtools/perl/perl_5.24.1.bb | 5 +++++
> 1 file changed, 5 insertions(+)
I like the idea of the patch but I think it triggered:
https://autobuilder.yocto.io/builders/nightly-world/builds/806/steps/BuildImages/logs/stdio
Cheers,
Richard
next prev parent reply other threads:[~2018-03-03 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 15:32 [PATCH] perl: use parallel build where possible Alexander Kanavin
2018-03-03 8:53 ` Richard Purdie [this message]
2018-03-05 14:03 ` Alexander Kanavin
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=1520067233.3436.34.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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