You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More of a question than a bug report. There is a significant performance regression from 2.7.3 -> 2.8.0 in situations with lots of data points. It seems to be related to _resolvePointOptions in updateElement.
Codepens demonstrating the performance difference:
(the y-value of the top trace is based on the time taken to update the graph).
A more general question: Is there a more performant route for displaying homogenous, data-heavy traces? (such as a line with 1000 points, all with the exact same properties, other than position)
edit: master is a bit better, but still slower than 2.7.3 in this case, and about 40% of the time appears to be spent in _resolveDataElementOptions.
The text was updated successfully, but these errors were encountered:
More of a question than a bug report. There is a significant performance regression from 2.7.3 -> 2.8.0 in situations with lots of data points. It seems to be related to
_resolvePointOptions
inupdateElement
.Codepens demonstrating the performance difference:
2.7.3
2.8.0
(the y-value of the top trace is based on the time taken to update the graph).
A more general question: Is there a more performant route for displaying homogenous, data-heavy traces? (such as a line with 1000 points, all with the exact same properties, other than position)
edit: master is a bit better, but still slower than 2.7.3 in this case, and about 40% of the time appears to be spent in
_resolveDataElementOptions
.The text was updated successfully, but these errors were encountered: