-
Notifications
You must be signed in to change notification settings - Fork 278
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
Performance problem while executing the given wasm file #751
Comments
Can you please try to run the Wasm file using other interpreter based Wasm runtimes? E.g. Wasm3, WAMR classic or fast interpreter, toywasm or Wasmedge interpreter. Generally interpreters are orders of magnitude slower in execution compared to JIT compiled runtimes. The most recent |
Thanks for your reply. Actually I have tried to use some of the runtimes you mentioned to execute the same wasm file. For Wasm3, it takes about 3 minutes to output the correct checksum result, and for WasmEdge, it takes about 10 minutes with its interpreter mode. According to your suggestion, I installed the latest version Compared to other interpreter based WASM Runtimes I have used, this time is still relatively long. As for if Wasmi really has performance related problems while executing the given wasm file, it still requires you to determine. Thanks a lot. |
If Wasm3 took 3 minutes then it should take One possibility is that you installed |
@Robbepop |
Glad to hear. Can you tell me about the exact times please? :) |
It takes about 1 m 16 s. |
Thanks! Oh wow that's quite some improvement. :D |
Description
Wasmi maybe have performance problems while executing the given wasm file.
Versions and Environment
Tools version: wasmi_cli 0.30.0
Operating system: Ubuntu 22.04.1
Architecture: x86_64
Current State
It will take about 1 hour to output the correct checksum result
checksum = 93DF9E88
Expected
Extra Info
The current execution result of wasmi is correct, but it will take about 1 hour, far exceeding the time required to execute other wasm files. At the same time, using other WebAssembly runtimes, such as wasmer and wasmtime, to execute the same wasm file will take no more than 1 minute to obtain the correct execution results. Therefore, I believe that there may be
performance related problems
in wasmi, which may slow down the execution speed of the given testcase.The text was updated successfully, but these errors were encountered: