What Every Developer Should Know About GPU Computing (2023)
blog.codingconfessions.com
What Every Developer Should Know About GPU Computing (2023)
1–10 of 46 posts
Re: What Every Developer Should Know About GPU Computing (2023)
#2This video is a great explainer too:
How do Graphics Cards Work? Exploring GPU Architecture (https://youtu.be/h9Z4oGN89MU?si=EPPO0kny-gN0zLeC)
Re: What Every Developer Should Know About GPU Computing (2023)
#3(2023)
Some discussion then: https://news.ycombinator.com/item?id=37967126
Re: What Every Developer Should Know About GPU Computing (2023)
#4Makes me consider writing a post on misconceptions of GPU computing, such as requiring the problem to be fully data-parallel.
Re: What Every Developer Should Know About GPU Computing (2023)
#5Makes me consider writing a post on misconceptions of GPU computing, such as requiring the problem to be fully data-parallel.
Please do! I would love to read about it. I have been playing with GPU hash tables shared between all the threads using locking (Interlocked.CompareExchange) and such in a Compute Shader. I have been wondering if there are better ways than locking.
Re: What Every Developer Should Know About GPU Computing (2023)
#6If you are not writing the GPU kernel, just use a high level language which wraps up the CUDA, Metal, or whatever.
Re: What Every Developer Should Know About GPU Computing (2023)
#7This video is a great explainer too: How do Graphics Cards Work? Exploring GPU Architecture ( https://youtu.be/h9Z4oGN89MU?si=EPPO0kny-gN0zLeC )
Wow, this is one of the best videos I've ever watched. Thanks for sharing
Re: What Every Developer Should Know About GPU Computing (2023)
#8Unrelated but I absolutely love this reply from the previous time this was posted and someone complained about the line "most programmmers ...":
> Try this on: "A non-trivial number of Computer Scientists, Computer Engineers, Electrical Engineers, and hobbyists have ..."
> Took some philosophy courses for fun in college. I developed a reading skill there that lets me forgive certain statements by improving them instead of dismissing them. My brain now automatically translates over-generalizations and even outright falsehoods into rationally-nearby true statements. As the argument unfolds, those ideas are reconfigured until the entire piece can be evaluated as logically coherent.
> The upshot is that any time I read a crappy article, I'm left with a new batch of true and false premises or claims about topics I'm interested in. And thus my mental world expands.
Re: What Every Developer Should Know About GPU Computing (2023)
#9great
Re: What Every Developer Should Know About GPU Computing (2023)
#10Makes me consider writing a post on misconceptions of GPU computing, such as requiring the problem to be fully data-parallel.
Please do! I would love to read about it. I have been playing with GPU hash tables shared between all the threads using locking (Interlocked.CompareExchange) and such in a Compute Shader. I have been wondering if there are better ways than locking.
Hash tables on GPUs are cool. You can use them for meshless radiance caches, that automatically (for better or for worse) adapt to the surrounding geometry.