Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Batch rendering #13

Closed
galvesribeiro opened this issue Sep 26, 2018 · 2 comments · Fixed by #24
Closed

Batch rendering #13

galvesribeiro opened this issue Sep 26, 2018 · 2 comments · Fixed by #24
Assignees
Labels
enhancement New feature or request

Comments

@galvesribeiro
Copy link
Member

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.

@jorolf
Copy link
Contributor

jorolf commented Jan 15, 2019

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.

@galvesribeiro
Copy link
Member Author

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants