Really weird, for a same TODOMVC react app, Chrome (101.0.4951.64) seems to be faster than Firefox (77.0.1) at handling a same DOM event (~12ms vs ~30ms). But with my implementation of the same TODOMVC app in wasm, built with Go, the same event is handled much faster in Firefox than in Chrome (~25ms vs ~50+ms). (And actually wasm event handling is slightly faster than the handling of the same event in react)
Mostly seems to me like calling into wasm has close to no overhead in Firefox. Anyone noticed something similar? Perhaps that it warrants a report. On Wednesday, June 1, 2022 at 8:51:43 PM UTC+2 atd...@gmail.com wrote: > Seems like it might be a slow handling of wasm in Chrome. Firefox is > almost twice as fast. There seems to be almost no overhead. > > On Tuesday, May 31, 2022 at 3:19:24 PM UTC+2 atd...@gmail.com wrote: > >> Hi, >> >> I am trying to optimize some wasm code that runs into the browser. >> So far, the performance is acceptable if not slightly faster than >> probably unoptimized js DOM manipulation (comparing my implementation of >> TODOMVC with the vanilla javascript one and react one) >> >> One issue I see is that triggering event handlers that calls into wasm >> seem to incur a big overhead penalty (~25ms) >> >> Any idea if this is normal and ways to alleviate it if so? (I haven.t >> tried using tinyGo yet) >> >> You can find a screenshot of the perf profile here : CDT Perf Profile >> screenshot <https://ibb.co/3SvcySG> >> >> Many thanks, >> > -- 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/d4d4d6db-e352-41b6-add7-b4ecfdf03a6an%40googlegroups.com.
