Compute shaders are finally available on the web, thanks to WebGPU.
In this video, we’re gonna dive deep into the world of GPU Compute Shaders.
This is part 2 of our new WebGpu series.
Here’s the link to part 1:
Subscribe so you don’t miss out our next videos.
FAQ Readme File:
Fantastic Articles To Read:
Chapters:
00:00 Intro
01:10 Measuring Performance
02:48 Simple Addition
08:26 Perlin Noise
10:47 Maze Generation
15:41 Particle System
18:50 Outro
——————–
Visionary 3D:
Twitter Account:
Discord Community:
Shaders Crash Course:
My Shaders Playlist:
#webgpu
#computeshaders
#computeshader
#compute_shader
#shaders
#threejs
#webgl
#wgsl
💣Mistakes:
2:19 – Computer Engineers didn't invent Big O. Mathematician Paul Bachmann did.
5:04 – I didn't explain how to write WGSL in this video. To learn a bit more about this language, take a look at my previous video.
5:52 – When you have a for loop, the big o run-time is O(n) only if the stuff that's happening in the loop is running in constant time.
12:52 – I'm sorry for my incompetence in writing rust. Maybe I shouldn't have used it in the video.
15:11 – Here I'm comparing Binary Tree implementation in WebGPU to DFS implementation in C++ and JS. I should've been more clear about this.
17:23 – Here in this screen shot, I forgot to use the WindTurbulenceForce which is being used in the compute shader.
19:08 – I lied. Lying is not good 🙂
He's gonna summon @ThePrimeagen saying things like "Blazingly Fast" 😂
Excellent video! Loved the pacing and the amount of info you provided in this one. Enough to make people excited and start exploring the concepts on their own.
Appreciate the effort! Thank you.🙏
I've never heard someone say WGSL like that lmao
on point subbed!
–release
Try using web worker pool while writing wasm next time.
showing numbers without code isn't that helpful tbh
Theme is interesting but format is not, having everything you say displayed on slides is not very fun to follow (one can get the transcript for this), way too long vid than it should
hi, great video, could you upload the code somewbere?
Javascript isn't slow, when compared to its peers. Its slow if you're comparing it to C/C++, Rust aka compiled languages and even java/C# compiled bytecode languages. But Javascript compared to python, perl, php, ruby, lua, aka interpreted languages, Javascript is literally the fastest. The issue is people like using Javascript for things that it shouldn't be used for, so it feels slow.
Finally, a video on the internet, that talks about C++ and Rust, and doesn't slander C++, cheers brother.
Although I couldn't grasp quite a bit of this vedio since I am a novice dev . The quality of the vedio is superb . Hope to see you grow .
Really good anumations and basicaialy video editing. Althought… its just using gpu… you can do it already in I think vulkan
Did you do cargo build with a release flag???? For rust
Ok, was first triggered by the “so darn slow” (the javascript multi stage JIT compiler is a piece of marvel)… and then I saw the sub-title on 1:09. Well played. Great video!
Let Rust for Application Code or the cool kids out there.
Core Components, Library Code, or any heavy-lifting etc.. – that's C++ Land, and it's gonna take a while till something beats that.
All hail C++❤
The interesting comparison would be, how much slowdown the webgpu abstraction introduces compared to a C++ cuda implementation. Rather than comparing CPU vs GPU Code.
Awesome video!
Could you explain how you measured the time for GPU compute without including the buffer copy / how you were able to measure the time of the buffer copy and subtract it?
love your work brother
I was almost crying at the end of the video man
I'm blown away. Not by WebGPU (although that's pretty incredible too), but by how amazing this video is. The pace at which you give information was on point, animations were pretty cool and I can't believe you took the time to implement these algorithms in wasm and webgpu! Keep it up man, loved this video and I'm excited to see your future ♥
Wow this was a great video, really informative, good job! The visuals were on point as well. I would be interested in a beginner's guide to webgpu as well, I find the syntax a bit confusing, if you're looking for video ideas 😉
I worked a lot to improve javascript performance for Web gpu…you can use different techniques to improve performance, use delta time,use performance.now() for getting time and do not use date.now(),use getImageData() function, if you using html canvas simply you can improve performance by reducing the width and height of the canvas, using less code can be helpful, using webgl and glsl can be very helpful, using three.js needs more performance, importing images by html and css needs less performance than javascript Image() object and many more techniques you can use to improve performance
if the data is in gpu land
is it persistent or we can use malloc like functions to delete the unnecessary data after
the task has been completed
Greatttte man❤
good goood goooooood! thanks!
I think it was an accurate, comprehensive and practical comparison! Excellent🤌👌🏻👌🏻🔥
next: what is "atomic"
For the GPU image, showing an external graphics card is kind of becoming passé. I type this on an iPad. Has GPU. Benefits from WebGPU. But no physical card.
Alternate image: highlight GPU cores of any modern APU chip.
I learn WebGPU, i wanna make cartoon object