» Wed Feb 04, 2015 1:55 am
I submitted this as a
bug report and would be interested if anyone else can reproduce what I see on my system....
Try this capx:
physics_asm_v_box2d.capx
It's a variation of the one in the bug report. It creates a large number of physics balls and then just runs as they bounce around in zero gravity - the idea was to create enough balls to stress the system but to maintain near 60 fps in r195. The layout also displays a horizontal scrolling graph of dt so any variations can be seen over time. The number that stresses my system on Chrome is 1600 - so you might need to tweak that up or down depending on what hardware you're using.
To my eye it appears that r196.2 causes more and more frequent frame drops (large dt values > 16 ms) than seemed apparent in r195. This might be a bespoke finding just to my system so it would be good for others to test it and see if it's either just me... It's also worth noting that I also consistently see no discernible improvement in performance when using asm.js over the standard box.2d.
r195 v r196.2 physics perf.png
You do not have the required permissions to view the files attached to this post.