All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: Build time data
Date: Fri, 13 Apr 2012 10:56:47 +0100	[thread overview]
Message-ID: <4F87F85F.8060108@r-finger.com> (raw)
In-Reply-To: <4F862237.50200@linux.intel.com>

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 left, this leaves the machine completely
usable for other things.


> Now RAM, you will want about 2 GB of RAM per core, with a minimum of 4GB.

My experience does not bear this out at all; building Yocto on a 6 core
hyper threaded desktop machine I have never ever seen the system memory
use to get significantly over a 2GB mark (out of 8GB available), doing
Yocto build using 10 cores/threads.


On a custom desktop machine with i7-x990 3.47GHz, 8GB ram, quiet
conventional hard disks, letting poky use 10 cores/threads (so I can get
my work done while it does its own thing in the background), a fresh
build of core-image-minimal for beagleboard, with debug & profile tools
and test apps, takes 77 minutes.

Obviously, not anywhere near as fast as the Intel OTC Xenon beast, but
much cheaper HW, and for my purposes the build speed is well in a region
where it is no longer a productivity issue.

Tomas


  parent reply	other threads:[~2012-04-13  9:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 20:42 Build time data Chris Tapp
2012-04-11 21:19 ` Autif Khan
2012-04-11 21:38 ` Bob Cochran
2012-04-12  0:30 ` Darren Hart
2012-04-12  0:43   ` Osier-mixon, Jeffrey
2012-04-12  4:39   ` Bob Cochran
2012-04-12  7:10     ` Darren Hart
2012-04-12  7:35   ` Joshua Immanuel
2012-04-12  8:00     ` Martin Jansa
2012-04-12  9:36       ` Joshua Immanuel
2012-04-12 14:12       ` Darren Hart
2012-04-12 23:37         ` Flanagan, Elizabeth
2012-04-13  5:51           ` Martin Jansa
2012-04-13  6:08             ` Darren Hart
2012-04-13  6:38               ` Martin Jansa
2012-04-13  7:24               ` Wolfgang Denk
2012-04-17 15:29             ` Martin Jansa
2012-04-12 14:08   ` Björn Stenberg
2012-04-12 14:34     ` Darren Hart
2012-04-12 22:43       ` Chris Tapp
2012-04-12 22:56         ` Darren Hart
2012-04-18 19:41           ` Chris Tapp
2012-04-18 20:27             ` Chris Tapp
2012-04-18 20:55             ` Darren Hart
2012-04-19 22:39               ` Chris Tapp
2012-04-13  8:45       ` Richard Purdie
2012-04-19 10:00         ` Koen Kooi
2012-04-19 12:48         ` Joshua Immanuel
2012-04-19 12:52           ` Richard Purdie
2012-04-19 13:47             ` Samuel Stirtzel
2012-04-13  8:47       ` Björn Stenberg
2012-04-13 14:41         ` Darren Hart
2012-04-19  7:24           ` Björn Stenberg
2012-04-19 14:11             ` Darren Hart
2012-04-13  9:56   ` Tomas Frydrych [this message]
2012-04-13 10:23     ` Koen Kooi

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=4F87F85F.8060108@r-finger.com \
    --to=tf+lists.yocto@r-finger.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.