Very poor performance about obelisk.js HOT 3 CLOSED

Hi, Ben, thanks for providing the test case. I changed a few code, please see here: http://codepen.io/nosir/pen/wJAfo now it is getting 60fps, mine is i5 macbook air.

You should move primitive(cube) generating logic out of the tick method, cause the primitive instance creating is the part which requires calculating to draw the pixels, and it decreased the performance in your code. As long as the primitive is generated, you can render it in tick loop as many as you want just like using bitmap cache copies.

I might create a wiki page to introduce this, thanks :)

from obelisk.js.

Hey Max, thanks for the help! That performance looks a lot better, I'll try things out with Obelisk. :)

from obelisk.js.

You're welcome, also I think if you could use requestAnimationFrame() instead of setInterval, it makes more sense :)

from obelisk.js.