[Question] Communication between main thread and Web Worker about react-360 HOT 4 CLOSED

Hey @axemclion,
You're right that in many cases (excluding Edge and Safari), stringify-then-post is faster than posting a POJO. I've been intending to clean up some of the bridge code to do exactly this, as well as some explicit measurement of time spent across the bridge. Mostly, the code is the way it is right now because some of it is yanked from RN, some of it was written to add some of our needs, and in general we've been pushing for functionality over perf until we reach the full public release. But thanks for bringing this up! I believe stringifying the body will bring some real perf improvements.

from react-360.

Thanks for the response !! I have been playing with React Web-Worker Performance for a while and have recently started diving into react-vr, primarily because of the web-worker design.

Is the perf work you are doing available somewhere to take a look at ?

I am using the infamous DBMonster as a perf benchmark. Will report back on any findings I have. Some other related questions

1. Is there a better performance benchmark application that I should instead use ? I am looking to write an automated performance monitor
2. The react-vr-web project is not yet open sourced, and I simply pulled out node_modules/react-vr-web and am modifying that. Is that a good starting point ?
3. I see that the operations currently are added to a queue, and then processed during every requestAnimation frame. Is that set in stone, or would exploring alternatives there make sense ?

from react-360.

Looks like we don't need JSON.stirngify hacks anymore - https://bugs.chromium.org/p/chromium/issues/detail?id=148757#c165

from react-360.

If someone is looking for help I have created simple module that makes communication between "Web Worker" and "Main Thread" easy :)
https://github.com/venits/react-vr-bridge

from react-360.