All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: yocto@yoctoproject.org
Subject: Re: Build time data
Date: Wed, 11 Apr 2012 17:38:00 -0400	[thread overview]
Message-ID: <4F85F9B8.8060902@mindchasers.com> (raw)
In-Reply-To: <1B707EEC-B001-45EA-BC0B-C0FF70BB7152@keylevel.com>

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 yet tied...
>
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>


I haven't seen one, but it would be great to have this on the wiki where 
everyone could post what they're seeing & using.

Maybe the autobuilder has some useful statistics 
(http://autobuilder.yoctoproject.org:8010/)?  Of course, you'll have to 
be careful to determine whether anything else was running at the time of 
the build.

On a related note, I have been wondering whether I would get the bang 
for the buck with an SSD for my build machines.  I would guess that 
building embedded Linux images isn't a typical use pattern for an SSD. I 
wonder if the long write & erase durations for FLASH technology would 
show its ugly face during a poky build.  I would think that the embedded 
micro inside the SSD managing the writes might get taxed to the limit 
trying to slice the data.  I would appreciate anyone's experience with 
SSDs on build machines.


  parent reply	other threads:[~2012-04-11 21:38 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 [this message]
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
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=4F85F9B8.8060902@mindchasers.com \
    --to=yocto@mindchasers.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.