From: Ulf Samuelsson <openembedded-core@emagii.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Improving Build Speed
Date: Thu, 21 Nov 2013 09:04:40 +0100 [thread overview]
Message-ID: <528DBE98.3080309@emagii.com> (raw)
In-Reply-To: <1384982956.16887.94.camel@ted>
>> Why restrict PARALLEL_MAKE to anything less than the number of H/W
>> threads in the machine?
>>
>> Came up with a construct PARALLEL_HIGH which is defined alongside
>> PARALLEL_MAKE in conf/local.conf
>>
>> PARALLEL_MAKE = "-j8"
>> PARALLEL_HIGH = "-j24"
>>
>> In the appropriate recipes, which seems to be processed by bitbake
>> in solitude I do:
>>
>> PARALLEL_HIGH ?= "${PARALLEL_MAKE}"
>> PARALLEL_MAKE = "${PARALLEL_HIGH}"
>>
>> This means that they will try to use each H/W thread.
> Please benchmark the difference. I suspect we can just set the high
> number of make for everything. Note that few makefiles are well enough
> written to benefit from high levels of make (webkit being an notable
> exception).
>
It looks like it is shaving off ~2 minutes from a build which normally
takes ~84 minutes.
First build
PARALLEL_MAKE = "-j12"
PARALLEL_HIGH = "-j24"
BB_NUMBER_THREADS = "24"
real 83m24.093s
Second build
PARALLEL_MAKE = "-j12"
PARALLEL_HIGH = "-j12"
BB_NUMBER_THREADS = "24"
real 85m12.007s
BR
Ulf
> Cheers, Richard _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Best Regards
Ulf Samuelsson
eMagii
next prev parent reply other threads:[~2013-11-21 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 21:05 Improving Build Speed Ulf Samuelsson
2013-11-20 21:29 ` Richard Purdie
2013-11-20 22:43 ` Ulf Samuelsson
2013-11-21 0:19 ` Martin Jansa
2013-11-21 7:15 ` Ulf Samuelsson
2013-11-21 12:53 ` Martin Jansa
2013-11-23 18:39 ` Nicolas Dechesne
2013-11-21 0:10 ` Martin Jansa
2013-11-21 8:04 ` Ulf Samuelsson [this message]
2013-11-21 13:53 ` Richard Purdie
2013-11-23 15:06 ` Ulf Samuelsson
2013-11-21 10:05 ` Burton, Ross
2013-11-21 11:51 ` Enrico Scholz
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=528DBE98.3080309@emagii.com \
--to=openembedded-core@emagii.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ulf@emagii.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.