Hi!
I noticed that compiling an 8 MiB WASM module (produced by the experimental WASI SDK for .NET) when using Wasmtime from commit 28cf995 (current dev release) takes much longer than when using Wasmtime 3.0.0 (tested on Windows 10 x64, Build 19044).
To reproduce:
On my system, with Wasmtime 3.0.0 this takes about 0.7 seconds, but with the build from commit 28cf995 it takes about 13.8 seconds, which is about 20 times as long.
Is this expected?
Bisecting shows that this starts to appear with commit fc62d4a (#5231) - with a release build from this commit, I get the 13.8s time, but with the previous commit 33a1925, I get a time of about 0.7s.
Versions and Environment
Wasmtime version or commit: Wasmtime v3.0.0 vs 28cf995
Operating system: Windows 10 Pro x64, Build 19044
Architecture: x64 (x86-64)
Thank you!
Hi!
I noticed that compiling an 8 MiB WASM module (produced by the experimental WASI SDK for .NET) when using Wasmtime from commit 28cf995 (current dev release) takes much longer than when using Wasmtime 3.0.0 (tested on Windows 10 x64, Build 19044).
To reproduce:
.movfile to.zip; I renamed it to be able to upload it here): https://user-images.githubusercontent.com/13289184/203989968-4639d6d5-15c9-4e57-bf01-c2eccd756642.movwasmtime-v3.0.0-x86_64-windows.zipwasmtime compile dotnet-codabix-wasm-build.wasmOn my system, with Wasmtime 3.0.0 this takes about 0.7 seconds, but with the build from commit 28cf995 it takes about 13.8 seconds, which is about 20 times as long.
Is this expected?
Bisecting shows that this starts to appear with commit fc62d4a (#5231) - with a release build from this commit, I get the 13.8s time, but with the previous commit 33a1925, I get a time of about 0.7s.
Versions and Environment
Wasmtime version or commit: Wasmtime v3.0.0 vs 28cf995
Operating system: Windows 10 Pro x64, Build 19044
Architecture: x64 (x86-64)
Thank you!