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
In order to improve performance and allow server-side rendering to work properly, we must implement batch-rendering.
Today, the implementation of this component strictly follow the APIs from HTML5 Canvas where each call actually draw something.
We need to experiment and implement an optimization that batch render requests to it will only invoke JS APIs (local or remote) in a batch to avoid multiple (unnecessary) serialization and interop calls happen.
The text was updated successfully, but these errors were encountered:
What this means is that we need to have a list that saves the method calls until either the last batch call completed or until an update method is called and then pass that list to a javascript function what will call all of them. That's how I would have done it atleast.
Yes. Right after we finish your WebGL PR, we need to tackle this one. Particularly enabling async methods so the server side blazor can work as well...
In order to improve performance and allow server-side rendering to work properly, we must implement batch-rendering.
Today, the implementation of this component strictly follow the APIs from HTML5 Canvas where each call actually draw something.
We need to experiment and implement an optimization that batch render requests to it will only invoke JS APIs (local or remote) in a batch to avoid multiple (unnecessary) serialization and interop calls happen.
The text was updated successfully, but these errors were encountered: