5 ms·
To wit, as described in their blog post: https://blogs.windows.com/msedgedev/2017/04/20/improved- https://blogs.windows.com/msedgedev/2017/04/20/improved- Edg
by luke_wagner 9y ago
To wit, as described in their blog post:
https://blogs.windows.com/msedgedev/2017/04/20/improved- https://blogs.windows.com/msedgedev/2017/04/20/improved-
Edge validates and compiles wasm code lazily. Thus, this simplistic benchmark isn't really measuring compile time on Edge. In contrast, Firefox, Chrome and Safari are doing some amount of AOT compilation before WebAssembly.instantiate() resolves.
- ehsankia 9y agoHere's a stupid question, but is the result of the Firefox and Chrome "instantiate" the exact same? Is the compilation doing the same job, or one could be performing more optimizations? Aka faster compilation but slower execution.
- computerphage 9y agoThey're doing slightly different things, but not to nearly the extent of Edge which is doing something very different.