Looking at Ammo pt1

Since it is a complete physics engine, Ammo.js is a particularly interesting piece of JavaScript that I investigated.  Because of the scale and newness of this technology, it has a share of problems, one being performance.  First, I tested it among several browsers.  I used Firefox and chrome. Using the ammo.js demo, there was a large fps difference in rendering between firefox and chrome.  Surprisingly, Firefox was faster even though chrome is normally faster in every other aspect.

Noting the difference between the browsers helped find the problem with ammo.  Both browsers have a different implementation for their JavaScript engines.  Chrome developers have taken it upon themselves to create a very sophisticated JavaScript engine, so it is safe to assume that some part of Ammo is breaking inside Chrome.  The demo used webgl which Chrome handles faster, so the fact that it ran slower points to the physics being the bottleneck. 

A closer look

Other applications with more intense graphics to render run more smoothly than this demo.  The large cap between the rendering makes me think it is the physics