Performance worse on v2 when panning & updating ui on js thread? #1753
Unanswered
jstheoriginal
asked this question in
Q&A
Replies: 1 comment
-
Here's some comparison videos: using v1 apis Screen.Recording.2021-12-07.at.1.02.31.PM.movusing v2 apis Screen.Recording.2021-12-07.at.12.31.44.PM.mov |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using this pan gesture code to update a value in a d3.js chart based on where the user is touching during the pan, so the selection tooltip can be positioned correctly.
When I did this on v1, performance was great. Now that I've changed it over to v2, the JS thread goes down to 0 fps and there's bad lag in the js code that reacts to the onUpdate. Based on examples in this repo, this seems to be the way to use the new api.
Am I doing this correctly? If not, how would one properly update something elsewhere in code that doesn't use reanimated & just gets drawn with svgs (like d3.js charts)?
Beta Was this translation helpful? Give feedback.
All reactions