3 ms·
It's built on top D3 and has the same limits (5k nodes 20k edges should not be a big problem). The "big" here is the ability to combine nodes, for two reasons:
by pcbje 10y ago
It's built on top D3 and has the same limits (5k nodes 20k edges should not be a big problem). The "big" here is the ability to combine nodes, for two reasons:
1 Reduce the number of nodes and edges, thus increasing capacity
2 Combine nodes that should be seen together (e.g. alternative spellings and typos), to better deal with the variation-aspect of big data
I see your point, but the goal here was to illustrate the functionality.
- quickben 10y agoI don't have the time to try it right now, but can it visualize 20M-100M nodes?
- yawgmoth 10y agoWhat would the use case be? Humans can't parse that visually. At a number way lower than 20M, nodes and edges should be culled.
- pcbje 10y agoAt some point you run out of pixels on your screen to visualize it all at once. My suggestion in your case is to not use a graph at the beginning, but rather grouping nodes based on metrics. Like degree (group all contacts of a node that only has a single contact), communities, or value (e.g. IP's in a subnet).
- TuringTest 10y agoTo illustrate the functionality, the point of the original poster is a valid one. The interactions for managing 5k nodes are not necessarily the same as those for managing 10 nodes - not just in terms of performance, but also in how to make sense of all the information shown; so showing a realistic use case is required to assess the possibilities of the tool.