-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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 issue with live updates #699
Comments
@Neil-Bennett |
I'm getting a similar issue with an app using a 5 second interval. Strangely, the app works fine on Linux, but sometimes I never get a single update on Windows. Sometimes I'll get a "max call stack exceeded" error from the JS as well. |
Same problem here. I wonder how well the JS library handle this sort of task. |
* Update CSS for DatePickerRange vertical arrows. * Use day size to calculate vertical height. * Fix eslint error.
* Update CSS for DatePickerRange vertical arrows. * Use day size to calculate vertical height. * Fix eslint error.
Dear all,
I have noticed a performance limitation of the updated graphs when I try to implement the live updates (https://dash.plot.ly/live-updates) tutorial.
I implemented the tutorial example without changes and it works as expected, however I noticed that if I increase the number of data points the traces on the dashboard cease to display (axis is rendered but no lines/markers are visible) when the number of points is greater than approximately 2000 (I used trial and error to find values that worked).
I tried changing the figure ‘type’ parameter to ‘scattergl’, but this was ineffective. This behaviour is observed in Chrome, Firefox and internet explorer.
If I increase the update interval time to e.g 5 seconds, I can plot 10,000 data points, but this is not very satisfactory as I am trying to base my own application on this approach but I need to plot e.g 24 hours worth of data at 1 second intervals, refreshing the graph with new data every 1-2 seconds.
Is this performance limitation expected and is there a way to improve this performance?
The text was updated successfully, but these errors were encountered: