Wasmtime GitHub notifications bot (Feb 03 2021 at 20:08): Wasmtime GitHub notifications bot (Feb 03 2021 at 20:08):bjorn3 commented on Issue #85:
This issue is not actionable. In addition a lot has changed since this issue was created, so it may already be fixed.
Wasmtime GitHub notifications bot (Feb 03 2021 at 20:13):cfallin commented on Issue #85:
We've had a number of significant performance improvements since this issue was filed (most notably: new backend, with new register allocator), and while we're still not quite as fast as V8 or SpiderMonkey, we're getting closer. We're hoping to have some continuous performance measurement infrastructure working soon (bytecodealliance/rfcs#3, bytecodealliance/rfcs#4) so we should prefer that for tracking over this general issue, I think.
Wasmtime GitHub notifications bot (Feb 03 2021 at 20:13):cfallin closed Issue #85:
I've tried several simple cpu bounded benchmarks. It seems that in general wasmtime is twice slower than V8 or Spider Monkey.
Last updated: Nov 22 2024 at 17:03 UTC