Takeshi Yoneda
Takeshi Yoneda
yeah that's one thing we should consider, but for now I think I would like to focus on the single thread perf and then we can return to the parallelization...
now with the current main branch, it seems like 14s~15s sec (previously 30s+) to compile your binary on my local machine @davidmdm 😎
hah yeah indeed it is unfortunate the spec doesn't specify what property should be returned. But in anyway this boils down to whether the code should be generalized to run...
fuzzing time 🏃
i think @ncruces you have a Wasm-compiled sqlite speetest right? I think that can be considered representative use case/bench of wazero. Given this is mainly interested in the Go compiler's...
feel free to reopen when ready to continue the work
turns out it's flaky - rerun succeeded
reproduced on my local m1 mac ``` ~/wazero/internal/integration_test/libsodium $ go test -bench='BenchmarkLibsodium/box_seal' -count=100 -benchtime=10x goos: darwin goarch: arm64 pkg: github.com/tetratelabs/wazero/internal/integration_test/libsodium BenchmarkLibsodium/box_seal-10 10 506911971 ns/op BenchmarkLibsodium/box_seal-10 10 504660892 ns/op BenchmarkLibsodium/box_seal-10 10...
turns out this happens with v1.7.0 as well, so the bug might have existed in the first place
maybe next is to see if this will happen with interpreter or amd64, but I have no cycle right now