Could you explain a bit more about what you're comparing? - Is the wasm version running in a browser? If so, which one? Or have you got a way to run wasm directly on the host (in which case, what is it)? - How is the linux/amd64 version running, if it's not talking to a DOM-type environment? If the native version is still using syscall/js, then how is it doing so? Or is the native version in a different repo? - By "the parent emulator project" do you just mean web2600 itself? On Friday, 3 September 2021 at 09:19:07 UTC+1 stephen.t....@gmail.com wrote:
> Hello, > > I have a moderately large Go project that performs fine on my development > machine. However when compiled for WASM the performance drops off > significantly. I'm hoping someone can help me understand why. > > For comparison purposes, on my hardware, the emulator will run uncapped at > a 110-120fps when compiled for linux/amd64 but the wasm/js binary runs at > maybe 10fps. > > This is the project on Github > > https://github.com/JetSetIlly/Gopher2600-Utils/tree/master/web2600 > > The only direct module requirement is the parent emulator project. The > indirect requirements listed in go.mod aren't being used. > > I've only done the barest minimum to get the WASM version working and in > fact know very little about WASM. It's more a proof of concept that > anything else, but it would be nice to get it performing well. > > Regards > > Stephen Illingworth > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/f8f2e3b9-4189-4e4e-8d4d-a871ec3e30b7n%40googlegroups.com.
