Debug LiveShare SDK getting slower and slower #143
Unanswered
rfjschouten
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have been using the InkingManager and the LiveCanvas from the @microsoft/live-share-canvas during the hack project. The LiveCanvas is stored in the Fluid Relay in the initialObjects. One of the things I have noticed, when you start inking (in local debug) and close the debugger and do this debugging and stopping over and over the performance is getting worse. It looks like the Fluid remembers every Inking action and when you start a new debug session, it goes through all these actions and in the end you see your previous state of the canvas. When I perform a clean action on the InkingManager, before I close the debugging session, it looks like this is not the case anymore. Is it true that all inking actions are stored in the Fluid and starting the App is going through all these actions? I have had situations, the App became really slow to start and it took really long to show the latest canvas state.
In my opinion it would be good to only have the latest state of the Canvas stored. I doubt this is the case at the moment. Could someone give more insights on this?
Beta Was this translation helpful? Give feedback.
All reactions