Wasmer Backend#3
Conversation
|
For reference, I backported the wasm benchmark to the main branch and ran it. Results are insane. Before is wasmer, after is wasmi. The overhead of wasmer + setting up web workers is currently like +50%, which isn't great. But the compute-limited performance is actually incredible. A 5.5k% increase? Wow, I clearly need to stick with this and make it work. |
|
Another thing - on native:
And in WASM:
The compute is taking ~10ms in either case. There's just a 40ms startup cost in the wasm benchmark. Let's hope we can reduce that. |
Rename bridge to Runtime Create proper runtime lifecycle Refactor wasm runtime
|
Continued improvements. Not as much as I would have liked, but definitely acceptable. Still ~3x wasmi's lightning-fast startup times. It honestly might be worthwhile having both runtimes. But 20ms isn't that long, so maybe not. Think now I'm done and will try this in tlock to see how the revm plugin behaves, plus make sure there aren't any integration issues (didn't change up the API too much I think?). |
Uh oh!
There was an error while loading. Please reload this page.