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 : CPU : 22 nm vs 32 nm
Date: Wed, 25 Jul 2012 22:32:32 +0200	[thread overview]
Message-ID: <501057E0.9030508@binarywings.net> (raw)
In-Reply-To: <14299030.YE6E2ePAfG@localhost>

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

Am 25.07.2012 22:14, schrieb Volker Armin Hemmann:
> Am Mittwoch, 25. Juli 2012, 16:05:29 schrieb Philip Webb:
>> 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  ?
> 
> no
> 

Lower transistor size gives you two advantages: Lower current (->
potentially lower power consumption and heat) and more transistors to do
something. The practical effects depend on what the chip maker does with
this.

>>
>> 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 ?
> 
> who cares?
> 

You cannot really compare this. If you can use more cores, e.g. because
you have an embarrassingly parallel application, by all means, get it.
Otherwise you should probably care more about single core performance.

>> How far is cache size important ( 6 vs 8 MB )?
> 
> depends on the architecture.
> 

In short, for all three questions: Look at benchmarks and look at the
TDP ratings if that is important to you.

nm numbers don't tell you anything that can be directly translated into
performance or other qualities. They only allow educated guesses. If you
really want to delve so deep into chip design, you could as well look at
pipeline depths, cache associativity and such alike (not that you should).

Regards,
Florian Philipp


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

  parent reply	other threads:[~2012-07-25 20:34 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 [this message]
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
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=501057E0.9030508@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