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

Improve responsiveness when hovering over many points #10234

Closed
MarcSkovMadsen opened this issue Jun 27, 2020 · 1 comment · Fixed by #10237
Closed

Improve responsiveness when hovering over many points #10234

MarcSkovMadsen opened this issue Jun 27, 2020 · 1 comment · Fixed by #10237

Comments

@MarcSkovMadsen
Copy link
Contributor

MarcSkovMadsen commented Jun 27, 2020

My Pain

I would like to use Bokeh plots in my applications but sometimes they feel slow and sluggish.

An example of this is plots with many points. The many points by them selves is not the main problem. The main problem is hovering.

If the users hovers over the Bokeh plot it becomes unresponsive and my fan turns on.

I suspect its due to collecting and showing tool tips for many points

My fear is that my users turn away from my apps because they appear slow or dead.

Example

https://ferret.pmel.noaa.gov/osmc/dashboard

I hover and the drag the plot. The first time its OK responsive. The second time it takes 10 secs before the plot moves.

bokeh-slow

Another Example

Its the same problem at awesome-panel.org in the Kickstarter Dashboard. If I want to select some points to filter on the hovering often steps in first and I have to wait 5-10 secs for the plot to respond.

image

Solution

Fix this :-) For example by

  • fixing the cause if there is a cause or
  • setting a max on the number of points to show hover information for.

FYI @philippjfr

@mattpap
Copy link
Contributor

mattpap commented Jun 27, 2020

https://ferret.pmel.noaa.gov/osmc/dashboard

For me it hangs as soons I attempt to use the hover tool. Hover tool/Tooltips are currently extremely inefficient, primarily due to inefficient manipulation of DOM nodes. When that's solved, we will be able to look into further optimizations, e.g. doing computations off main thread.

setting a max on the number of points to show hover information for.

Various policies, like limiting the number of entries showed, were supposed to be implemented for awhile now (issue #9087).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants