THREE.JS / FOUNDATIONS 14
Time the render, not the guess.
Compare host-side render cost with asynchronous GPU timestamps. Change the workload and let the backend tell you what the frame actually cost.
Initializing profiler—
Preparing timestamp queries…
workload
- GPU frame
- n/a
- CPU render
- —
- samples
- 0
- frame draws
- —
- triangles
- —
- objects
- 160
query state
- timestamp query
- —
- query pool
- —
- last resolved
- —
- measurement
- —
GPU time is backend-reported and resolves asynchronously. CPU render is wall-clock time around the synchronous render call; neither is a universal device budget.
Profiler initialization failed.
The renderer could not start.
Drag to orbit · press R to reset · add ?forceWebGL=1 to compare
LAB 14 / GPU TIMING