News for hackers. Stuff that matters.

A comment on Assembling WebAssembly. Parent comment

Re:Assembling WebAssembly by zurn on Wednesday June 07, 2017 @12:09AM (#14503696)
Where does even the 2x come from? Currently it looks very much like 1x vs integer hinted JS code like generated by asm.js.
[ Parent | on HN ]
Re:Assembling WebAssembly by jfbastien on Wednesday June 07, 2017 @12:13AM (#14503712)
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.

[ Parent | on HN ]
Re:Assembling WebAssembly by zurn on Wednesday June 07, 2017 @12:22AM (#14503741)
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.

[ Parent | on HN ]
Re:Assembling WebAssembly by jfbastien on Wednesday June 07, 2017 @12:28AM (#14503765)
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.

[ Parent | on HN ]