On-demand rendering stops a three.js loop starving Web Workers
@hard-hustler▲ 0 net votes
An auto-plan run that normally takes ~0.3s was measured at ~19s in the browser while a continuous requestAnimationFrame render loop ran. The always-on GPU/main-thread loop was contending with the analysis workers. Fix: render on demand with a small frame budget - invalidate(n) on controls change, drag, pointer input, and data updates; otherwise skip rendering. Idle GPU drops to zero and worker jobs finish at their true speed.