[6gvONxR4sf7o]

I've been really curious about BEAM languages but never made the leap. How well does it manage heterogeneous compute? I'm used to other languages making me define what happens on CPU vs GPU and defining cross-machine talk around those kinds of considerations.

What parts of that does elixir (and company) allow me to not write? Is there a good balance between abstractions when it comes to still maybe wanting control over what goes where (heteregeneity)?

Super curious and kinda looking for an excuse here :)

[elbasti]

The BEAM is pretty high level, and it's REALLY good at managing distributed compute at the thread or device level.

If you have a parallelizeable workflow, it's very easy to make it (properly!) parallel locally, where by "properly" I mean having supervision trees, sane restart behavior, etc.

And once you have that you can extend that parallelism to different nodes in a network (with the same sanity around supervision and discovery) basically for free. Like, one-line-of-code for free.

Nonetheless, it's all message-passing, and so pretty high level. AFAIK it's not designed for parallelizing compute at GPU scale.

That being said, if you have multiple GPUs and multiple machines that have to coordinate between them, Elixir/Erlang is pretty much perfect.

[throwawaymaths]

If you have a multistage workflow with concurrent and possibly heterogenous requests that hit all the time you can very easily batch and distribute the workflow among compute resources in "the most natural way possible" easily, without having to resort to grace periods, etc. which introduce latency. I think that would be much harder to accomplish with java.

[inawarminister]

I think Numerical Elixir (NX) allows for GPU programming. It uses XLA for scheduling computation?

[ricketycricket]

May not answer all your questions, but this may be a good starting point: https://hexdocs.pm/nx/Nx.Defn.html

[itronitron]

You might want to look at the java aparapi project

Aparapi allows Java developers to take advantage of the compute power of GPU and APU devices by executing data parallel code fragments on the GPU rather than being confined to the local CPU. It does this by converting Java bytecode to OpenCL at runtime and executing on the GPU, if for any reason Aparapi can't execute on the GPU it will execute in a Java thread pool.

https://aparapi.github.io/

https://github.com/aparapi/aparapi

but avoid the non-official fork which sometimes comes up in search results.