Demos on http://www.babylonjs.com/ (for example, the heart demo) all load much slower in firefox than in chrome. In firefox, when it says "streaming items" it causes a lot of hard drive activity on each number that it counts down (an fsync of a large file perhaps?) whereas in chrome the numbers go down much faster with almost no disk IO noticeable. Sorry if I filed this in the wrong place, I am not sure this is due to IndexedDB, but I do see it uses IndexedDB, and do not see localStorage or sessionStorage being used, and not sure what else could cause such hard drive usage.

(ack, this is the issue i mentioned at the gdc games dinner)

The database code is here to shave a few hops: https://github.com/BabylonJS/Babylon.js/blob/master/Babylon/Tools/babylon.database.js The notable thing is that it detects when Chrome throws a DataCloneError because it does not support storing Blobs (https://code.google.com/p/chromium/issues/detail?id=108012 with some fairly recent landings and backouts, so probably not in most channels at this time) https://github.com/BabylonJS/Babylon.js/blob/master/Babylon/Tools/babylon.database.js#L274 Once that happens the code-path for loading images alters so that it no longer uses IndexedDB, suggesting Chrome might have a significantly reduced I/O load: https://github.com/BabylonJS/Babylon.js/blob/master/Babylon/Tools/babylon.tools.js#L188

Thanks! I filed https://github.com/BabylonJS/Babylon.js/issues/164 over there.