Skip to content

Too Slow at initialization in Window chrome #680

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

Open
dongho-shin opened this issue Mar 20, 2025 · 2 comments
Open

Too Slow at initialization in Window chrome #680

dongho-shin opened this issue Mar 20, 2025 · 2 comments

Comments

@dongho-shin
Copy link
Contributor

I'm raising this as an issue to see if anyone has found a workaround for the slow initialization on Windows Chrome. (I understand that performance issue can be solved WebGPU.)

I check the performance with profiler, getProgramInfoLog and getProgramParameter functions are taking up the most of time, which is explained in getProgramInfoLog performance issue.

@dongho-shin
Copy link
Contributor Author

dongho-shin commented Mar 20, 2025

it seems to Window 10, chrome got KHR_pararell_shader_compile not supported. I think it's a key for this issue i'll dig it more
=> Actually in mac there's no difference between angle backend OPENGL(not supported), Default(supported)

@gkjohnson
Copy link
Owner

Yes unfortunately this is a known issue with Windows 10 and the direct x shader compiler. The pathtracing shader can take up to 30 seconds if I recall correctly - it compiles much more quickly on mac devices. Async compilation is the best solution for this as far as I know but unfortunately there's not much that can be done if the extension isn't supported. There are some issues in the chrome bug tracker like this one but I don't expect this will be fixed in Chrome / ANGLE / DirectX any time soon if ever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants