AlmightySnoo 🐢🇮🇱🇺🇦

Yoko, Shinobu ni, eto… 🤔

עַם יִשְׂרָאֵל חַי Slava Ukraini 🇺🇦 ❤️ 🇮🇱

  • 45 Posts
  • 112 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle











  • Something you’ll learn to live by once enter the workplace: your coworkers are not your friends. There might be a one in a thousand case that’s an exception to this rule, but most of the time you should not think of them as more than coworkers you have to work with to get your job done. I’ve witnessed too many cases of coworkers backstabbing each other for their own professional ambitions or where a coworker dies and everyone just completely forgets about him a few days later.

    That doesn’t mean you should be overly pessimistic either. The idea is to be pragmatic. No one wants a toxic environment, so everyone will put in some effort to maintain a cozy facade, and you should too, as that minimizes tensions for everyone. The mistake would be forgetting that it’s all a facade and starting to think of them as something like a family, that’s a mistake most juniors make.

    My motto is: smile at your coworkers but guard your damn ass when you turn your back to them.









  • ROCm is that its very unstable

    That’s true, but ROCm does get better very quickly. Before last summer it was impossible for me to compile and run HIP code on my laptop, and then after one magic update everything worked. I can’t speak for rendering as that’s not my field, but I’ve done plenty of computational code with HIP and the performance was really good.

    But my point was more about coding in HIP, not really about using stuff other people made with HIP. If you write your code with HIP in mind from the start, the results are usually good and you get good intuition about the hardware differences (warps for instance are of size 32 on NVidia but can be 32 or 64 on AMD and that makes a difference if your code makes use of warp intrinsics). If however you just use AMD’s CUDA-to-HIP porting tool, then yeah chances are things won’t work on the first run and you need to refine by hand, starting with all the implicit assumptions you made about how the NVidia hardware works.


  • HIP is amazing. For everyone saying “nah it can’t be the same, CUDA rulez”, just try it, it works on NVidia GPUs too (there are basically macros and stuff that remap everything to CUDA API calls) so if you code for HIP you’re basically targetting at least two GPU vendors. ROCm is the only framework that allows me to do GPGPU programming in CUDA style on a thin laptop sporting an AMD APU while still enjoying 6 to 8 hours of battery life when I don’t do GPU stuff. With CUDA, in terms of mobility, the only choices you get are a beefy and expensive gaming laptop with a pathetic battery life and heating issues, or a light laptop + SSHing into a server with an NVidia GPU.