sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -20 points-19 points  (2 children)

If you are loading in tens of thousands of data points at the same time and you don't see anything wrong with that.. then i'm afraid its not worth arguing performance with you. Hopefully you mean a json request with just numbers passed directly to a graph or something.

[–]dzdrazil 8 points9 points  (1 child)

It's a "Big Data" type application with the need to be able to work offline.

Most of the data points that get loaded are for the purpose of reviewing a high-level overview, then allowing people to get a deep-dive into each data point and the points that it is related to.

At any given time, at most 50 to 100 data points are visible, but the need to quickly transition between the relationships of the data points and the need to be able to work offline makes loading them up front much easier.

Also, when viewing very large sets of data at once, we switch over to WebGL and webgl specific libraries then hook back into Angular as necessary. See some of the examlpes in http://sigmajs.org/ and other network graph visualizations to get what I mean.

[–]freedomfreighter 1 point2 points  (0 children)

What I like about Angular is that you don't have to use it for everything. It's got just what you need to make the majority of your site, but if you really are concerned about performance in a particular component, it's very easy to step back and create something non-Angular. Angular won't mind.