Too Slow at initialization in Window chrome

[dongho-shin]

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]

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]

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.

[gkjohnson]

With the WebGPUPathTracer becoming the priority for the project I'm going through and closing all issues related to the WebGLPathTracer specifically to try to clean things up. Once the WebGPUPathTracer is released we'll plan to remove the WebGLPathTracer from the project (see #779).