Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
neanderthal.uncomplicate.org
Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
1–10 of 19 posts
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#2Author here, feel free to ask me anything.
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#3Hello, Windows 10 user here. How can I be sure I'm using optimized atlas? I tried building it earlier, but with no success. I found some info on atlas forum for older versions, but couldn't get it to work.
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#4Hello, Windows 10 user here. How can I be sure I'm using optimized atlas? I tried building it earlier, but with no success. I found some info on atlas forum for older versions, but couldn't get it to work.
Easy: if it works, it uses the ATLAS version that is installed on the system, which means that when it works, it will use the optimized ATLAS that you provided.
That means that you have to build it itself, which is problematic on Windows, BUT, the author recently released version 3.10.3, and one of major improvements is that builds fine on Windows with cygwin and mingw.
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#5Not knowing what this was I pressed the "Neanderthal" link at the top left, but this got me a 404 at http://neanderthal.uncomplicate.org/articles/
Apart from that, looks good!
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#6Not knowing what this was I pressed the "Neanderthal" link at the top left, but this got me a 404 at http://neanderthal.uncomplicate.org/articles/ Apart from that, looks good!
Fortunately, that link should only lead to the main page of the site. I'll repair that immediately.
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#7Sweet! Did you consider using AutoGEMM.py from clBLAS instead of a static GEMM kernel ?
I was considering using a polyhedral compiler macro (like PPCG), for writing OpenCL kernels in matlisp, but it's not clear how optimal this would be.
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#8Sweet! Did you consider using AutoGEMM.py from clBLAS instead of a static GEMM kernel ? I was considering using a polyhedral compiler macro (like PPCG), for writing OpenCL kernels in matlisp, but it's not clear how optimal this would be.
clBLAS is, in my opinion, hard to build AND hard to integrate.
On top of it, this approach gives better performance in most cases even on AMD, and especially on Nvidia. Now, I have AMD hardware, but it is better to create an overall more encompassing library, thus I avoided clBLAS :)
When I need to write my own OpenCL kernels, I use ClojureCL - it gives me easy management while still retaining full control of the kernels and their performance.
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#9Sweet! Did you consider using AutoGEMM.py from clBLAS instead of a static GEMM kernel ? I was considering using a polyhedral compiler macro (like PPCG), for writing OpenCL kernels in matlisp, but it's not clear how optimal this would be.
clBLAS is, in my opinion, hard to build AND hard to integrate. On top of it, this approach gives better performance in most cases even on AMD, and especially on Nvidia. Now, I have AMD hardware, but it is better to create an overall more encompassing library, thus I avoided clBLAS :) When I need to write my own OpenCL kernels, I use ClojureCL - it gives me easy management while still retaining full control of the ker…
I found the latest version of clBLAS on Fiji achieves a fantastic ~4 Tflops (on 2^n matrices). NVblas has probably had more resources allocated to it that clBLAS. I'd be positively surprised if the kernels in Neantherdal beat those. Do you plan on adding benchmarks for the GPU calls ? I can help running the clBLAS benchmarks, if you like, since I have a tuned setup.
If you want to take a look at it, the AutoGemm generator seems to be a simple python script written in order to overcome the limitations of the C preprocessor. I was considering using its tiling structure, since I already have a Lisp->OpenCL compiler in place (and have had no luck beating it). See, for instance,
https://github.com/matlisp/matlisp-opencl/blob/master/tests/...
https://github.com/matlisp/matlisp-opencl/blob/master/src/te...
Re: Neanderthal 0.8.0: CPU and GPU support on Linux, Windows, and OS X
#10Earlier quoted context omitted.
clBLAS is, in my opinion, hard to build AND hard to integrate. On top of it, this approach gives better performance in most cases even on AMD, and especially on Nvidia. Now, I have AMD hardware, but it is better to create an overall more encompassing library, thus I avoided clBLAS :) When I need to write my own OpenCL kernels, I use ClojureCL - it gives me easy management while still retaining full control of the ker…
I found the latest version of clBLAS on Fiji achieves a fantastic ~4 Tflops (on 2^n matrices). NVblas has probably had more resources allocated to it that clBLAS. I'd be positively surprised if the kernels in Neantherdal beat those. Do you plan on adding benchmarks for the GPU calls ? I can help running the clBLAS benchmarks, if you like, since I have a tuned setup. If you want to take a look at it, the AutoGemm gene…
What is the theoretical MAX flops on that Fiji card? I achieve 3.75 TFLOPS on Hawaii, which has much less power than Fiji...