From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: Philip Webb <purslow@ca.inter.net>
Cc: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] new machine : CPU : 22 nm vs 32 nm
Date: Thu, 26 Jul 2012 12:34:07 +0200 [thread overview]
Message-ID: <1525304.7pUK7Ol4gj@localhost> (raw)
In-Reply-To: <20120725202442.GG2965@ca.inter.net>
Am Mittwoch, 25. Juli 2012, 16:24:42 schrieb Philip Webb:
> 120725 Volker Armin Hemmann wrote:
> > 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
>
> In the absence of further explication, I'm likely to go with 22 nm .
because structure size has no influence on the performance - from a user point
of view.
In theory: smaller structers - less power needed - faster switching - so
higher clocks are possible.,
In practice: smaller structures - more leak current - not as much faster
clocks as hoped.
For a user there is no difference between a 3ghz 32nm or a 3ghz 22nm cpu. The
later one MIGHT use less power. But nothing is guaranteed.
>
> >> 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?
>
> These answers are not very helpful : does anyone have anything more so ?
because you don't. cores and nm are in no way related.
>
> >> How far is cache size important ( 6 vs 8 MB )?
> >
> > depends on the architecture.
>
> It occurs to me that a larger cache goes with more cores,
> so the last question is not so important.
no, really, this is the only question that makes sense.
And it depends on the cache structure. A 6mb L3 'victim' cache that only
caches stuff that is not in L2 and L1 might be better than a 8mb L3 cache that
also holds the same stuff as L2 and L1.
--
#163933
next prev parent reply other threads:[~2012-07-26 10:35 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 [this message]
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
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=1525304.7pUK7Ol4gj@localhost \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=purslow@ca.inter.net \
/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