Originally posted by: JackyP
Well the SPEC numbers published on spec.org and discussed at RWT show it to be superior in bandwidth heavy _rates, where K10 and K10.5 normally could rule against penryns. Over at techreport they wrote that even their 1P nehalem (I know it was differently configured) outperformed 2P Shanghai and Penryn in quite a lot benchmarks and they hinted at the power of nehalem many times in the article, I think it's even in their conclusion.
It.Anandtech showed Nehalem to be faster at Linpack.
Many reviews show even Penryn outperforming Shanghai in int workloads (e.g. sunguard ACR, spec_int, spec_int_rate; SPECjvm2008 <- similar performance).
Nehalem improves performance in those applications yet again. So nehalem seems to be faster in most (or at least a lot) of the benchmarks where K10/K10.5 used to rule. The rest is just an extrapolation, as nehalem is based on core 2 and shanghai on deneb and core 2 used to be better in most other applications...
The early leaks of desktop Deneb showed it to be ~5% faster than K10 (linked in my thread), not a single rumour or leak showed Deneb to be considerably faster than Penryn (even though those tend to hype up the products), additionally there's the rule 'a die shrink cannot magically improve your architecture by 15-20%'.
Thus "Shanghai won't have sufficient IPC on many workloads" can be supported as a fact.
You could have found that out yourself going to all the links I posted and read =)
Now I see the interesting tidbits are few and in between and maybe not that easy to find?
...
...
*must stop constantly editing posts* edit #7
Thanks for clarifying Jacky. I apologize if I insulted you at all, as that was not my intent.
