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

Performance improvements to canvas heatmap implementation #559

Closed
aashish24 opened this issue Apr 15, 2016 · 3 comments
Closed

Performance improvements to canvas heatmap implementation #559

aashish24 opened this issue Apr 15, 2016 · 3 comments
Assignees
Labels

Comments

@aashish24
Copy link
Member

Currently the heatmap implementation using canvas2D API does not scale and has very poor framerate even with smaller size datasets.

@aashish24
Copy link
Member Author

aashish24 commented Apr 15, 2016

From @jbeezley

You can apply scale transform to simulate zooming. Yes, it is not the same thing as rerendering, but it makes for an acceptable visual substitute. The behavior that leaflet exhibits is that all animated navigations (zoom and pan) are simulated by CSS transforms. Once the animation is finished the debounced call to rerender the canvas is made.

@aashish24
Copy link
Member Author

@jbeezley some other ideas:

  • Render a coarser resolution (either at the data level or at the rendering level) - need to verify if this will really help (this is a very common vis technique).
  • Render only when user has stopped panning or zooming. (or combine it with css transformations) like @jbeezley suggested.

@manthey
Copy link
Contributor

manthey commented May 18, 2016

Added via PR #574 and #577.

@manthey manthey closed this as completed May 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants