4 ms·
Xeon Phi is somewhat misunderstood, and its early incarnations have not helped that. The most important point to understand is that it is neither a CPU or GPU a
by jandrewrogers 11y ago
Xeon Phi is somewhat misunderstood, and its early incarnations have not helped that. The most important point to understand is that it is neither a CPU or GPU architecture. Code designed for either of those architectures will be very suboptimal even if it does run adequately.
The Xeon Phi is a modern reincarnation of a barrel processor. It understands x86-64 opcodes but your data structures and algorithms need to be designed quite differently than vanilla CPU code if you want to optimize throughput. No one is doing that though.
In principle, if your code is correctly designed for the architecture, the Xeon Phi should significantly outperform both CPUs and GPUs for a wide range of use cases. The strength of these architectures is that their throughput is relatively insensitive to both latency and lack of trivial parallelism, which are the major bottlenecks to a lot of modern software performance. It is why Intel resurrected this style of computing architecture.
Basically, very few people know how to design software for these architectures even though it is pretty easy (much easier than GPU code). I have experience designing software for exotic architectures like this, I know what they are capable of in terms of throughput, but have never worked with a Xeon Phi. Nonetheless, the silicon specs suggest that someone that actually knows what they are doing should be able to significantly outperform e.g. GPUs for things like machine learning. Right now, it is basically being wasted because most developers treat them like weird CPUs.
I'd love to play with one of the new Xeon Phi processors to characterize its true performance but I am unlikely to see one. But I would not dismiss their performance; it is an extremely efficient kind of architecture for a surprisingly wide range of workloads if used well.
- Tomte 11y agoIt understands x86-64 opcodes but your data structures and algorithms need to be designed quite differently than vanilla CPU code if you want to optimize throughput. No one is doing that though. Would you be willing to expand on that? It sounds fascinating. I'd also gladly take links or key words to google for.
- Tomte 11y agojandrewrogers wrote a bit more a year ago in https://news.ycombinator.com/item?id=8649774 https://news.ycombinator.com/item?id=8649774
- chubot 11y agoHm, that's interesting. If true, it sounds like they need to take a lesson from nVidia and start providing more tools -- for example, the CUDA compiler, and libraries like cuDNN and cuFFT. I'm sure you can do better by hand than the code generated by the CUDA compiler. But people need something to get started with, and it's probably good enough for a lot of applications. In order to get adoption, the vendor has to meet developers closer to the application. There are very few people writing assembly code from scratch anymore... and those that do are probably the kind of people who are designing their own hardware anyway! It makes more sense for the vendor to be writing libraries in assembly, since they know the architecture best. Then apps can build on top of that in higher level languages.
- aristidb 11y agoThey even have some interesting tools, but should IMHO invest more in them: https://ispc.github.io/ https://ispc.github.io/
- sklogic 11y agoCuda computational model does not fit Phi well, you need a different approach (and, ideally, a different language).
- rbanffy 11y agoThey have good OpenCL and MPI support. Intel has tools that help characterize the performance of programs running on it. They are, obviously, complex tools that take some time and dedication to master. http://shop.oreilly.com/product/9780124104143.do http://shop.oreilly.com/product/9780124104143.do is an introduction and weights more than 400 pages.
- 14113 11y agoAccording to an Intel employee I spoke to, OpenCL won't be available from day one on knights landing - all it will support will be OpenMP and MPI. Apparently they're the two main libraries which their target customer (HPC) require, so they're not putting any effort into OpenCL until they're sure it's wanted.
- leoc 11y agoDo you have access to one of the older Phis which were (and maybe still are) available on discount? http://www.phoronix.com/scan.php?page=news_item&px=MTgzNjY http://www.phoronix.com/scan.php?page=news_item&px=MTgzNjY