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 17:22:30 +0200	[thread overview]
Message-ID: <3ea34a000909050822q18c12f91odca9ddc249ea646e@mail.gmail.com> (raw)
In-Reply-To: <4AA26D65.2030201@hiramoto.org>

On Sat, Sep 5, 2009 at 3:53 PM, Karl Hiramoto<karl@hiramoto.org> wrote:
> See the benchmarks a core 2 duo is many times faster than a atom:
> http://www.tomshardware.com/reviews/intel-atom-efficiency,2069-8.html

These benchmarks are for the Atom N230, as opposed to the dual-core
Atom N330, so not really a valid comparison. Clearly, any dual-core
chip will always outperform a comparable single-core chip.

For me, there's a some likelihood that even an Atom N230 will still
outperform the Pentium-M that I have in my laptop at the moment, so
for me, anything would really be an improvement. Having a dual-core
Atom for a build machine would mean 4 concurrent threads instead of 2.

I guess I should really just ask ...

Has anyone recently upgraded their Gentoo machine from a single-core
to a dual-core processor, and if so, was there a clearly noticeable
increase in build speed ?



  reply	other threads:[~2009-09-05 15:22 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 [this message]
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=3ea34a000909050822q18c12f91odca9ddc249ea646e@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