public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new machine : (1) which CPU ?
Date: Fri, 20 Jul 2012 14:18:02 +0200	[thread overview]
Message-ID: <50094C7A.2080203@binarywings.net> (raw)
In-Reply-To: <500949AF.7080704@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]

Am 20.07.2012 14:06, schrieb Dale:
> 
> v_2e@ukr.net wrote:
>>   Hello!
>>
>> On Fri, 20 Jul 2012 03:24:42 -0400
>> Philip Webb <purslow@ca.inter.net> wrote:
>>
>>
>>> However, I'm quite willing to look at AMD or consider waiting a bit
>>> till something newer from Intel reaches the regular market.
>>   Speaking of AMD processors, I remember one of my friends told that
>> their A10-series a good. I didn't study any details of it, but if you
>> are interested, you can check them out as well.
>>
>> Regards, Vladimir ----- <v_2e@ukr.net> 
> 
> I built my rig with a AMD CPU and I like it.  I prefer AMD since it has
> a lot of bang for less bucks.  Mine is this one:
> 
> AMD Phenom(tm) II X4 955 Processor
> 
> I went from 12 to 14 hours building LOo on my older AMD 2500+ single
> core to about a hour or so on my new rig. 
> 
> One thing I have learned over the years when money is tight.  Always buy
> parts that are about 2 to 3 notches below the latest release.  My
> current CPU is 3.2Ghz which is about two notches below the fastest they
> had at the time.  I think the fastest was 3.4Ghz or something.  I saved
> a lot of money but most likely wouldn't be able to see the difference in
> speed.  You can do the same for mobos and such too. 
> 
> Also, with Linux, older hardware has more stable drivers than newer
> stuff.  If you buy a brand new mobo with all new chipsets, you can run
> into stability issues until the drivers get sorted out.  If you buy one
> that has been out a year or so, you have a MUCH better chance of getting
> good stable drivers. 
> 
> As always, your mileage may vary. 
> 
> Dale
> 
> :-)  :-) 
> 

+1 for AMD, especially if you consider integrated GPUs. If you want to
be sure you get a good deal, look for FLOPS per Dollar charts or similar
benchmarks. For example this [1].

[1] http://www.cpubenchmark.net/cpu_value_available.html

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-07-20 12:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20  7:24 [gentoo-user] new machine : (1) which CPU ? Philip Webb
2012-07-20 11:40 ` v_2e
2012-07-20 12:06   ` Dale
2012-07-20 12:18     ` Florian Philipp [this message]
2012-07-20 17:44       ` Dale
2012-07-21  1:27         ` Philip Webb
2012-07-21  1:49           ` Alecks Gates
2012-07-21  2:15             ` Dale
2012-07-21  4:06             ` Michael Mol
2012-07-21  5:55             ` waltdnes
2012-07-21  8:44               ` Florian Philipp
2012-07-21  9:59                 ` v_2e
2012-07-22  3:13               ` Alecks Gates
2012-07-20 12:13   ` Michael Mol
2012-07-20 23:24     ` Mick
2012-07-21 12:33 ` [gentoo-user] " Nikos Chantziaras
2012-07-21 12:56   ` microcai
2012-07-21 13:07   ` Frank Steinmetzger
2012-07-22  3:18   ` Alecks Gates
2012-07-22 13:14     ` Nikos Chantziaras

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=50094C7A.2080203@binarywings.net \
    --to=lists@binarywings.net \
    --cc=gentoo-user@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