On 18 Apr 2012, at 21:55, Darren Hart wrote:
> A couple of things to keep in mind here. The minimal build is very
> serialized in comparison to something like a sato build. If you want to
> optimize your build times, look at the bbmatrix* scripts shipped with
> poky to find the sweet spot for yo
On 04/19/2012 12:24 AM, Björn Stenberg wrote:
> Darren Hart wrote:
>> Right, gnuplot likes evenly spaced values of BB and PM. So you could
>> have done: 8,12,16,24,28,32
>
> I did that, and uploaded it to the wiki:
> https://wiki.yoctoproject.org/wiki/Build_Performance#parallelism
>
> Looks
2012/4/19 Richard Purdie :
> On Thu, 2012-04-19 at 18:18 +0530, Joshua Immanuel wrote:
>> Hello,
>>
>> On Fri, 2012-04-13 at 09:45 +0100, Richard Purdie wrote:
>> > There are undoubtedly ways we can improve performance but I think
>> > we've done the low hanging fruit and we need some fresh ideas.
On Thu, 2012-04-19 at 18:18 +0530, Joshua Immanuel wrote:
> Hello,
>
> On Fri, 2012-04-13 at 09:45 +0100, Richard Purdie wrote:
> > There are undoubtedly ways we can improve performance but I think
> > we've done the low hanging fruit and we need some fresh ideas.
>
> Is there a way to integrate
Hello,
On Fri, 2012-04-13 at 09:45 +0100, Richard Purdie wrote:
> There are undoubtedly ways we can improve performance but I think
> we've done the low hanging fruit and we need some fresh ideas.
Is there a way to integrate distcc in yocto so that we could distribute
the build across machines.
-
Op 13 apr. 2012, om 10:45 heeft Richard Purdie het volgende geschreven:
> On Thu, 2012-04-12 at 07:34 -0700, Darren Hart wrote:
>>
>> On 04/12/2012 07:08 AM, Björn Stenberg wrote:
>>> Darren Hart wrote:
/dev/md0/build ext4
noauto,noatime,nodiratime,commit=6000
>>>
>>
Darren Hart wrote:
> Right, gnuplot likes evenly spaced values of BB and PM. So you could
> have done: 8,12,16,24,28,32
I did that, and uploaded it to the wiki:
https://wiki.yoctoproject.org/wiki/Build_Performance#parallelism
Looks like 24/32 is the sweet spot for this system, for this build.
On 04/18/2012 12:41 PM, Chris Tapp wrote:
> On 12 Apr 2012, at 23:56, Darren Hart wrote:
>> Get back to us with times, and we'll build up a wiki page.
>
> Some initial results / comments:
>
> I'm running on:
> - i7 3820 (quad core, hyper-treading, 3.6GHz)
> - 16GB RAM (1600MHz XMP profile)
>
On 18 Apr 2012, at 20:41, Chris Tapp wrote:
> On 12 Apr 2012, at 23:56, Darren Hart wrote:
>> Get back to us with times, and we'll build up a wiki page.
>
>
>
> I also tried rebuilding the kernel:
> bitbake -c clean linux-yocto
> rm -rf the sstate bits for the above
> bitbake linux-yocto
On 12 Apr 2012, at 23:56, Darren Hart wrote:
> Get back to us with times, and we'll build up a wiki page.
Some initial results / comments:
I'm running on:
- i7 3820 (quad core, hyper-treading, 3.6GHz)
- 16GB RAM (1600MHz XMP profile)
- Asus P9X79 Pro motherboard
- Ubuntu 11.10 x86_64 server i
On Fri, Apr 13, 2012 at 07:51:51AM +0200, Martin Jansa wrote:
> On Thu, Apr 12, 2012 at 04:37:00PM -0700, Flanagan, Elizabeth wrote:
> > On Thu, Apr 12, 2012 at 7:12 AM, Darren Hart wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > >
> > >
> > > On 04/12/2012 01:00 AM
On 04/13/2012 01:47 AM, Björn Stenberg wrote:
> Darren Hart wrote:
>> One thing that comes to mind is the parallel settings, BB_NUMBER_THREADS
>> and PARALLEL_MAKE. I noticed a negative impact if I increased these
>> beyond 12 and 14 respectively. I tested this with bb-matrix
>> (scripts/contrib/
Op 13 apr. 2012, om 11:56 heeft Tomas Frydrych het volgende geschreven:
> On 12/04/12 01:30, Darren Hart wrote:
>> Next up is storage.
>
> Indeed. In my experience by far the biggest limiting factor in the
> builds is getting io bound. If you are not running a dedicated build
> machine, it is w
On 12/04/12 01:30, Darren Hart wrote:
> Next up is storage.
Indeed. In my experience by far the biggest limiting factor in the
builds is getting io bound. If you are not running a dedicated build
machine, it is well worth using a dedicated disk for the poky tmp dir;
assuming you have cpu time lef
Darren Hart wrote:
> One thing that comes to mind is the parallel settings, BB_NUMBER_THREADS
> and PARALLEL_MAKE. I noticed a negative impact if I increased these
> beyond 12 and 14 respectively. I tested this with bb-matrix
> (scripts/contrib/bb-perf/bb-matrix.sh). The script is a bit fickle, but
On Thu, 2012-04-12 at 07:34 -0700, Darren Hart wrote:
>
> On 04/12/2012 07:08 AM, Björn Stenberg wrote:
> > Darren Hart wrote:
> >> /dev/md0/build ext4
> >> noauto,noatime,nodiratime,commit=6000
> >
> > A minor detail: 'nodiratime' is a subset of 'noatime', so there is no
> > ne
Dear Darren Hart,
In message <4f87c2d3.8020...@linux.intel.com> you wrote:
>
> > Phenom II X4 965, 4GB RAM, RAID0 (3 SATA2 disks) for WORKDIR, RAID5
> > (the same 3 SATA2 disks) BUILDDIR (raid as mdraid), now I have
> > Bulldozer AMD FX(tm)-8120, 16GB RAM, still the same RAID0 but
> > different m
On Thu, Apr 12, 2012 at 11:08:19PM -0700, Darren Hart wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/12/2012 10:51 PM, Martin Jansa wrote:
>
> > And my system is very slow compared to yours, I've found my
> > measurement of core-image-minimal-with-mtdutils around 95 mins
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/2012 10:51 PM, Martin Jansa wrote:
> And my system is very slow compared to yours, I've found my
> measurement of core-image-minimal-with-mtdutils around 95 mins
> http://patchwork.openembedded.org/patch/17039/ but this was with
> Phenom II
On Thu, Apr 12, 2012 at 04:37:00PM -0700, Flanagan, Elizabeth wrote:
> On Thu, Apr 12, 2012 at 7:12 AM, Darren Hart wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> >
> >
> > On 04/12/2012 01:00 AM, Martin Jansa wrote:
> > > On Thu, Apr 12, 2012 at 01:05:00PM +0530, Joshua Imm
On Thu, Apr 12, 2012 at 7:12 AM, Darren Hart wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 04/12/2012 01:00 AM, Martin Jansa wrote:
> > On Thu, Apr 12, 2012 at 01:05:00PM +0530, Joshua Immanuel wrote:
> >> Darren,
> >>
> >> On Wed, 2012-04-11 at 17:30 -0700, Darren Hart wrot
On 04/12/2012 03:43 PM, Chris Tapp wrote:
> On 12 Apr 2012, at 15:34, Darren Hart wrote:
>>
>>
>> On 04/12/2012 07:08 AM, Björn Stenberg wrote:
>>> Darren Hart wrote:
/dev/md0/build ext4
noauto,noatime,nodiratime,commit=6000
>>>
>>> A minor detail: 'nodiratime' is a su
On 12 Apr 2012, at 15:34, Darren Hart wrote:
>
>
> On 04/12/2012 07:08 AM, Björn Stenberg wrote:
>> Darren Hart wrote:
>>> /dev/md0/build ext4
>>> noauto,noatime,nodiratime,commit=6000
>>
>> A minor detail: 'nodiratime' is a subset of 'noatime', so there is no
>> need to specif
On 04/12/2012 07:08 AM, Björn Stenberg wrote:
> Darren Hart wrote:
>> /dev/md0/build ext4
>> noauto,noatime,nodiratime,commit=6000
>
> A minor detail: 'nodiratime' is a subset of 'noatime', so there is no
> need to specify both.
Excellent, thanks for the tip.
>
>> I run on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/2012 01:00 AM, Martin Jansa wrote:
> On Thu, Apr 12, 2012 at 01:05:00PM +0530, Joshua Immanuel wrote:
>> Darren,
>>
>> On Wed, 2012-04-11 at 17:30 -0700, Darren Hart wrote:
>>> I run on a beast with 12 cores, 48GB of RAM, OS and sources on
Darren Hart wrote:
> /dev/md0/build ext4
> noauto,noatime,nodiratime,commit=6000
A minor detail: 'nodiratime' is a subset of 'noatime', so there is no need to
specify both.
> I run on a beast with 12 cores, 48GB of RAM, OS and sources on a G2
> Intel SSD, with two Seagate Barrac
On Thu, 2012-04-12 at 10:00 +0200, Martin Jansa wrote:
> > On Wed, 2012-04-11 at 17:30 -0700, Darren Hart wrote:
> > > I run on a beast with 12 cores, 48GB of RAM, OS and sources on
> > > a G2 Intel SSD, with two Seagate Barracudas in a RAID0 array for
> > > my /build partition. I run a headless U
On Thu, Apr 12, 2012 at 01:05:00PM +0530, Joshua Immanuel wrote:
> Darren,
>
> On Wed, 2012-04-11 at 17:30 -0700, Darren Hart wrote:
> > I run on a beast with 12 cores, 48GB of RAM, OS and sources on a G2
> > Intel SSD, with two Seagate Barracudas in a RAID0 array for my /build
> > partition. I ru
Darren,
On Wed, 2012-04-11 at 17:30 -0700, Darren Hart wrote:
> I run on a beast with 12 cores, 48GB of RAM, OS and sources on a G2
> Intel SSD, with two Seagate Barracudas in a RAID0 array for my /build
> partition. I run a headless Ubuntu 11.10 (x86_64) installation running
> the 3.0.0-16-server
On 04/11/2012 09:39 PM, Bob Cochran wrote:
> On 04/11/2012 08:30 PM, Darren Hart wrote:
>> SSDs are one way to
>> go, but we've been known to chew through them and they aren't priced as
>> consumables.
>
> Hi Darren,
>
> Could you please elaborate on "been known to chew through them"?
>
> Are
On 04/11/2012 08:30 PM, Darren Hart wrote:
SSDs are one way to
go, but we've been known to chew through them and they aren't priced as
consumables.
Hi Darren,
Could you please elaborate on "been known to chew through them"?
Are you running into an upper limit on write / erase cycles? Are you
Excellent topic for a wiki page.
On Wed, Apr 11, 2012 at 5:30 PM, Darren Hart wrote:
>
>
> On 04/11/2012 01:42 PM, Chris Tapp wrote:
>> Is there a page somewhere that gives a rough idea of how quickly a full
>> build runs on various systems?
>>
>> I need a faster build platform, but want to get
On 04/11/2012 01:42 PM, Chris Tapp wrote:
> Is there a page somewhere that gives a rough idea of how quickly a full build
> runs on various systems?
>
> I need a faster build platform, but want to get a reasonable price /
> performance balance ;-)
>
> I'm looking at something like an i7-2700K
On 04/11/2012 04:42 PM, Chris Tapp wrote:
Is there a page somewhere that gives a rough idea of how quickly a full build
runs on various systems?
I need a faster build platform, but want to get a reasonable price /
performance balance ;-)
I'm looking at something like an i7-2700K but am not ye
> Is there a page somewhere that gives a rough idea of how quickly a full build
> runs on various systems?
I dont think there is a page anywhere.
This is as rough as it can get on the two machine that I have not
including the time it takes to download the source files.
HP 2.8GHz core i-7 dual c
Is there a page somewhere that gives a rough idea of how quickly a full build
runs on various systems?
I need a faster build platform, but want to get a reasonable price /
performance balance ;-)
I'm looking at something like an i7-2700K but am not yet tied...
Chris Tapp
opensou...@keylevel.c
36 matches
Mail list logo
