Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] local.conf.sample: Add automatic defaults for BB_NUMBER_THREADS and PARALLEL_MAKE
Date: Wed, 29 Jan 2014 13:46:55 +0100	[thread overview]
Message-ID: <52E8F83F.7090300@dresearch-fe.de> (raw)
In-Reply-To: <3453178.7rjKagprWh@peggleto-mobl5.ger.corp.intel.com>

On 29.01.2014 12:52, Paul Eggleton wrote:
> On Wednesday 29 January 2014 12:47:54 Steffen Sledz wrote:
>> On 29.01.2014 11:59, Richard Purdie wrote:
>>> On Wed, 2014-01-29 at 11:14 +0100, Steffen Sledz wrote:
>>>> On 27.01.2014 15:39, Richard Purdie wrote:
>>>>> Its rather sad that people don't appear to read local.conf and then
>>>>> complain about slow builds when they're just using a single thread.
>>>>> Most systems have more than one core now so we might as well use a more
>>>>> automatic default for these values. This may lead to better experiences
>>>>> for new users.
>>>>>
>>>>> [YOCTO #2528]
>>>>>
>>>>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>>>> ---
>>>>> diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample
>>>>> index 71856b8..36d33e1 100644
>>>>> --- a/meta/conf/local.conf.sample
>>>>> +++ b/meta/conf/local.conf.sample
>>>>> @@ -18,12 +18,18 @@
>>>>>
>>>>>  # option determines how many tasks bitbake should run in parallel:
>>>>>  #
>>>>>  #BB_NUMBER_THREADS ?= "4"
>>>>>
>>>>> +#
>>>>> +# Default to setting automatically based on cpu count
>>>>> +BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
>>>>>
>>>>>  #
>>>>>  # The second option controls how many processes make should run in
>>>>>  parallel when # running compile tasks:
>>>>>  #
>>>>>  #PARALLEL_MAKE ?= "-j 4"
>>>>>  #
>>>>>
>>>>> +# Default to setting automatically based on cpu count
>>>>> +PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
>>>>> +#
>>>>>
>>>>>  # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j
>>>>>  4" would # be appropriate for example.
>>>>
>>>> On our Fedora-18 build host this change leads to the following exception.
>>>> :(> 
>>> Do you have:
>>>
>>> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=721773072da08cf0f5e12
>>> 06961ada3083b6722b4
>> No.
>>
>> But now it becomes really interesting. As mentioned before it works well on
>> our openSUSE-13.1 build host (without this commit)???
> 
> Are you sure you're not overriding BB_NUMBER_THREADS / PARALLEL_MAKE on the 
> machine where it's "working"? You can use bitbake -e | less (variable history) 
> to be sure.

Yes, this was a good hint.

Sorry for disturbance.

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058


  reply	other threads:[~2014-01-29 12:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 14:39 [PATCH] local.conf.sample: Add automatic defaults for BB_NUMBER_THREADS and PARALLEL_MAKE Richard Purdie
2014-01-27 16:45 ` Otavio Salvador
2014-01-27 17:23   ` Stewart, David C
2014-01-27 17:25     ` Burton, Ross
2014-01-28 10:08 ` Koen Kooi
2014-01-28 10:41   ` Richard Purdie
2014-01-29 12:09   ` Ulf Samuelsson
2014-01-29 12:56     ` Richard Purdie
2014-01-29 13:32       ` Ulf Samuelsson
2014-01-29 14:44         ` Ross Burton
2014-02-01  9:21       ` Mike Looijmans
2014-02-03 21:23         ` Ulf Samuelsson
2014-02-03 23:34           ` Richard Purdie
2014-02-04 16:13   ` Enrico Scholz
2014-02-04 16:59     ` Mark Hatle
2014-02-04 18:00       ` Enrico Scholz
2014-01-29 10:14 ` Steffen Sledz
2014-01-29 10:22   ` Paul Eggleton
2014-01-29 11:42     ` Steffen Sledz
2014-01-29 10:59   ` Richard Purdie
2014-01-29 11:47     ` Steffen Sledz
2014-01-29 11:52       ` Paul Eggleton
2014-01-29 12:46         ` Steffen Sledz [this message]
2014-01-29 16:39 ` Laszlo Papp

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=52E8F83F.7090300@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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