4 ms·
Intel's problem has always been the libraries in the hpc world. Nvidia understood this early on, and they dumped an ungodly amount of money into getting people
by shaklee3 8y ago
Intel's problem has always been the libraries in the hpc world. Nvidia understood this early on, and they dumped an ungodly amount of money into getting people onto their platform by investing in libraries and tools. Intel thought that by just releasing a card with a bunch of Xeon cores and not a whole lot of accompanying Library support would do the trick.
Their mkl library is a good example of that. There are a bunch of different ways/libraries to accomplish the same task, and it's not always clear which to use. Further, the documentation is basically just an API printout with very few examples. You can't rely on stackoverflow to document things for you.
This isn't unique to Intel either. I'm looking at you AMD. It wasn't until recently that rocm started picking up steam and amd realizing is important -- long after their Enterprise GPUs were out.
- dragontamer 8y ago> Intel thought that by just releasing a card with a bunch of Xeon cores Atom cores, actually. > This isn't unique to Intel either. I'm looking at you AMD. It wasn't until recently that rocm started picking up steam and amd realizing is important -- long after their Enterprise GPUs were out. Between 2010 and 2016, AMD reverse-mortgaged their headquarters and fired roughly 20% of their staff. The highly successful "Small Cat" line of CPUs was cancelled (basis for PS4 / XBox One / and Laptops). There was a significant chance they'd go bankrupt. AMD finally makes money these days, which is probably why ROCm is able to get the proper investments that it deserves. But yes, its way late. But their company definitely couldn't afford to compete against NVidia before Ryzen.
- shaklee3 8y agoIt's a modified Atom core, and is closer to the Xeon cores. It was the first to have the AVX-512 instruction set, followed by the Xeon.