Time To Build Yocto

Time To Build Yocto

[nick]

I am wondering from your experience how long is the largest build you have ever seen and what was it building. I am 
considering a high powered build system for Yocto and want to known about build times in order to help me with
purchasing decisions.
Cheers Nick 

Re: Time To Build Yocto

[Chris Tapp]

On 20 Oct 2014, at 21:44, nick <xerofoify@gmail.com> wrote:

> I am wondering from your experience how long is the largest build you have ever seen and what was it building. I am 
> considering a high powered build system for Yocto and want to known about build times in order to help me with
> purchasing decisions.

There was a recent thread discussing this - have a look at https://lists.yoctoproject.org/pipermail/yocto/2014-October/021808.html

You need to start by working out what you'll be spending most of your time doing - full image builds, incremental images, single recipes, etc.

My build system has an i7-3820 overclocked to 4.6 GHz with 16 GB RAM and SSDs. It takes about an hour to build an X11 image from scratch (no shared state, source already downloaded). I could reduce the build time to about 25 minutes by upgrading to a new CPU (12 core, 24 threads) for $2700 - once you have your use-case you can do the math to work out what the payback time will be ;-)

--

Chris Tapp
opensource@keylevel.com
www.keylevel.com

----
You can tell you're getting older when your car insurance gets real cheap!

Re: Time To Build Yocto

[Robert P. J. Day]

On Mon, 20 Oct 2014, nick wrote:

> I am wondering from your experience how long is the largest build
> you have ever seen and what was it building. I am considering a high
> powered build system for Yocto and want to known about build times
> in order to help me with purchasing decisions.

dear yocto mailing list:

  at the risk of sounding heartless, please don't feed the troll. nick
krause is notorious from the kernel and kernel newbie mailing lists as
someone who, desperate to get his name into the git log as a kernel
developer, has pissed off pretty much *everyone* by submitting
badly-formed, ill-considered patches against numerous subsystems, to
the point where he was finally *banned* from LKML. that didn't slow
him down, as he simply joined the kernel newbies ML and did exactly
the same thing there.

  this is nick:

http://www.themukt.com/2014/08/04/someone-trolling-linux-kernel-mailing-lists-really-hard/

it remains to be seen if nick has changed his ways at all -- i am
simply posting this as a public service announcement so you know what
you might be getting into.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: Time To Build Yocto

[nick]

Thanks Chris,
I was wondering if a i7 was worth it seems it is and yes for the matter, I did have issues with the kernel
community and trying to work then out.
Nick

On 14-10-22 03:59 PM, Chris Tapp wrote:
> 
> On 20 Oct 2014, at 21:44, nick <xerofoify@gmail.com> wrote:
> 
>> I am wondering from your experience how long is the largest build you have ever seen and what was it building. I am 
>> considering a high powered build system for Yocto and want to known about build times in order to help me with
>> purchasing decisions.
> 
> There was a recent thread discussing this - have a look at https://lists.yoctoproject.org/pipermail/yocto/2014-October/021808.html
> 
> You need to start by working out what you'll be spending most of your time doing - full image builds, incremental images, single recipes, etc.
> 
> My build system has an i7-3820 overclocked to 4.6 GHz with 16 GB RAM and SSDs. It takes about an hour to build an X11 image from scratch (no shared state, source already downloaded). I could reduce the build time to about 25 minutes by upgrading to a new CPU (12 core, 24 threads) for $2700 - once you have your use-case you can do the math to work out what the payback time will be ;-)
> 
> --
> 
> Chris Tapp
> opensource@keylevel.com
> www.keylevel.com
> 
> ----
> You can tell you're getting older when your car insurance gets real cheap!
>