Viewing profile — jpsamaroo
jpsamaroo
HN member- Joined
- Tue, Oct 20, 2020, 11:48 PM UTC
- HN karma
- 65
- Public activity
- 17 items
- HN profile
- View on Hacker News ↗
About jpsamaroo
No profile information was provided.
Recent public activity
-
comment
Comment #32005540
This is exciting news! What's also exciting is that it's not just C++ that can run on this supercomputer; there is also good (currently unofficial) support for programming those GP…
-
comment
Comment #30011164
Sxmo uses ModemManager[0] for calls+texts, and mmsd-tng[1] for MMS support. It generally works quite well (in my limited experience), modulo some dropped messages (might already be…
-
comment
Comment #29781148
I think the OP's point is that running these optimizations in production as-is is dangerous because future code changes in the various places could accidentally impede the optimize…
-
comment
Comment #29521134
It is certainly a shame, but I'm confident that Dagger and its new DTable should be able to cover all of the ground that JuliaDB covers, while being far easier to maintain. I think…
-
comment
Comment #29520991
Firstly, I'll say that we already have work started to implement out-of-core directly in Dagger: https://github.com/JuliaParallel/Dagger.jl/pull/289 . With that PR in place, it sho…
-
comment
Comment #29190625
Definitely not dead; Vega is well supported, and with some tweaks, Polaris probably works too (although it definitely was broken in HIP around ROCm 4.0.0 or so). I think AMD has so…
-
comment
Comment #27501603
For kernel programming, https://github.com/JuliaGPU/KernelAbstractions.jl (shortened to KA) is what the JuliaGPU team has been developing as a unified programming interface for GPU…
-
comment
Comment #27501552
AMD has done great work in a very short amount of time, but let's not forget that they're still very new to the GPU compute game. The ROCm stack is overall still pretty buggy, and …
-
comment
Comment #26359562
This is an issue with AMD not wanting to long-term support the code paths in ROCm components necessary to enable ROCm on these devices. My hope is that Polaris GPU owners will step…
-
comment
Comment #26359490
> Jax is even consider to do better in that department in terms on performance then all of julia so wat are u talking about Please provide sources for this claim
-
comment
Comment #26308491
Yes, and that's why Julia gained CUDA support first. My point was to respond to "Why would someone use this instead of plain old OpenCL(or CUDA) with C++?", and my answer was, "you…
-
comment
Comment #26304459
OpenCL and various other solutions basically require that one writes kernels in C/C++. This is an unfortunate limitation, and can make it hard for less experienced users (researche…
-
comment
Comment #25821938
At least for the GPU case, the ecosystem is slowing moving towards writing generic kernels that can be executed on both the CPU (multithreaded) and the GPU, without doing anything …
-
comment
Comment #25821752
JavaScript's JIT is a tracing JIT, so it can compile code in the background while the interpreter/less optimized compiled code is actually running. In Julia, the compiler runs firs…
-
comment
Comment #25140564
Actually, Sxmo has MMS patches pending on the mailing list which allow receiving and viewing text, audio, and video content: https://lists.sr.ht/~mil/sxmo-devel/patches/14017 EDIT:…
-
comment
Comment #24843622
Tim has been working on making it easy to use CUDA.jl and AMDGPU.jl pretty interchangeably through GPUArrays.jl, and this approach seems to be pretty extensible to other accelerato…
-
comment
Comment #24843536
> This is a complete novice, ill informed, question. So forgive it in advanced, but why have an AMD specific backend at all? Couldn't you just use AMD's HIP/HIP-IFY tool on the CUD…