3 ms·
The abstraction does not require a lot of understanding/bodges to get performant code by amateurs: https://cuda.juliagpu.org/stable/tutorials/introduction/ htt
by Joel_Mckay 2mo ago
The abstraction does not require a lot of understanding/bodges to get performant code by amateurs:
https://cuda.juliagpu.org/stable/tutorials/introduction/ https://cuda.juliagpu.org/stable/tutorials/introduction/
But I agree the shared memory Distributed Computing part of Julia still needs a lot of work. Spawning binary image instances over ssh is too fragile. =3
- deleted 2mo ago[deleted]
- Someone 2mo ago> The abstraction does not require a lot of understanding/bodges to get performant code by amateurs I agree the change is simple, and didn’t question that; I questioned the “implicitly” in the claim > Julia is the first language I've seen in years that implicitly abstracts parallelism cleanly. (Aside: I think scala does this even nicer. There, adding `.par` can make code run multi-threaded. See https://docs.scala-lang.org/overviews/parallel-collections/overview.html https://docs.scala-lang.org/overviews/parallel-collections/o...)
- Joel_Mckay 2mo agoIf you read the tutorial, the broadcast iterators and GPU kernel are often implicit. As the CUDA array type hints means you don't need to explicitly define standard operations unless doing something custom. I hope one day Julia does a cleaner version of Scala or Erlang/Elixir OTP languages. Clustering on OTP was certainly an area even seasoned gray beards tried to avoid. =3 https://youtu.be/lg-710Kk5CM?t=20 https://youtu.be/lg-710Kk5CM?t=20