O.K. fucking major rant below. Disclaimer I worked for an vendor selling large quantities pretty much anything in the HPC space at the time KNC came to market a

O.K. fucking major rant below. Disclaimer I worked for an vendor selling large quantities pretty much anything in the HPC space at the time KNC came to market and I now work for a different (larger) HPC vendor. When I say "Larrabee" I mean all of Knights, all of MIC, all of Xeon Phi, all of the "Isle" cards - they're all exactly the same chip and the same people and the same software effort. Marketing seemed to dream up a new codeword every week, but there was only ever three chips: Knights Ferry / Aubrey Isle / LRB1 - mostly a prototype, had some performance gotchas, but did work, and shipped to partners. Knights Corner / Xeon Phi / LRB2 - the thing we actually shipped in bulk. Knights Landing - the new version that is shipping any day now (mid 2016). I can kind of see what the author is getting at here but it's worth reminding general readers KNL is a wildly different beast from KNF or KNC. 1. It's self hosting, it runs the OS itself/ there is no "host CPU". - Yes KNC ran it's own OS but it was in the form of a PCI-E card which still had to be put into a server of some kind. - Yes KNL is slated to have PCI=E card style variants but the self hosting variants are what will be appearing first and I honestly don't think the PCI-E variants will gain much if any market traction. 2. It features MCDRAM which provides a massive increase in total memory bandwidth within the chip. Arguably this is necessary with such large core counts. 3. Some KNL variants will have Intel's Omni-Path interconnect directly integrated which should further drive down latency in HPC clusters. Behind all that marketing, the design of Larrabee was of a CPU with a very wide SIMD unit, designed above all to be a real grown-up CPU - coherent caches, well-ordered memory rules, good memory protection, true multitasking, real threads, runs Linux/FreeBSD, etc. Here's an interesting snippet, drop "Larrabee" from the above and replace it with "Xeon". I'm just wanting the point here that the Xeon and Xeon Phi product lines are only going to look more similar over time. For a while now the regular Xeons have been getting wider. Which is to say more cores and fatter vector units. The Xeon Phi line started out with more cores but is having to drive the performance of those cores up. Over time we're going to see one line get features before the other e.g. AVX512 is in KNL and will be in a "future Xeon" (Skylake). And it's widely rumored that "future Xeons" will support some form of non-volatile main memory, something not on any Xeon Phi product roadmap today. The main differentiator will be that Xeon products need to continue to cater to the mass market whereas Xeon Phi can do more radical things to drive compute intensive workloads (HPC). Larrabee, in the form of KNC, went on to become the fastest supercomputer in the world for a couple of years, and it's still making a ton of money for Intel in the HPC market that it was designed for, fighting very nicely against the GPUs and other custom architectures. Yes at the time Tianhe 2 made it's debut it was largely powered by KNC and it placed at number 1 on the top 500. Did KNC as a product make a lot of money for Intel? Probably not. Yes they shipped a lot of parts for Tianhe 2 but for other HPC customers, not so much. At the time putting a KNC card against a Sandy Bridge CPU it wasn't leaps and bounds faster. Yes you're always going to have to re-factor when making such a change in architecture but the gains just weren't worth it in most cases. Not to say there haven't been useful deployments of KNC that have contributed to "real science", but it was not a wild success by any measure. As for "fighting very nicely against the GPUs and other custom architectures", I don't think so. When KNC got to the market Nvidia GPUs already had a pretty well established base in the HPC communities. Many scientific domains already had GPU optimized libraries users could pick off the self and use. Whilst KNC was cheaper than the Kepler GPUs on the market at the time it wasn't much cheaper. Again back to regular Xeons, for a cost/ performance benefit KNC wasn't worth it for a lot of people. Its successor, KNL, is just being released right now (mid 2016) and should do very nicely in that space too. I do agree with this, KNL is going to do very well. There are whole systems being built with KNL rather than large clusters with some KNC or some GPUs. 1. Make the most powerful flops-per-watt machine. Not sure what is mean here, most efficient machine in the top 10? Tianhe 2 is not an efficient machine by any stretch of the imagination. For reference here's the top 10 of the Green 500 for when Tianhe 2 placed as number 1 on the Top 500. http://www.green500.org/lists/green201306 http://www.green500.org/lists/green201306 SUCCESS! Fastest supercomputer in the world, and powers a whole bunch of the others in the top 10. Big win, covered a very vulnerable market for Intel, made a lot of money and good press. Yes KNC provides the bulk of the computing power for Tianhe 2 but at the time of writing of the above is number 2, not number 1. Secondly that is the ONLY machine in the top 10 that uses KNC AT ALL.