threads set in local.conf

threads set in local.conf

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

Hello all,
Is this loading what others on a similar system are experiencing (see
below)?

I first was setting my threads to 6 on a AMD 6 core system.
In the mega-manual i found
5.4. Configuring the local.conf File

Briefly, set BB_NUMBER_THREADS and PARALLEL_MAKE to twice your host
processor's number of cores.

I am creating an image with 8017 tasks for the beagleboard.
I set threads to 12 and now the build is proceeding much more rapid than
when threads were set to 6.  In 30 minutes the build has completed 2435
tasks or about 25%.
I am seeing a fairly high load 35. 30. 24 and the fan is been at high speed
since the build  started.  The system has 8G of memory and now it is using
and it was using about  13800 of swap space.

Any and all help will be appreciated.
Thanks

[-- Attachment #2: Type: text/html, Size: 1102 bytes --]

Re: threads set in local.conf

[Philip Balister]

On 10/19/2013 08:59 AM, Edward Vidal wrote:
> Hello all,
> Is this loading what others on a similar system are experiencing (see
> below)?
> 
> I first was setting my threads to 6 on a AMD 6 core system.
> In the mega-manual i found
> 5.4. Configuring the local.conf File
> 
> Briefly, set BB_NUMBER_THREADS and PARALLEL_MAKE to twice your host
> processor's number of cores.
> 
> I am creating an image with 8017 tasks for the beagleboard.
> I set threads to 12 and now the build is proceeding much more rapid than
> when threads were set to 6.  In 30 minutes the build has completed 2435
> tasks or about 25%.
> I am seeing a fairly high load 35. 30. 24 and the fan is been at high speed
> since the build  started.  The system has 8G of memory and now it is using
> and it was using about  13800 of swap space.
> 
> Any and all help will be appreciated.

I'm not sure what problem you are trying to solve here.

I'd suggest adding more RAM though, that will ease the disk usage.

Philip


> Thanks
> 
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 

Re: threads set in local.conf

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]

Hello All,
As Philip suggested adding more RAM helps
The system model name: AMD Phenom(tm) II X6 1090T Processor w/16GB of RAM.
In 1 hour it ran 4391 of 8016 tasks or 54% This was a
core-image-sato-sdk-ex (my receipe) with gnuplot, gsl, boost,
qt-mobility-x11, java, and gnuradio.The full build  was taking close to 4
hours with 6 threads and 8GB of RAM.
Regards


On Sun, Oct 20, 2013 at 7:39 AM, Philip Balister <philip@balister.org>wrote:

> On 10/19/2013 08:59 AM, Edward Vidal wrote:
> > Hello all,
> > Is this loading what others on a similar system are experiencing (see
> > below)?
> >
> > I first was setting my threads to 6 on a AMD 6 core system.
> > In the mega-manual i found
> > 5.4. Configuring the local.conf File
> >
> > Briefly, set BB_NUMBER_THREADS and PARALLEL_MAKE to twice your host
> > processor's number of cores.
> >
> > I am creating an image with 8017 tasks for the beagleboard.
> > I set threads to 12 and now the build is proceeding much more rapid than
> > when threads were set to 6.  In 30 minutes the build has completed 2435
> > tasks or about 25%.
> > I am seeing a fairly high load 35. 30. 24 and the fan is been at high
> speed
> > since the build  started.  The system has 8G of memory and now it is
> using
> > and it was using about  13800 of swap space.
> >
> > Any and all help will be appreciated.
>
> I'm not sure what problem you are trying to solve here.
>
> I'd suggest adding more RAM though, that will ease the disk usage.
>
> Philip
>
>
> > Thanks
> >
> >
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>

[-- Attachment #2: Type: text/html, Size: 2412 bytes --]