-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very high CPU usage compared to Shadertoy #66
Comments
I don't know much about how integrated GPUs work, but I would assume that in this context GPU usage equates CPU usage. Correct me if I'm wrong. I know the extension uses quite a lot of GPU time, depending on the shaders that are used. From my superficial investigation that might be related to THREE.js. The online version of shadertoy does not use the THREE.js framework, but afaik does all the webgl code themselves. But I can't say for sure if it is an issue with how we're using the library or if it is actually doing too much work. It is certainly something work investigating, but probably requires a more involved solution. Do you have an example of which shaders cause the high usage or does it happen really on any shader? |
Is this better in the latest version that uses async I/O? |
On my desktop this is not really a problem but on my laptop with an integrated GPU, the CPU usage goes up to 50%+ on all threads compared to ~15% on the regular Shadertoy website using the same very basic shader code.
I don't know if this is because of a limitation by VSCode or something?
The text was updated successfully, but these errors were encountered: