Optimize a canvas with thousands of moving objects
Tests GPU-bound vs CPU-bound bottleneck diagnosis. Strong answers: batch draw calls to cut JS-to-GPU overhead, and render to a smaller back buffer to reduce fill-rate cost.
Tests whether you can diagnose GPU-bound vs CPU-bound rendering bottlenecks in a high-object-count canvas scene. A strong answer covers two distinct pipeline optimizations: first, batching draw calls or using instanced arrays to collapse thousands of individual submissions into a single GPU command, minimizing driver overhead; second, rendering to a smaller back buffer or limiting devicePixelRatio to reduce fragment-shader workload and memory bandwidth.
Read the original → developer.mozilla.org
- #webgl
- #canvas
- #performance
- #rendering
- #batching
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.