From: nick <xerofoify@gmail.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Time To Build Yocto
Date: Wed, 22 Oct 2014 18:25:08 -0400 [thread overview]
Message-ID: <54482EC4.6090901@gmail.com> (raw)
In-Reply-To: <6C4C72C1-9016-4C6B-80D5-16572BE7A9ED@keylevel.com>
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!
>
next prev parent reply other threads:[~2014-10-22 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 20:44 Time To Build Yocto nick
2014-10-22 19:59 ` Chris Tapp
2014-10-22 22:25 ` nick [this message]
2014-10-22 20:07 ` Robert P. J. Day
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=54482EC4.6090901@gmail.com \
--to=xerofoify@gmail.com \
--cc=opensource@keylevel.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.