Benchmarking wazero #9
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a benchmark for Wazero.
Now I am not sure if the comparison is 100% correct, because wasm is lower level, and would require some additional boilerplate to pass or receive arguments other than integers or floats (which btw is feasible via https://github.com/knqyf263/go-plugin, but it's using protocol buffers).
But I was interested in having a rough idea of the performance anyway.
I originally planned to compare it to wasmer-go, wasmtime-go and wasmedge, but I could not get those to work.
At the moment, the native go compiler only provides
//go:wasmimport
directives and no//go:wasmexport
, which makes it unusable withGOARCH=wasm
(hence the need for tinygo). But once it does in the future, it would be nice to have the same benchmark for both compilers.Results on my computer (I did not update the readme because I am not sure what was the referential for the benchmark there):