WAMR3D vs three.js r186: the same scene

Compare: each engine with its own WebGPU renderer, same scene code WAMR3D (WebGPU) against three.js (WebGL), same scene code WAMR3D batched calls against three.js (WebGPU) transforms only: both drawn by the three.js WebGL renderer Small cubes: 125002000500010000 Reload both · open one at a time for a fair measurement: left · right · WAMR3D demo with parity check

"CPU update" is animation, world matrices and camera matrices; "draw submission" is the renderer's work on the CPU. Frame rate is capped by the display and shared by two canvases in this view, so it is not an engine measurement: use node examples/compare/measure.mjs --gpu for numbers.