From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joe Sauer <jsauer@vernier.com>
Cc: poky@o-hand.com
Subject: Re: requesting input on specs for a new Poky build server
Date: Mon, 18 Apr 2011 09:46:36 +0100 [thread overview]
Message-ID: <1303116396.5518.79.camel@rex> (raw)
In-Reply-To: <BANLkTikxXCxeCfqnSC9kKRqVvCgF5=Ju+Q@mail.gmail.com>
Hi Joe,
On Mon, 2011-04-11 at 14:50 -0700, Joe Sauer wrote:
> I have the pleasure of spec'ing out a new server for doing Poky builds
> (we are at Green 3.3.1). As a reference point, my desktop machine is
> a quad-Xeon @ 2.5 GHz with 4GB of RAM and SATA disk. I can do a full
> "clean" build for our LabQuest (armv5te) in 2 hours.
>
> Here are some questions I would like to get feedback on regarding a
> build server:
>
> 1. Would I get better build time going with more procs (8?) or faster
> procs (3+ GHz)?
>
> 2. Are SATA drives OK, or should I go with RAID to get better R/W
> performance?
>
> 3. If I have to choose one or the other, should I go with faster
> procs or faster disk I/O?
Good questions and I'm not sure I have a definitive answer for you. Some
parts of the build are I/O bound, some are CPU bound and I think you
could see benefits by improving both at this point in time. I'd suspect
CPU still wins as the bigger bottleneck though. Disk I/O can partly be
worked around by a little more RAM.
Cheers,
Richard
prev parent reply other threads:[~2011-04-18 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 21:50 requesting input on specs for a new Poky build server Joe Sauer
2011-04-12 0:03 ` Tom Rini
2011-04-20 15:23 ` Darren Hart
2011-04-18 8:46 ` Richard Purdie [this message]
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=1303116396.5518.79.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=jsauer@vernier.com \
--cc=poky@o-hand.com \
/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.