CUDA.jl
Rust-CUDA
CUDA.jl | Rust-CUDA | |
---|---|---|
15 | 37 | |
1,133 | 2,884 | |
1.1% | 2.4% | |
9.5 | 0.0 | |
7 days ago | 6 months ago | |
Julia | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
CUDA.jl
-
Ask HN: Best way to learn GPU programming?
It would also mean learning Julia, but you can write GPU kernels in Julia and then compile for NVidia CUDA, AMD ROCm or IBM oneAPI.
https://juliagpu.org/
I've written CUDA kernels and I knew nothing about it going in.
- What's your main programming language?
-
How is Julia Performance with GPUs (for LLMs)?
See https://juliagpu.org/
-
Yann Lecun: ML would have advanced if other lang had been adopted versus Python
If you look at Julia open source projects you'll see that the projects tend to have a lot more contributors than the Python counterparts, even over smaller time periods. A package for defining statistical distributions has had 202 contributors (https://github.com/JuliaStats/Distributions.jl), etc. Julia Base even has had over 1,300 contributors (https://github.com/JuliaLang/julia) which is quite a lot for a core language, and that's mostly because the majority of the core is in Julia itself.
This is one of the things that was noted quite a bit at this SIAM CSE conference, that Julia development tends to have a lot more code reuse than other ecosystems like Python. For example, the various machine learning libraries like Flux.jl and Lux.jl share a lot of layer intrinsics in NNlib.jl (https://github.com/FluxML/NNlib.jl), the same GPU libraries (https://github.com/JuliaGPU/CUDA.jl), the same automatic differentiation library (https://github.com/FluxML/Zygote.jl), and of course the same JIT compiler (Julia itself). These two libraries are far enough apart that people say "Flux is to PyTorch as Lux is to JAX/flax", but while in the Python world those share almost 0 code or implementation, in the Julia world they share >90% of the core internals but have different higher levels APIs.
If one hasn't participated in this space it's a bit hard to fathom how much code reuse goes on and how that is influenced by the design of multiple dispatch. This is one of the reasons there is so much cohesion in the community since it doesn't matter if one person is an ecologist and the other is a financial engineer, you may both be contributing to the same library like Distances.jl just adding a distance function which is then used in thousands of places. With the Python ecosystem you tend to have a lot more "megapackages", PyTorch, SciPy, etc. where the barrier to entry is generally a lot higher (and sometimes requires handling the build systems, fun times). But in the Julia ecosystem you have a lot of core development happening in "small" but central libraries, like Distances.jl or Distributions.jl, which are simple enough for an undergrad to get productive in a week but is then used everywhere (Distributions.jl for example is used in every statistics package, and definitions of prior distributions for Turing.jl's probabilistic programming language, etc.).
-
C++ is making me depressed / CUDA question
If you just want to do some numerical code that requires linear algebra and GPU, your best bet would be Julia or Python+JAX.
-
Parallélisation distribuée presque triviale d’applications GPU et CPU basées sur des Stencils avec…
GitHub - JuliaGPU/CUDA.jl: CUDA programming in Julia.
- Why Fortran is easy to learn
-
Generic GPU Kernels
Should have (2017) in the title.
Indeed cool to program julia directly on the GPU and Julia on GPU and this has further evolved since then, see https://juliagpu.org/
-
Announcing The Rust CUDA Project; An ecosystem of crates and tools for writing and executing extremely fast GPU code fully in Rust
I'm excited to eventually see something like JuliaGPU with support for multiple backends.
-
[Media] 100% Rust path tracer running on CPU, GPU (CUDA), and OptiX (for denoising) using one of my upcoming projects. There is no C/C++ code at all, the program shares a single rust crate for the core raytracer and uses rust for the viewer and renderer.
That's really cool! Have you looked at CUDA.jl for the Julia language? Maybe you could take some ideas from there. I am pretty sure it does the same thing you do here, and they support any arbitrary code with the limitations that you cannot allocate memory, I/O is disallowed, and badly-typed code(dynamic) will not compile.
Rust-CUDA
-
[Media] Anyone try writing a ray tracer with rust? It's pretty fun!
Source code [here](https://github.com/ihawn/RTracer) if anyone is interested in taking a look or giving feedback. As a side question, does anyone have any general advise on getting GPU compute working with rust? I tried [this project](https://github.com/Rust-GPU/Rust-CUDA) but had a bunch of issues (And it doesn't look like an active repo anyways)
-
Is rust or python better for Machine learning? Or is there enough decent frameworks?
You have this https://github.com/Rust-GPU/Rust-CUDA
-
toolchain nightly package building issue
What I'm trying to do is check out https://github.com/Rust-GPU/Rust-CUDA for a class project.
- [Rust] État de GPGPU en 2022
- Which crate for CUDA in Rust?
-
Announcing cudarc and fully GPU accelerated dfdx: ergonomic deep learning ENTIRELY in rust, now with CUDA support and tensors with mixed compile and runtime dimensions!
Be warned, NON_BLOCKING streams do not fully synchronize with sync host to device copies. They are not guaranteed to actually finish by the time they return. Meaning its possible to initiate a copy, then initiate a kernel launch, and have the copy be unfinished by the time the kernel is launched. This caused so many confusing bugs that i personally decided to stop using NON_BLOCKING altogether in rust-cuda. https://github.com/Rust-GPU/Rust-CUDA/issues/15
-
In which circumstances is C++ better than Rust?
- Cuda is not doing by FFI linking, instead is compiling CUDA code natively in Rust https://github.com/Rust-GPU/Rust-CUDA and even if it not complete as the C++ SDK is more than a toy
- I learned 7 programming languages so you don't have to
-
GNU Octave
Given your criteria, you might want to consider (modern) C++.
* Fast - in many cases faster than Rust, although the difference is inconsequential relative to Python-to-Rust improvement I guess.
* _Really_ utilize CUDA, OpenCL, Vulcan etc. Specifically, Rust GPU is limited in its supported features, see: https://github.com/Rust-GPU/Rust-CUDA/blob/master/guide/src/... ...
* Host-side use of CUDA is at least as nice, and probably nicer, than what you'll get with Rust. That is, provided you use my own Modern C++ wrappers for the CUDA APIs: https://github.com/eyalroz/cuda-api-wrappers/ :-) ... sorry for the shameless self-plug.
* ... which brings me to another point: Richer offering of libraries for various needs than Rust, for you to possibly utilize.
* Easier to share than Rust. A target system is less likely to have an appropriate version of Rust and the surrounding ecosystem.
There are downsides, of course, but I was just applying your criteria.
-
Your average rustafarians
Technically, yes. There are crates for OpenCL and CUDA, although official ROCm support does not exist yet.
What are some alternatives?
LoopVectorization.jl - Macro(s) for vectorizing loops.
rust-gpu - 🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
cunumeric - An Aspiring Drop-In Replacement for NumPy at Scale
wgpu - Cross-platform, safe, pure-rust graphics api.
awesome-quant - A curated list of insanely awesome libraries, packages and resources for Quants (Quantitative Finance)
rust-ndarray - ndarray: an N-dimensional array with array views, multidimensional slicing, and efficient operations
cudf - cuDF - GPU DataFrame Library
GLSL - GLSL Shading Language Issue Tracker
Tullio.jl - ⅀
WeasyPrint - The awesome document factory
GPUCompiler.jl - Reusable compiler infrastructure for Julia GPU backends.
vk-bootstrap - Vulkan Bootstrapping Iibrary