From: Martin Guy <martinwguy@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] personal compile-farm ?
Date: Sun, 6 Sep 2009 04:47:26 +0100 [thread overview]
Message-ID: <56d259a00909052047m77bca0ddxc64496d6b62a53c5@mail.gmail.com> (raw)
In-Reply-To: <3ea34a000909050519q443d40a8m6db896b5544077e2@mail.gmail.com>
On 9/5/09, Christopher Friedt <chrisfriedt@gmail.com> 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 built a 12-cpu one (using 400MHz pentiums, the maximum MHz/price for
old junk on ebay at the time!) and got pretty much linear speedup
using distcc with 2 jobs on each CPU.
M
next prev parent reply other threads:[~2009-09-06 3:47 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
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 [this message]
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=56d259a00909052047m77bca0ddxc64496d6b62a53c5@mail.gmail.com \
--to=martinwguy@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