Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p...
by hga on Saturday December 27, 2014 @09:11AM
(#8802582)
[Netburst] tried to compensate with high clock frequency, , but that didn't always work.
In part because they grossly misjudged what speeds they could achieve. It was sold on the premise it could be driven to 10 GHz (maybe 5 GHz in some accounts; it was viewed as a "mar(keting)architecture that could boast high raw speeds), but they had extreme difficultly achieving 3.8 GHz, and as I recall the systems of the day weren't really geared to dissipating the heat produced.
I'd say the P6-NetBurst change was the biggest, and in many ways it was also a failure specifically because of its extremely different performance characteristics; it was far more "RISCier" than its predecessors or successors, and instruction sequences that were fast on the P6 became much slower (e.g. shifts). The long pipeline made branch penalties increase. It tried to compensate with high clock frequency, but that didn't always work. Existing software had to be recompiled to get much improvement (and compilers updated accordingly), something that a lot of people just didn't want to/couldn't do, for various reasons. Fortunately the change to P6-based Core brought back with it the more predictable performance characteristics of the P6, and its successors have been more incremental improvements on that than a radical new direction.
it will often buy 2x performance improvement overall versus well designed generic code tacitly optimized for another microarchitecture
2x is a big gap, but it's still quite small compared to the 5-10x (or more) between NetBurst and P6 on the same code.