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
Basically any plot longer than 3 days is unusable, it least with Chrome on Mac. Part of the problem may be the increasing price volatility which creates more data to be plotted, but I suspected it could be related to this bug as well: novus/nvd3#691
Perhaps updating to more modern versions of nvd3 and d3 would fix, or at least improve, things as an easy fix. Also, it seems like the Voronoi feature is pretty heavy-weight, so perhaps an option could be provided to turn it off chart.useVoronoi(false).
The text was updated successfully, but these errors were encountered:
I looked into this a little bit more and it looks like AdBlockPro was part of the problem, but there's definitely a problem with the Voronoi diagram.
One test (8 days, I think) broke down as:
14 sec. - fetch from server
2 sec. - render chart
6 sec. - update interactive layer (Voronoi)
11 sec. - ABP filter processing (!!)
But turning off ABP and going up to 30 days showed there's some kind of O(n^2) action going on with the Voronio diagram:
20 sec. - fetch
6 sec. - render
3 sec. - D3 timer flush (??)
4.9 min - update interactive layer (!!) - 4.8 min. of which is in d3.geom.voronoi
The Voronoi based interaction layer is a nice UX addition, but I'd happily give it up to get back 5 minutes every time I wanted to plot a chart.
tfmorris
added a commit
to tfmorris/ec2price
that referenced
this issue
Apr 27, 2016
While nice from a UX point of view, it's a CPU & memory hog for large numbers. With it off, hover still works, but only when you're directly over the point, rather than in the neighborhood (Voronoi region).
Basically any plot longer than 3 days is unusable, it least with Chrome on Mac. Part of the problem may be the increasing price volatility which creates more data to be plotted, but I suspected it could be related to this bug as well: novus/nvd3#691
Perhaps updating to more modern versions of nvd3 and d3 would fix, or at least improve, things as an easy fix. Also, it seems like the Voronoi feature is pretty heavy-weight, so perhaps an option could be provided to turn it off
chart.useVoronoi(false)
.The text was updated successfully, but these errors were encountered: