Show HN: Canvas engines performance comparison – PixiJS, Two.js, and Paper.js

Re:Show HN: Canvas engines performance comparison – PixiJS, ... by AshleysBrain on Wednesday May 06, 2020 @07:04AM (#23089656)

Shameless plug here, but I made a quick-and-dirty perf test that does something similar in our HTML5 game engine Construct 3, and it appears to run way faster even with 20000 boxes: https://www.scirra.com/labs/boxperf/index.html

This kind of test is easy work for a well-batched renderer. You can accumulate everything in to a single big typed array, copy to a single vertex buffer, and do one call to drawElements() in WebGL, and bingo, tens of thousands of sprites drawn in one go.

I've got other similar performance tests that can do hundreds of thousands of sprites @ 30 FPS (on a high-end machine), which I believe are bottlenecked mainly on memory bandwidth, because I only managed to make it go faster by reducing the size of the JS objects involved.

Modern JS is ultra fast - if you have the right performant coding style.

[ Parent | on HN ]

Re:Show HN: Canvas engines performance comparison – PixiJS, ... by mkalygin on Wednesday May 06, 2020 @07:20AM (#23089749)

FWIW the code in the post doesn't use sprites. I think it is done intentionally because not all of the engines support sprites. As someone mentioned in this thread if PixiJS would use sprites, it could be 10x faster.

[ Parent | on HN ]