public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Friedt <chrisfriedt@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] personal compile-farm ?
Date: Sat, 5 Sep 2009 14:19:47 +0200	[thread overview]
Message-ID: <3ea34a000909050519q443d40a8m6db896b5544077e2@mail.gmail.com> (raw)
In-Reply-To: <4AA2465B.80805@hiramoto.org>

Hi Karl,

On Sat, Sep 5, 2009 at 1:07 PM, Karl Hiramoto<karl@hiramoto.org> wrote:
>> For those who have a multi-core compile-farm at home, is there a
>> largely noticeable difference in speed?

Sorry, that should read 'difference in speed for builds'.

> I don't have an atom myself but from looking at the specs, for the same
> amount of money, i'd think you'd be better of with a single machine with
> lots of RAM and 4 to 8 cores with lots of cache for compiling.

Thanks for your reply.

I'm primarily interested in something that uses a smaller form-factor
for power, noise pollution, and space reasons, but 4 to 8 cores
probably doesn't fit in that class.

Most certainly I'll be installing the maximum amount of RAM possible -
i do practically all builds now using tmpfs, since RAM has gotten so
amazingly cheap and fast, so yes, RAM is key.

CCACHE also helps out considerably, but I haven't been using it lately
out of fear that it had some interference issues with ${CROSS}-emerge
.

Cheers,

C



  parent reply	other threads:[~2009-09-05 12:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 10:48 [gentoo-embedded] personal compile-farm ? Christopher Friedt
2009-09-05 11:07 ` Karl Hiramoto
2009-09-05 12:17   ` Peter Stuge
2009-09-05 12:19   ` Christopher Friedt [this message]
2009-09-05 12:57     ` wireless
2009-09-05 13:05       ` Peter Stuge
2009-09-05 13:53     ` Karl Hiramoto
2009-09-05 15:22       ` Christopher Friedt
2009-09-06  3:47     ` Martin Guy
2009-09-05 21:31 ` jsyrytczyk
2009-09-11  8:13   ` Christopher Friedt
2009-09-06  9:21 ` Ed W

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=3ea34a000909050519q443d40a8m6db896b5544077e2@mail.gmail.com \
    --to=chrisfriedt@gmail.com \
    --cc=gentoo-embedded@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox