|Not So Quick! WebAssembly|
|Written by Ian Elliot|
|Wednesday, 30 January 2019|
A lot of hopes are pinned on the future success of WebAssembly as an alternative to native apps. Of course, for this to be true WebAssembly has to be fast. But how fast is it?
The reason for the loss of performance seems to be the way that the code is structured to use twice the number of loads and stores than equivalent native code. The researchers attribute this to the lack of registers and not making use of a wider range of x86 addressing modes. There is also the issue of larger code size, resulting in more L1 cache misses. Finally the cost of making code safe results in additional operations.
OK, this isn't really good news, but you have to remember that WebAssembly is in its infancy and this sort of information should enable implementers to improve efficiency. It might just be that WebAssembly isn't fast now, but it might be in the future. Another interesting finding is that Chrome is about 27% slower than Firefox, so providing evidence that implementation matters.
Abhinav Jangda, Bobby Powers, Arjun Guha, Emery Berger
or email your comment to: firstname.lastname@example.org
|Last Updated ( Wednesday, 30 January 2019 )|