Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wasmtime and wasmer shims are much slower in stress test benchmarks than other runtimes #860

Open
Mossaka opened this issue Feb 17, 2025 · 0 comments
Labels
question Further information is requested wasmtime Anything wasmtime shim related

Comments

@Mossaka
Copy link
Member

Mossaka commented Feb 17, 2025

The results are a bit surprising:

  • Wamr: 95 tasks/s
  • Wasmedge: 85 tasks/s
  • Wasmer: 17 tasks/s
  • Wasmtime: 16 tasks/s

The two C/C++ runtimes seem to be much faster than the two Rust runtimes.
At first I though we might be building the shim in debug mode, but IIUC the logs indicate that's not the case. I wonder if there's something else going on here.

I think we should merge this PR and investigate these results separately.

Originally posted by @jprendes in #855 (comment)

@Mossaka Mossaka added question Further information is requested wasmtime Anything wasmtime shim related labels Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested wasmtime Anything wasmtime shim related
Projects
None yet
Development

No branches or pull requests

1 participant