undefined | Better HN

0 pointszurn9y ago0 comments

Where does even the 2x come from? Currently it looks very much like 1x vs integer hinted JS code like generated by asm.js.

0 comments

3 comments · 1 top-level

jfbastien9y ago· 2 in thread

That is incorrect. See: https://github.com/WebAssembly/spec/blob/master/papers/pldi2...

These are already old numbers, and section 7.3 says 33.7% more efficient. Were one to run updated numbers, and use more than Chrome and Firefox, I'm pretty sure the numbers would be better still.

zurnOP9y ago

Very interesting looking paper, thanks.

I note that the comment in 7.3 says the biggest speedup vs asm.js is in validation, so I assume this means the measurement includes startup. This advantage is easy to concede to WebAssembly due to its design.

jfbastien9y ago

FWIW I trust that the numbers were good when the Google and Mozilla folks gathered them, but I had nothing to do with numbers!

In particular, I haven't looked into validation. JSC doesn't treat asm.js any differently than JavaScript, so the comparison would be different as well.

j / k navigate · click thread line to collapse