4 ms·
I think x86 shows that you don't have to have zero bad ideas in order to get a high performance design.
by monocasa 6y ago
I think x86 shows that you don't have to have zero bad ideas in order to get a high performance design.
- PaulHoule 6y agoYou have to have zero bad ideas that set a ceiling on performance... e.g. you have clear ALL the bottlenecks out of the way. Just doing something about the one potential bottleneck that you feel like doing something about doesn't necessarily get you a gain in performance at all.
- monocasa 6y agoCan you point out the specific bottlenecks that hampered Itanium and Cell?
- PaulHoule 6y agoItanium's problem I know pretty well. The idea of scheduling parallelism in the compiler (VLIW) doesn't work for mainstream workloads because the time it takes for data to come back from the DRAM is highly variable. A super-scalar processor can possibly run some instructions at the hardware level while other block wait until data gets back from DRAM. A VLIW processor packs N instructions together (say N=3) and if one of them is blocked by DRAM, they all block. (If one of them is blocked by Optane they all block for a very long time...) It looks obvious in retrospect but it's amazing how most of the RISC workstation vendors missed it and put themselves out of business by getting on the Itanic train. (VLIW is successful for DSP and GPU, but that's because workloads like that can have completely predictable fetches) I don't know what the problem w/ Cell was exactly, but it was the same in that it couldn't pull data from DRAM fast enough to keep the silicon busy.
- monocasa 6y agoWith Itanium, they had advanced loads to decouple the pipeline from unknown memory latencies. Also Itanium was a heavily superscalar design; I think you meant out of order. Cell just plain didn't really let you directly address main RAM, so you never saw unknown DRAM accesses stalling the cores. Access to the local memory was always single cycle. In neither case was unknown RAM latencies an issue with the design.