3 ms·
Faster than native? So, WebAssembly has achieved what Java tried to sell us since it's inception?
by k__ 4y ago
Faster than native?
So, WebAssembly has achieved what Java tried to sell us since it's inception?
- egberts1 4y agoYeah, basically by bypassing the OS VM memory switching/context-switch with their own brand of memory-switching/context-switching, but with one notable difference: stackless internal representation (IR) bytecodes. Can we open up a new class of vulnerabilities in Mitre?
- k__ 4y agoCould operating systems use this technique to speed up things?
- dahfizz 4y agoWe already have things like io_uring to achieve this speedup. As usual, this benchmark is comparing against an extremely naive implementation. It even uses a non-optimizing compiler! A fair benchmark would take advantage of all the features that native code has available - huge pages, CPU acceleration, io_uring, and, most obviously, a compiler that supports -O2. If they did that, the native code would smoke wasm.
- AnIdiotOnTheNet 4y agoTo be fair, almost any JIT VM is capable of being "faster than native" (by which is meant pure AoT) in some circumstances because it has more information on the environment and circumstances of execution.
- k__ 4y agoThat's what I'm reading since the first release of Java. Still, C/C++ and Rust are running circles around it.