You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Since the most performance intensive parts of the library on larger scales will be the Canvas parts, a lot of performance could be gained by moving those parts into a WebWorker rendering to an OffscreenCanvas. Especially any larger graphs which currently block the main thread would no longer cause the site itself to block.
Describe the solution you'd like
A new option while instantiating the graph object, which would either:
cause the library to spawn a WebWorker for the actual rendering, and transfer control to that (would have to spawn worker)
allow the user to supply an OffscreenCanvas as well as a message mechanism between WebWorker and main thread instances (would rely on user spawning worker)
Describe alternatives you've considered
/
Additional context
Since you probably don't want to proxy all events to the Web Worker, splitting the rendering would be the easier way, although it would require mirroring the node state.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Since the most performance intensive parts of the library on larger scales will be the
Canvas
parts, a lot of performance could be gained by moving those parts into aWebWorker
rendering to anOffscreenCanvas
. Especially any larger graphs which currently block the main thread would no longer cause the site itself to block.Describe the solution you'd like
A new option while instantiating the graph object, which would either:
WebWorker
for the actual rendering, and transfer control to that (would have to spawn worker)OffscreenCanvas
as well as a message mechanism betweenWebWorker
and main thread instances (would rely on user spawning worker)Describe alternatives you've considered
/
Additional context
Since you probably don't want to proxy all events to the Web Worker, splitting the rendering would be the easier way, although it would require mirroring the node state.
The text was updated successfully, but these errors were encountered: