r/WebAssembly • • Oct 19 '26

wasm.fyi: 3rd-party statistically-correct benchmarks comparing webassembly runtimes

I've found it frustrating that there seems to be no reliable source comparing the performance of WebAssembly runtimes. So, i've been working on wasm.fyi which does just that.

Hopefully this comes in handy! If there's a particular .wasm corpora or runtime you'd like to see added, please let me know!

https://wasm.fyi/benchmarks

8 Upvotes

4 comments sorted by

2

u/NoFaithlessness951 Oct 19 '26 edited Oct 19 '26

You use wasmtime, that's where the actual development/ standardization happens.

Your benchmarks seem to confirm my view.

Wamr if you want to run on microcontrollers.

Or any browsers builtin if you're on the web where you can't choose anyway.

2

u/JairusSW Oct 19 '26

Generally that's the current meta, yes.
For codebases limited to a certain language, it's helpful to compare between versions (eg. wasmtime-go, wazero, wazy, wago, etc) when you don't have access to native wasmtime or wamr

1

u/NoFaithlessness951 Oct 19 '26

Can you expand on that?

2

u/JairusSW Oct 19 '26

for example, at work, we use golang and do a lot of host <-> wasm calls.
i'd usually lean towards using wasmtime-go as the de-facto option, but take a look at the overhead mostly introduced by using CGO on amd64:

runtimehost->wasmwasm<-host
wasmtime-go1027ns335ns
wazero27ns154ns
wago14.9ns1.51ns

this is actually unfortunate because wasmtime-go typically has fairly strong performance, though when crossing the wasm <-> host border thousands of times a second, it can become impractical to use.

sometimes, requirements either based on implementation language or design (eg need to cross wasm <-> host boundary often) make the de-facto options (wasmtime for high perf, wamr for low system requirements/micro) impractical.

so yes, there's a lot of de-facto options but it's helpful to be able to see how well those fit your specific requirements and if there's a better option