Know your engine limitations!

[AGulev]

I just remembered about Bunny mark test:

Bunnymark benchmark

There are actually quite a few performance improvements you can make. I created my own version: https://github.com/britzl/defold-bunnymark A couple of key things to consider in your version: Don’t do go.get_position(). Keep one vector3 per bunny and work against that vector3 in update(). And if you insist on doing go.get_position, then consider using that vector3 instead of creating a new vector3 for every bunny every frame. Avoid index access into tables (every foo.something requires a looku…

And this test have the same results as @GerodruS results.

And it is so sadly.

For example:

• 2.5 years demo of old version of PIXI.js;
• in browser;
• on ipad4 ;
  Displays 15000 bunnnies without any problem with 60 FPS
  pixi.js bunnymark

Defold IPA (native app!!!) can’t show 500 bunnnies =(