3 ms·
I spent a lot of time on those benchmarks. I think my conclusion is just that because WASM isn't a register-machine architecture, you basically have to implemen
by fwsgonzo 2y ago
I spent a lot of time on those benchmarks. I think my conclusion is just that because WASM isn't a register-machine architecture, you basically have to implement a register allocator to be really fast. wasmtime uses a complex allocator to great success. wasm3 has done it too, but it's just a basic one and it won't be able to compete with GCC or Clang. I could be wrong here, but what else is there? During my testing, it was never in question if libriscv was faster.
I used my usual benchmarks: STREAM (memory) and CoreMark (CPU).
- infogulch 2y agoPosted a few hours ago: Wasmi 0.32 performs a register-based translation which gets great benchmark results. https://news.ycombinator.com/item?id=40499130 https://news.ycombinator.com/item?id=40499130
- fwsgonzo 2y agoI saw that. Keep in mind that libriscv is 35% faster than wasm3, and it looks like wasmi is not as fast as wasm3 yet. But they are making good progress.