[dead]
CUDA-oxide: Nvidia's official Rust to CUDA compiler
121–130 of 132 posts
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#122Earlier quoted context omitted.
The claim is that people are running CUDA on Windows for business analytics and data science? This feels less likely an accurate picture and more likely any mass data processing is already happening on Linux K8s clusters.
Yes, if they happen to run tooling like Excel, PowerBI, Tableau,.... Also Linux support for CUDA on laptops, especially with dual GPU setup isn't particularly great. Most workstation class laptops are Windows based.
AFAIK neither excel nor Tableau has any CUDA functionality to begin with so I’m not sure what point you’re trying to make. No one is doing CUDA number crunching on local laptops - either the problem is big enough to warrant a proper data center or it’s small enough that a local CPU is fine. Local CUDA is a weird middle ground that requires a lot of complexity for marginal compute capability.
Linux support for CUDA in such an environment is irrelevant.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#123Earlier quoted context omitted.
The claim is that people are running CUDA on Windows for business analytics and data science? This feels less likely an accurate picture and more likely any mass data processing is already happening on Linux K8s clusters.
The K8s clusters do exist, but I've never met anyone in my life that develops their Jupyter notebooks from their business' Kubernetes setup. Most of them don't even use WSL, to my chagrin (and to their detriment).
And they’re running these Jupyter notebooks on CUDA? I’m suspicious there’s a problem size where the complexity of GPU processing is warranted but it’s small enough to be workable with a local Windows machine.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#124Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#125Earlier quoted context omitted.
Yes, because Windows software doesn't sprung into existence out of nowhere.
Neither did Linux software.
It actually did, plenty of it are UNIX ports that predate the Linux kernel, looking for a cheaper home.
Note how Linux only has a relevant market share on deployment scenarios that were previously UNIX/POSIX turf.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#126Earlier quoted context omitted.
Yes, if they happen to run tooling like Excel, PowerBI, Tableau,.... Also Linux support for CUDA on laptops, especially with dual GPU setup isn't particularly great. Most workstation class laptops are Windows based.
AFAIK neither excel nor Tableau has any CUDA functionality to begin with so I’m not sure what point you’re trying to make. No one is doing CUDA number crunching on local laptops - either the problem is big enough to warrant a proper data center or it’s small enough that a local CPU is fine. Local CUDA is a weird middle ground that requires a lot of complexity for marginal compute capability. Linux support for CUDA in…
Because you are lost how a day in the office of a big corporation looks like.
Also this attitude about people not doing compute on laptops, is yet another reason why Intel and AMD keep losing to NVidia.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#127Earlier quoted context omitted.
I think the whole codebase was more or less written by AI...
that ship has long sailed, "it no longer matters" saying a codebase, an article was written with AI doesn't mean much, it could be good, it could be bad. folks often say it to generate outrage, but that means nothing. is the codebase great, good, bad, terrible? that's the only thing that matters.
No, it's always bad. It's just on a spectrum of how competent is the viewer (you and me) to notice how bad it is. It's all shit, the question is whether you are skilled and experienced enough to tell.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#128I'm quite interested in how they dealt with Rust's memory model, which might not neatly map to CUDA's semantics. Curious what the differences are compared to CUDA C++, and if the Rust's type system can actually bring more safety to CUDA (I do think writing GPU kernels is inherently unsafe, it's just too hard to create a safe language because of how the hardware works, and because of the fact that you're hyper-optimiz…
FWIW, Rust’s memory model is more or less completely identical to C++’s, by design. Atomics work the same, there’s provenance, and so on. Whether it is a convenient language for GPU programming probably remains to be seen, but I definitely wouldn’t be surprised if you could make a decent DSL-like API for writing safe code that leverages the full spectrum of GPU oddities. That’s what CUDA is, right?
Originally CUDA hardware was designed without a specific memory model, after C++11, NVidia went into a multi year effort to redesign the hardware to match C++ memory model semantics.
CppCon 2017: "Designing (New) C++ Hardware”
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#129Earlier quoted context omitted.
AFAIK neither excel nor Tableau has any CUDA functionality to begin with so I’m not sure what point you’re trying to make. No one is doing CUDA number crunching on local laptops - either the problem is big enough to warrant a proper data center or it’s small enough that a local CPU is fine. Local CUDA is a weird middle ground that requires a lot of complexity for marginal compute capability. Linux support for CUDA in…
Because you are lost how a day in the office of a big corporation looks like. Also this attitude about people not doing compute on laptops, is yet another reason why Intel and AMD keep losing to NVidia.
Considering I’ve worked for the world’s biggest corporations, medium sized corporations, and startups, I don’t think it’s lost on me. All I said is that the market for single user machine CUDA is marginal which is precisely where Windows dominates, thus even if Mojo doesn’t have windows support to start, it’s not competitively where they need to be.
You’ve been rude and dismissive and raised completely unrelated software, but you haven’t actually figured out a way to attack that claim that single user GPU compute isn’t actually important.
AMD seems to be doing quite well and NVidia is also getting all its revenue and and market cap from cloud GPUs not single user desktops and laptops so I really don’t understand your point - it doesn’t seem to be grounded in the tactical and strategic decisions anyone is making. That’s precisely why Nvidia continue to cripple their consumer parts to avoid them being used by corporations who don’t want to pay the markup for server parts. But even those corporations who would buy NVidia GPUs in bulk would still be doing compute with Linux clusters, not Windows.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#130Earlier quoted context omitted.
FWIW, Rust’s memory model is more or less completely identical to C++’s, by design. Atomics work the same, there’s provenance, and so on. Whether it is a convenient language for GPU programming probably remains to be seen, but I definitely wouldn’t be surprised if you could make a decent DSL-like API for writing safe code that leverages the full spectrum of GPU oddities. That’s what CUDA is, right?
Originally CUDA hardware was designed without a specific memory model, after C++11, NVidia went into a multi year effort to redesign the hardware to match C++ memory model semantics. CppCon 2017: "Designing (New) C++ Hardware” https://www.youtube.com/watch?v=86seb-iZCnI
Thanks, that’s interesting. It feels like a sensible choice.