search

dc-js / dc.graph.js

interactive network visualization
Apache License 2.0
98 stars 24 forks source link

timeline is churning #46

Open gordonwoodhull opened 8 years ago

gordonwoodhull commented 8 years ago

When there's a ton of data points in the vizgems viewer, the timeline eats 100% cpu in ticks.each.

Isn't there a better way to do hierarchical binds?

gordonwoodhull commented 8 years ago

This is actually the bottleneck - the viewer could be flying through unchanged data at least twice as fast if it weren't for this.

gordonwoodhull commented 8 years ago

82eda67e105d8c333a64e7e4646c861ab1a3b863 and 37787b5b40cb6cb9462e77c43e67d83905a88527 help a little bit, but there really needs to be less DOM objects - when there are 3500 data points, that is 7000 ticks and of course there are only 200 pixels to display them in so it's a complete waste.

I guess it needs to be sort of a heatmap, using alpha to count multiple data points/pixel or something.

gordonwoodhull commented 8 years ago

I'd also like it to be green-up, red-down.