2 ms·
I think this article is a bit off target. Yes, it's true that a simple recompile of an OpenMP app won't give you peak performance, but it's still nice to be abl
by modeless 15y ago
I think this article is a bit off target. Yes, it's true that a simple recompile of an OpenMP app won't give you peak performance, but it's still nice to be able to do it as a starting point for incremental porting.
Furthermore, while OpenMP apps probably will have scaling issues at 50+ cores, I think the bigger issue that the article hardly mentions is the new wide vector unit in the MIC cores. That's where all the FLOPS happen, and it's a completely new instruction set. x86 is a sideshow. Apps will need to be rewritten for the vector unit to get anywhere near peak performance on MIC.
- pavlov 15y agoSince apps need to be rewritten anyway, what's the value of doing the simple recompile using OpenMP? It doesn't offer sufficient performance and it doesn't function as a template for the rewritten app. The whole thing seems like a marketing-driven exercise in fake compatibility. Imagine a company with an old PalmOS app which needs to be ported to iPad if the company wants to stay relevant. They can't just wrap the Palm app inside an emulator and sell that -- it's just not good enough for a port because it doesn't leverage any of the new platform's strengths. That's pretty much what Intel is proposing.
- modeless 15y agoI disagree that all apps need to be entirely rewritten. I think it would be perfectly reasonable to use an existing OpenMP app as a starting point, and it's likely that some parts would work fine. Even if the MIC chip runs some parts of the app slower than a Xeon would, it could still be worth running those parts on the MIC chip to avoid sending intermediate results through the PCIe bottleneck.