-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
scrollZoom performance issues introduced in 2.3.0 #5912
Comments
Thanks for the report & beautiful demo. |
Thanks for the quick reply @archmoj, much appreciated! I've tried setting the Excited I've applied this to my actual project code but sadly it did almost nothing in terms of performance improvement. After spending a few hours on trying to extract the minimum example that would still trigger the issue from our production code, this is what I've came up with: Demo: https://codesandbox.io/s/plotly2-performance-drop-demo-tickvals-1t424 Steps to reproduce:
Unlike the |
I can replicate this slowdown with the sample provided, thanks very much! @archmoj are you able to replicate also? |
Related to #5584. |
@archmoj adding I will put more testing on that and report back if I find more related issues/details, but for now I think I am happy with using these additional configuration parameters you've pointed out. |
Closing. Please feel free to reopen or open a new issue if you encountered a new one. |
I'm not sure if i can reopen the issue, let's see if it happens automatically with this comment, if not I'll open a new one and link to here. (UPD: reopened as #6054) So not all the issues are fixed with those flags you have suggested above. |
There is a significant performance drop when using scroll zoom in version
2.3.0
and newerLatest version with better performance is
2.2.1
Demo: https://codesandbox.io/s/plotly2-performance-drop-iinx5
Steps to reproduce:
plotly.js-dist
dependency version (in the dependencies section of the toolbar on the left) from2.3.0
to2.2.1
and test the scroll zoom againThe text was updated successfully, but these errors were encountered: