All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Recommended Hardware for building
Date: Tue, 07 Oct 2014 19:53:25 -0400	[thread overview]
Message-ID: <20141007235325.GJ25997@denix.org> (raw)
In-Reply-To: <CAJTo0LaHLETQJxzVpm_B9y+GX9RNBiCY1UF7kBhuWBEeMcs+Uw@mail.gmail.com>

On Thu, Oct 02, 2014 at 11:04:43AM +0100, Burton, Ross wrote:
> On 2 October 2014 10:36, Oliver Novakovic <Oliver.Novakovic@alpine.de> wrote:
> > Can anyone recommend a reasonable performant hardware setup to use ?
> >
> > What should be considered ? Are there any pitfalls ? What about bottlenecks
> > in the build system ?
> >
> > Specifically:
> >
> > How many cores are recommended ? And how much cache is necessary ?
> > How much of the main memory does Yocto really use ? Is 32 GB sufficient or
> > should I go for 64 ?
> >
> > Does it make sense to use two SSDs as Raid0  to get builds faster ?
> 
> As much of everything as you can afford.  :)  The build isn't heavy in
> any particular metric, so don't sacrifice RAM for SSDs for example.
> 
> RAID 0 over SSD would be nice and fast, but I prefer having a good
> amount of RAM and a tuned ext4 (no journal, long commit delay) so data
> doesn't actually hit the disk as frequently. Keeping the actual build
> directories on a separate disk is good for performance and not causing
> data loss when you lose a disk.
> 
> There are people that have 64GB in machines and then set TMPDIR to a
> tmpfs.  Surprisingly this isn't that much faster (5% or so), but it's
> a lot easier on the hardware and power consumption.

That's how I roll - after I lost few SSD drives by constantly building and 
rebuilding stuff, I ended up shoving 64GB of RAM into my gear and building 
into RAM-based tmpfs. Of course, there are size limits to what can be built in 
one go, but there are workarounds and ways to serialize builds...

-- 
Denys


  parent reply	other threads:[~2014-10-08  0:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02  9:36 Recommended Hardware for building Oliver Novakovic
2014-10-02 10:04 ` Burton, Ross
2014-10-02 16:51   ` Chris Tapp
2014-10-02 19:09     ` Martin Jansa
2014-10-03 12:47       ` Bryan Evenson
2014-10-07 23:53   ` Denys Dmytriyenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-06  8:47 Oliver Novakovic

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=20141007235325.GJ25997@denix.org \
    --to=denis@denix.org \
    --cc=ross.burton@intel.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.