Replies to post #67486 on Advanced Micro Devices Inc (AMD)

[jhalada]

alan,

I think the issue is floating point,
And in particular linpack. I think the fused macro-ops will allow four floating point operations per cycle, bringing floating point performance above the P4... when code is compiled to take advantage of the "virtual FMAC".

I thought these were 4 integer pipes...

Yeah, on floating point, you can have any performance you want. It is just a question of how much resources you throw at it. But I doubt Intel is going to make Conroe unbalanced in favor of floating point.

On Integer, it is a lot more tricky to extract parallelism, which is why additional pipes get diminishing returns. But Intel may have found some new tricks...

Joe

[KeithDust2000]

alan, Personally, I am not convinced either Athlon 64 NOR conroe will be constrained to 3.2Ghz in 2006.

Search your own posts for something like "expecting less than 5Ghz in 2005 is folly". Whenever I read your projections (not just Prescott) on clock speed, I can´t help thinking "that guy is just too optimistic, everytime". Do you have an explanation for your general bullishness on clock speed scaling? Personally, I think 3Ghz is the max for DC Opteron in 2006, and likely only possible within an extended power envelope.