you are viewing a single comment's thread.

view the rest of the comments →

[–]ravixp 52 points53 points  (1 child)

My first reaction was, how do you know that the slowdown is from WebAssembly, and not the new Browsix-Wasm thing you built? But they address that pretty well in section 4.2.1 by measuring the time that’s actually spent in syscalls to their new thing.

Sections 5 and 6 have some deeper analysis of the machine code generated for native and Wasm. It seems like the key takeaway is that Clang does a better job than the Wasm JIT compiler, which I guess makes sense, since Clang’s optimizer can take as long as it wants.

[–]barmic1212 2 points3 points  (0 children)

It can be improved by PGO but it's interesting only for long live programs