8350rocks :
IPC = Instructions Per Cycle
All that would really mean is that the architecture's capability is going to be utilized efficiently. It does technically possess 150-175% of the horsepower of the intel chip...if it was optimized efficiently internally, it would be a more effective architecture than what intel currently offers.
yes yes... but IPC for x86 is 1 to 1.1 or up to 1.2 "instructions per clock" for a little more optimized code. "full fury" optimized code could be much more, yet staying clearly below the 2 instructions per clock per thread [
makes one wonder why have CPU cores with more than 2 ALU pipes ... right ?] . And NO ONE in current software offerings, that everybody uses, has "full fury"... not even benchmarks that can be more optimized for a particular uarch than another...
[
EDIT: of course in this we are talking about NON VECTOR integer code, which is the traditional and logical way of counting IPC, since architecturally x86 is NOT a "vector" uarch... though good vectorized code could in many cases pass the 2 IPC barrier... ]
Since IPC is talked so much this days, it would be nice to have a "benchmark" that would have code specifically to indicate those numbers ( 1 to 1.2 or so IPC)...so the results would be 0.x to 1.z, or something like that.
Performance depends on so much factors that is hard to beggin with, but with those numbers in mind it would be easy to understand that on x86,
no CPU today is "technically or potentially", anything like 150 to 170% IPC wise more performant than another. Not even Haswell compared with Jaguar, that is, 0.9 compared with 1.2 is around ~35% in "potential"... its much more than that, by many other factors, including instructions in the super bloated pointless x86 logical extensions ( like in vector from SSE to AVX), that one chip have natively, while in another must be executed by "microcode" (painful slow)... which might indicate that the "spree to bloat" to newer instruction extensions was/is only to gain "competitive advantage", accounting with this factor( seems obvious no ?)...
High degrees of advantage/speedup only comes with high parallel data code and high parallel execution models (c
ache and memory and clocks and even logical instructions could never reach that >100% speedups) ... but in here we are NOT talking about CPU but more like GPGPU models...
That is where AMD has an advantage IMO, and it spells APU not CPU. But the apps for this are yet to few and too far in between to make a decisive advantage... "never settle programs" for Multimedia apps could be the salvation of AMD... but doubt those kind will appear as "common benchmark" apps anytime soon...