cl-cuda
magicl
cl-cuda | magicl | |
---|---|---|
5 | 14 | |
270 | 226 | |
- | 0.4% | |
0.0 | 5.4 | |
almost 3 years ago | 6 months ago | |
Common Lisp | Common Lisp | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cl-cuda
-
Why Lisp? (2015)
> You can write a lot of macrology to get around it, but there's a point where you want actual compiler writers to be doing this
this is not the job of compiler writers (although writing macros is akin to writing a compiler but i do not think that this is what you mean). in julia the numerical programming packages are not part of the standard library and a lot of it is wrappers around C++ code especially when the drivers to the underlining hardware are closed-source [0]. also here is the similar library in common lisp [1]
[0] https://github.com/JuliaGPU/CUDA.jl
[1] https://github.com/takagi/cl-cuda
- Fast and Elegant Clojure: Idiomatic Clojure without sacrificing performance
-
Hacker News top posts: Aug 14, 2021
A Common Lisp Library to Use Nvidia CUDA\ (0 comments)
- A Common Lisp Library to Use Nvidia CUDA
-
Machine Learning in Lisp
Personally, I've been relying on the stream-based method using py4cl/2, mostly because I did not - and perhaps do not - have the knowledge and time to dig into the CFFI based method. The limitation is that this would get you less than 10000 python interactions per second. That is sufficient if you will be running a long running python task - and I have successfully run trivial ML programs using it, but any intensive array processing gets in the way. For this later task, there are a few emerging libraries like numcl and array-operations without SIMD (yet), and numericals using SIMD. For reasons mentioned on the readme, I recently cooked up dense-arrays. This has interchangeable backends and can also use cl-cuda. But barring that, the developer overhead of actually setting up native-CFFI ecosystem is still too high, and I'm back to py4cl/2 for tasks beyond array processing.
magicl
-
A tutorial quantum interpreter in 150 lines of Lisp
(Link didn't work for me)
https://github.com/quil-lang/magicl/blob/master/src/high-lev...
-
Why Lisp?
use MAGICL. [1] It is optionally and transparently accelerated by BLAS/LAPACK.
[1] https://github.com/quil-lang/magicl/blob/master/doc/high-lev...
-
How fast can you multiply matrices using only common lisp?
Maybe have a look at how magicl does this?
-
A software engineer's circuitous journey to calculate eigenvalues
This is essentially the first option, which is already supported by MAGICL by loading MAGICL/EXT-LAPACK [1].
[1] https://github.com/quil-lang/magicl#extensions
-
Uncle Stats Wants You
I think what the magicl team has done is brilliant - allowing multiple implementations is awesome.
-
Good Lisp libraries for math
Second up is magicl, especially useful if performance is a concern. This might not be as extensive as numcl, but it's been battle tested in the industry over the last decade or so. Because this uses generic functions, so long as you are using not-very-small arrays, performance should not be a concern for you. And even if you are, you could write your own functions that use the low-level functions that magicl's backends define. Otherwise performance can be at par with numpy.
-
Why is python numpy *so* much faster than lisp in this example?
This Dev How-To describes (I hope in enough detail) how to add these specialized routines to MAGICL.
-
CL-AUTOWRAP generated (C)BLAS wrapper in QUICKLISP
I agree... and I do don't want be the person who has not rallied. I just took a look at guicho's issue from 2019. And here, you yourself have admitted that the high level interface is less than ideal and needs more work. However, the very point that magicl is an industry standard could imply that potentially radical backward-incompatible changes can be hard. But, honestly, I want to discuss this, time permitting!
- Fast and Elegant Clojure: Idiomatic Clojure without sacrificing performance
-
Anybody using Common Lisp or clojure for data science
Common Lisp is a great language to build new tools for data science, but currently has pretty awful library support existing data science workflows. Common Lisp is sorely lacking in high-quality statistics, plotting, and sparse arrays. There’s been a long work-in-progress library to bring flexible and high-performance linear algebra to Lisp, but it needs more contributors.
What are some alternatives?
numcl - Numpy clone in Common Lisp
lisp-matrix - A matrix package for common lisp building on work by Mark Hoemmen, Evan Monroig, Tamas Papp and Rif.
criterium - Benchmarking library for clojure
py4cl - Call python from Common Lisp
numericals - CFFI enabled SIMD powered simple-math numerical operations on arrays for Common Lisp [still experimental]
Petalisp - Elegant High Performance Computing
hash-array-mapped-trie - A hash array mapped trie implementation in c.
rewrite - Automated mass refactoring of source code.
april - The APL programming language (a subset thereof) compiling to Common Lisp.