3 ms·
It's good that there is competition, but it speaks for emscripten that Cheerp (formerly known as duetto) had to pick two relatively obscure areas where emscript
by flohofwoe 11y ago
It's good that there is competition, but it speaks for emscripten that Cheerp (formerly known as duetto) had to pick two relatively obscure areas where emscripten+asm.js can be beaten.
The slower startup speed with asm.js enabled, at least in Spidermonkey is because it does Ahead-Of-Time (AoT) compilation. The advantage is that once the binary code is generated, it will never be touched again. Other JS engines might decide to de-optimize and re-compile some code, or go through several 'tiers' and only optimize the hot-running parts, which means slow first-time execution and at worst stuttering at unpredictable times. Both are deadly for apps where a smooth frame update is required.
I wonder why startup speed in V8 is slow though, AFAIK it doesn't do AOT compilation, or is this now the case with the new Turbofan module?
The second area, dynamic memory growth is unfortunate at first glance, but a trade-off for better performance, I wonder if pre-allocating a large chunk of memory is still as much an issue in 64-bit browsers as with 32-bit.
- reitzensteinm 11y agoIn my experience with Unity HTML 5, Firefox beats the hell out of Chrome, both on startup time and cold performance (they are both great when warmed up). I'm not too happy that the browser that was first to deprecate native plugins didn't provide usable asm.js as a replacement first.
- azakai 11y ago> I wonder why startup speed in V8 is slow though, AFAIK it doesn't do AOT compilation, or is this now the case with the new Turbofan module? Correct, Turbofan does a lot more up-front compilation for asm.js. There is also work in v8 to do full asm.js validation and AOT using that info, https://bugs.chromium.org/p/v8/issues/detail?id=4203 https://bugs.chromium.org/p/v8/issues/detail?id=4203 > I wonder if pre-allocating a large chunk of memory is still as much an issue in 64-bit browsers as with 32-bit. On 64-bit it's mostly a non-issue, yeah, you can allocate a single 1GB+ chunk fairly easily. There have also been big improvements on 32-bit Chrome over the last year, https://code.google.com/p/chromium/issues/detail?id=394591 https://code.google.com/p/chromium/issues/detail?id=394591 https://code.google.com/p/chromium/issues/detail?id=533580 https://code.google.com/p/chromium/issues/detail?id=533580 But again, this is mostly a non-issue on 64-bit, and 64-bit is rapidly becoming the norm anyhow.