From: Darren Hart <dvhart@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: yocto@yoctoproject.org
Subject: Re: what's the proper value for BB_NUMBER_THREADS?
Date: Thu, 03 Nov 2011 10:32:52 -0700 [thread overview]
Message-ID: <4EB2D044.7050207@linux.intel.com> (raw)
In-Reply-To: <4EAEDD3A.9070601@mlbassoc.com>
On 10/31/2011 10:39 AM, Gary Thomas wrote:
> On 2011-10-31 11:25, Robert P. J. Day wrote:
>> On Mon, 31 Oct 2011, Mark Hatle wrote:
>>
>>> On 10/30/11 11:15 AM, Robert P. J. Day wrote:
>>>> On Sun, 30 Oct 2011, Christian Gagneraud wrote:
>>>>
>>>>> On 30/10/11 15:32, Robert P. J. Day wrote:
>>>>>>
>>>>>> all the docs recommend twice the number of cores (AFAICT), yet the
>>>>>> template local.conf file suggests that, for a quad core, the value of
>>>>>> 4 would be appropriate. shouldn't that say 8? same with
>>>>>> PARALLEL_MAKE?
>>>>>
>>>>> Hi Robert,
>>>>>
>>>>> The Poky ref manual says (rule of thumb) x2 for BB_NUMBER_THREADS,
>>>>> and x1.5 for PARALLEL_MAKE.
>>>>
>>>> if that's the case, anyone object to my submitting a patch to
>>>> update local.conf.sample appropriately?
>>>>
>>>> rday
>>>>
>>>
>>> I agree the manual and local.conf files should match. The issue
>>> seems to be that the perfect values are subjective. Things like
>>> memory, disk speed, chipset latency, and of course processor
>>> speed/cores all affect the optimal setting. But we do need a
>>> consistent rule of thumb.. I myself usually use x2 for both THREADS
>>> and MAKE.
>>
>> that's what i would normally use, assuming that having an overly
>> high value for either of those settings can't possibly hurt. if
>> that's the consensus, i can adjust the references to say 2x everywhere
>> that i know of. just let me know.
>
> Look back in the archives - I think it was Richard that did a fairly
> extensive study of this and he (whoever it was) found that there were
> saturation points and trying to get beyond them had a negative impact.
2x on each works well up to about 12 in my experience. Richard has found
benefits using 24 on a similar system with more memory. However, if you
aren't building on a monster machine, then 2x serves as a reasonable
rule of thumb.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-11-03 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 15:32 what's the proper value for BB_NUMBER_THREADS? Robert P. J. Day
2011-10-30 16:03 ` Christian Gagneraud
2011-10-30 16:15 ` Robert P. J. Day
2011-10-31 17:15 ` Mark Hatle
2011-10-31 17:25 ` Robert P. J. Day
2011-10-31 17:39 ` Gary Thomas
2011-11-03 17:32 ` Darren Hart [this message]
2011-11-03 17:41 ` Robert P. J. Day
2011-11-15 23:08 ` Rifenbark, Scott M
2011-11-15 23:51 ` Darren Hart
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=4EB2D044.7050207@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 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.