Mark Hatle writes:
>>> I've noticed that after 4 threads IO becomes a big bottleneck when
>>> you have things like webkit, qt, asio etc in the buildqueue. Combine
>>> that with issues like every make -j thread taking >2GB ram with asio
>>> and webkit this default seems a bit high. I'd use 0.5*num
On 2/4/14, 10:13 AM, Enrico Scholz wrote:
Koen Kooi
writes:
+# Default to setting automatically based on cpu count
+BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
I've noticed that after 4 threads IO becomes a big bottleneck when you
have things like webkit, qt, asio etc in the buildqueue.
Koen Kooi
writes:
>> +# Default to setting automatically based on cpu count
>> +BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
>
> I've noticed that after 4 threads IO becomes a big bottleneck when you
> have things like webkit, qt, asio etc in the buildqueue. Combine that
> with issues like eve
On Mon, 2014-02-03 at 22:23 +0100, Ulf Samuelsson wrote:
> 1 feb 2014 kl. 10:21 skrev Mike Looijmans :
>
> > On 01/29/2014 01:56 PM, Richard Purdie wrote:
> >> On Wed, 2014-01-29 at 13:09 +0100, Ulf Samuelsson wrote:
> If bitbakes can track the loading of the CPU, then maybe some parts
> in the la
1 feb 2014 kl. 10:21 skrev Mike Looijmans :
> On 01/29/2014 01:56 PM, Richard Purdie wrote:
>> On Wed, 2014-01-29 at 13:09 +0100, Ulf Samuelsson wrote:
>>> We discussed this 2.3 months ago.
>>> Did some studies on my dual hex-core machine (24 H/W treads) while
>>> building a cloud9-gnome-image d
On 01/29/2014 01:56 PM, Richard Purdie wrote:
On Wed, 2014-01-29 at 13:09 +0100, Ulf Samuelsson wrote:
We discussed this 2.3 months ago.
Did some studies on my dual hex-core machine (24 H/W treads) while
building a cloud9-gnome-image derivative.
This did about 7500 tasks.
Enabled the CPU superv
Thank you for this contribution.
As a side note, please consider the documentation bits in the future
as well. :-) I have just opened a separate ticket for that here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5770
On Mon, Jan 27, 2014 at 2:39 PM, Richard Purdie
wrote:
> Its rather sad t
webkit, node are also not running in parallell in later part of the build
WebKit does parallel builds internally so what you’re seeing here is everything
that doesn’t depend on webkit has finished, so the remaining tasks are blocking
on the webkit build.
Ross
--
Ross Burton
Open Source Techno
2014-01-29 13:56, Richard Purdie skrev:
On Wed, 2014-01-29 at 13:09 +0100, Ulf Samuelsson wrote:
We discussed this 2.3 months ago.
Did some studies on my dual hex-core machine (24 H/W treads) while
building a cloud9-gnome-image derivative.
This did about 7500 tasks.
Enabled the CPU supervisors
On Wed, 2014-01-29 at 13:09 +0100, Ulf Samuelsson wrote:
> We discussed this 2.3 months ago.
> Did some studies on my dual hex-core machine (24 H/W treads) while
> building a cloud9-gnome-image derivative.
> This did about 7500 tasks.
>
> Enabled the CPU supervisors in the panel.
>
> Everything
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 app
2014-01-28 11:08, Koen Kooi skrev:
Op 27 jan. 2014, om 15:39 heeft Richard Purdie
het volgende geschreven:
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 mig
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
> >>> complai
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 sys
On 29.01.2014 11:22, Paul Eggleton wrote:
> On Wednesday 29 January 2014 11:14:47 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
>
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 mig
On Wednesday 29 January 2014 11:14:47 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
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
On Tue, 2014-01-28 at 11:08 +0100, Koen Kooi wrote:
> Op 27 jan. 2014, om 15:39 heeft Richard Purdie
> het volgende geschreven:
>
> > 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
> >
Op 27 jan. 2014, om 15:39 heeft Richard Purdie
het volgende geschreven:
> 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
On 1/27/14, 8:45 AM, "Otavio Salvador" wrote:
>On Mon, Jan 27, 2014 at 12:39 PM, 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
On 27 January 2014 17:23, Stewart, David C wrote:
> Nice! Now if we could just convince people to configure their VM guests
> with enough cpus -
Now if only we could make bitbake error out when it's running inside a VM. ;)
Ross
___
Openembedded-core ma
On Mon, Jan 27, 2014 at 12:39 PM, 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 thes
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.
[YO
24 matches
Mail list logo
