Re: [ViennaCL-devel] Coding Style Unification

Hey, > @Toby : I'll also try to take care of runing the auto-tuner/benchmark > script on my HD5850 or Hawaii (It's the Firepro W9100, but you can > advertise a R9 290x for single-precision, as it is much cheaper and has > the same chip for single precision). Which one do you prefer? I opt for th

Re: [ViennaCL-devel] Coding Style Unification

Hi, ViennaCL 1.6.0 should come out with an optimized kernel for GEMM that achieves (on large square matrices) 4 TFLOP/s SP and 1.8 TFLOP/s DP on FirePro W9100 (or 4 TFLOP/s SP on R9 290x). This is for full matrices column-major NoTrans X Trans, or equivalently row-major Trans X NoTrans. I have no

Re: [ViennaCL-devel] Coding Style Unification

Philippe, I couldn't help but notice you have a FirePro W9100. Any chance you have updated benchmarks similar to http://viennacl.sourceforge.net/viennacl-benchmarks.html? I realize the intent of the graphical benchmark SoC project is to get more data from a variety of systems but my curiosity is

Re: [ViennaCL-devel] Coding Style Unification

Hi Philippe, Philippe Tillet writes: > I've already told this on IRC. The GEMV uses very conservative profiles > with very few threads. Now that I have ported a simple version of GEMM > (when only full matrices are used), I'll re-bind the generator into > pyviennacl and will try to get an auto-tu

Re: [ViennaCL-devel] Coding Style Unification

Hey, @Toby : I'll also try to take care of runing the auto-tuner/benchmark script on my HD5850 or Hawaii (It's the Firepro W9100, but you can advertise a R9 290x for single-precision, as it is much cheaper and has the same chip for single precision). Which one do you prefer? @Karl : Yes, an easy

Re: [ViennaCL-devel] Coding Style Unification

Toby St Clere Smithe writes: > ... my Intel Ivy Bridge M GT2 GPU > takes ~0.001s (at last competitive with MKL, though I'm waiting to test > correctness as I write this) ... So it turns out that Beignet [Intel's Linux OpenCL implementation for Ivy Bridge GPUs] is correct (at least here).. Cheers

Re: [ViennaCL-devel] Coding Style Unification

Hey, > I made a small mistake when creating these "conservative" profiles. GEMV > runs with only one work group. I'll fix this, don't worry :) ah, that's an easy fix then. Thanks! Best regards, Karli > > 2014-07-06 13:31 GMT+02:00 Karl Rupp >: > > Hey, > >

Re: [ViennaCL-devel] Coding Style Unification

Hi, > I've already told this on IRC. The GEMV uses very conservative profiles > with very few threads. Now that I have ported a simple version of GEMM > (when only full matrices are used), I'll re-bind the generator into > pyviennacl and will try to get an auto-tuning up and runing in python. > T

Re: [ViennaCL-devel] Coding Style Unification

I made a small mistake when creating these "conservative" profiles. GEMV runs with only one work group. I'll fix this, don't worry :) 2014-07-06 13:31 GMT+02:00 Karl Rupp : > Hey, > > > I'm getting on the plane in a couple of hours, so this might be the last > > you here from me till the middle

Re: [ViennaCL-devel] Coding Style Unification

Hey, > I'm getting on the plane in a couple of hours, so this might be the last > you here from me till the middle of the night Europe time. Have a good flight and enjoy Texas! :-) >> > I suggest we start unifying in a couple of days indeed. I still have a >>> couple of things to merge, ess

Re: [ViennaCL-devel] Coding Style Unification

Hi Toby, I've already told this on IRC. The GEMV uses very conservative profiles with very few threads. Now that I have ported a simple version of GEMM (when only full matrices are used), I'll re-bind the generator into pyviennacl and will try to get an auto-tuning up and runing in python. Then, I

Re: [ViennaCL-devel] Coding Style Unification

Hey all, I'm getting on the plane in a couple of hours, so this might be the last you here from me till the middle of the night Europe time. Karl Rupp writes: > > I suggest we start unifying in a couple of days indeed. I still have a >> couple of things to merge, essentially having GEMM dynamic

Re: [ViennaCL-devel] Coding Style Unification

Hi, > I suggest we start unifying in a couple of days indeed. I still have a > couple of things to merge, essentially having GEMM dynamically generated > for some cases and publishing the repo for auto-tuning using pyviennacl. > These have to be done soon so that Toby can present some good benchm

Re: [ViennaCL-devel] Coding Style Unification

Hey, I suggest we start unifying in a couple of days indeed. I still have a couple of things to merge, essentially having GEMM dynamically generated for some cases and publishing the repo for auto-tuning using pyviennacl. These have to be done soon so that Toby can present some good benchmarks at