2 ms·
The old version does AVX and the new version doesn't? Thats crazy! AVX can result in a large speedup [1] in codes that would otherwise not vectorized. For alrea
by frozenport 14y ago
The old version does AVX and the new version doesn't? Thats crazy! AVX can result in a large speedup [1] in codes that would otherwise not vectorized. For already existing codes it can be 20%.
The best strategy may be to work with ec2 or reject the AVX non-compliant instances.
[1] http://www.behardware.com/medias/photos_news/00/30/IMG0030514.gif?iact=hc&vpx=757&vpy=114&dur=12085&hovh=177&hovw=284&tx=90&ty=88&sig=108728287951082340176&ei=QCntUMHgIcrY2QWfsoDABQ&page=1&tbnh=147&tbnw=229&start=0&ndsp=18&ved=1t:429,r:16,s:0,i:138 http://www.behardware.com/medias/photos_news/00/30/IMG003051...
- kelkabany 14y agoThe older hardware (Intel Xeon X5550) for m2.* instances did not support AVX. The newer hardware supports AVX, but to maintain compatibility with the old hardware, it is disabled (but was still advertised, which is what caused the issue). AVX is turned on in newer instances like the cc2.8xlarge, which maps to the f2 core on PiCloud.
- masklinn 14y agoNeither version does AVX, the old ones because it's not hardware-supported and the new one because it's disabled in the hypervisor. But some packages apparently don't fully check AVX support: they check that the hardware is AVX-able, but they don't check if it's been disabled.