Web workers in 3D web applications

Considering the support for offscreen canvas i don’t see this really as an option. If in a worker or the main thread a overloaded bad managed scene will perform bad either way, the major part should be synchronous with each frame including user input. It rather makes sense to give workers any tasks which can be asynchronous in my opinion.

The only reason i use a offscreen canvas if available is for rendering procedural data sets in Tesseract, what is rather new, before tiles were only rendered in the main-thread in a semi-threaded way by distributing the workload what still works at 60 FPS.

1 Like