I've no idea in what way KNL isn't a CPU, or how optimizing for it is fundamentally different, from running one in an HPC setting. For vectorized floating poin

I've no idea in what way KNL isn't a CPU, or how optimizing for it is fundamentally different, from running one in an HPC setting. For vectorized floating point code of the sort for which we're particularly interested in these things (e.g. DGEMM), you get peak performance from a single thread/core. The design is supposed to be "balanced", and it does appear to do a reasonable job of that for the sort of code that uses the bulk of the time on our system. In some cases, Broadwell will do substantially better, of course. I don't have URLs for performance examples to hand. People mostly seem to be ignoring the potentially important additions in KNL -- the memory system and the built-in interconnect (though I don't know if the latter is available yet). Also the large core count should help by keeping more MPI communication local. I don't know of any relevant results for multi-node jobs, but 64 cores covers a fair number of the HPC jobs I see.