Hello, I'm hoping for some help with a Go WASM project I am working on.
The project is based on another project of mine, which runs very well and I have no concerns about its performance. The WASM project however performs poorly. The help I need is to determine whether the performance of the WASM version can be improved. I apologise in advance if this is an inappropriate topic for this mailing list, but I think it presents an interesting case study. The main project is an Atari 2600 emulator and located on github: https://github.com/JetSetIlly/Gopher2600 The WASM project is also on Github: https://github.com/JetSetIlly/Gopher2600-Utils The ebiten_test directory is the WASM project. It uses the core of the main project to load and display a running Atari ROM file. When compiled natively, this ebiten program performs well. However the WASM targeted compilation of the same ebiten project is significantly slower. On my hardware, the comparative performance is more than 60 FPS for the native version and less than 10 FPS for the WASM version. My questions are: Is such a performance drop expected in a WASM project? How can I analyse the performance of the WASM program? I have used Go profiling to identify bottlenecks but how do I do something similar for WASM? As you can tell, I am all at sea when it comes to modern web development so any help and advice would be much appreciated. Regards Stephen -- 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/57da7e15-0126-438f-82e0-d59ac882e3den%40googlegroups.com.
