<a href="http://blog.accelereyes.com/blog/wp-content/uploads/2012/02/maria_tweet1.png"><img class="aligncenter size-full wp-image-2202" title="maria_tweet" src="http://blog.accelereyes.com/blog/wp-content/uploads/2012/02/maria_tweet1.png" alt="" width="525" height="76" /></a>

The question above comes from María (<a href="http://twitter.com/turbonegra">@turbonegra</a>).  She follows us <a href="http://twitter.com/accelereyes">@accelereyes</a>.  Many of you are wondering when ArrayFire support for new CUDA version 4.1 will be released.  The answer: work is currently under way.

CUDA 4.1 includes a <a href="http://www.tomshardware.com/news/nvidia-cuda-gpu-developer-llvm,14579.html">new Fermi compiler</a>, and many people in the GPU ecosystem have <a href="http://forums.nvidia.com/index.php?showtopic=222547">reported slowdowns</a> from upgrading to the new CUDA version. So we've delayed releasing ArrayFire and Jacket support for CUDA 4.1 because we want to verify performance and reliability across all our unit tests, performance regressions, and customer code samples.  Our tests sweep across various driver versions and everything from mobile GeForce cards through server-grade Tesla and Fermi chips.

We are still working through the testing and verification at the moment. While <a href="http://developer.download.nvidia.com/CUDA/training/CUDA_4_1_Webinar_v11-11-22.pdf">NVIDIA's general claim of 10% performance benefit</a> are a bit fluffy, things do look <strong>good</strong> overall, and we believe CUDA 4.1 is ready for prime time. Various FFT, BLAS, and LAPACK routines show solid performance enhancements. In the few places where we have observed a performance degradation (e.g. linear texturing), we are working closely with NVIDIA to ensure these are addressed in coming driver and toolkit releases.

We'll post here and on <a href="http://twitter.com/accelereyes">twitter</a> when CUDA 4.1 support ready in ArrayFire and Jacket. Stay tuned!

&nbsp;

PS:  Thanks to María for prompting this post :)