From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new machine : CPU : 22 nm vs 32 nm
Date: Thu, 26 Jul 2012 09:50:45 -0400 [thread overview]
Message-ID: <CA+czFiAtTXHbdQKR5jW20xtS1-xEL=_t2zOKqx0_k2CgFQWNLg@mail.gmail.com> (raw)
In-Reply-To: <50114977.9000001@gmail.com>
On Thu, Jul 26, 2012 at 9:43 AM, Евгений Пермяков <permeakra@gmail.com> wrote:
> On 07/26/2012 12:05 AM, Philip Webb wrote:
>>
>> I've listed what's available at the local store,
>> which I trust to stock reliable items, tho' I wouldn't ask their advice.
>>
>> All the AMD's are 32 nm , while the Intel recommended by one commenter
>> -- Core i5-3570 4-Core Socket LGA1155, 3.4 Ghz, 6MB L3 Cache, 22 nm --
>> is 22 nm : it costs CAD 230 & they have 3 in stock,
>> which suggests demand, but not the most popular ( 9 in stock).
>>
>> Isn't 22 nm going to be faster than 32 nm ?
>>
>> In the same price range, AMD offers Bulldozer X8 FX-8150 (125W)
>> 8-Core Socket AM3+, 3.6 GHz, 8Mb Cache, 32 nm ( CAD 220 , 2 in
>> stock).
>>
>> How do you compare cores vs nm ?
>> How far is cache size important ( 6 vs 8 MB )?
>>
>> When I built my current machine 2007, the CPU cost CAD 213 ,
>> so both look as if they're in the right ballpark.
>>
> If you're building new, performance-oriented box, you should take latest
> intel with AVX because of AVX. As I recall, recent gcc has support for avx,
> so some performance gain may be achieved.
> If you want home box, you may be interested in AMD A8 and similar chips, as
> they are reasonably fast and very chip
AMD parts have had AVX since the Bulldozer core release in Q3 2011.
>
> In any case, I'd put most of my money in 2-4 big 3Tb HDD's for media and 8+
> Gb fast memory, as modern browsers eat memory like crazies and CPU is
> usually fast enough. Decoding HDTV mkv's should occur on gpu block in any
> case, so general performance for most uses is irrelevant, as it was fast
> enough four yesrs earlier. Simply check, that you can offload HDTV decoding
> to GPU in your config.
Here, you're talking about either VDPAU or VAAAPI support. VDPAU is
only offered by nVidia cards, and even then you need to run the
proprietary driver. VAAPI is supported by Intel graphics and ATI's
proprietary driver. There's talk about using VDPAU as a backend to
VAAPI, but everything I read on the subect says things like
'potentially' and 'could be'.
--
:wq
next prev parent reply other threads:[~2012-07-26 13:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 20:05 [gentoo-user] new machine : CPU : 22 nm vs 32 nm Philip Webb
2012-07-25 20:14 ` Volker Armin Hemmann
2012-07-25 20:24 ` Philip Webb
2012-07-26 10:34 ` Volker Armin Hemmann
2012-07-25 20:32 ` Florian Philipp
2012-07-25 20:49 ` Michael Mol
2012-07-26 0:21 ` Dale
2012-07-26 1:26 ` [gentoo-user] " walt
2012-07-26 1:56 ` Dale
2012-07-26 1:34 ` [gentoo-user] " Michael Mol
2012-07-26 2:32 ` Dale
2012-07-26 3:01 ` Alecks Gates
2012-07-28 0:56 ` Dale
2012-07-26 0:33 ` [gentoo-user] " Nikos Chantziaras
2012-07-26 0:53 ` Alecks Gates
2012-07-26 8:39 ` [gentoo-user] " microcai
2012-07-26 13:55 ` Michael Mol
2012-07-26 13:43 ` Евгений Пермяков
2012-07-26 13:50 ` Michael Mol [this message]
2012-07-26 14:18 ` Евгений Пермяков
2012-07-26 14:48 ` Michael Mol
2012-07-28 0:30 ` microcai
2012-07-28 0:59 ` Michael Mol
2012-07-28 12:08 ` Pandu Poluan
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='CA+czFiAtTXHbdQKR5jW20xtS1-xEL=_t2zOKqx0_k2CgFQWNLg@mail.gmail.com' \
--to=mikemol@gmail.com \
--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