3 ms·
Still not big, but a bit bigger: https://gransk.com/ggraph-bigger.html https://gransk.com/ggraph-bigger.html (Nodes: 611 Edges: 2499) Edit: It's an excerpt of
by pcbje 10y ago
Still not big, but a bit bigger: https://gransk.com/ggraph-bigger.html https://gransk.com/ggraph-bigger.html (Nodes: 611 Edges: 2499)
Edit: It's an excerpt of the Enron dataset.
- pcbje 10y agoTo merge nodes based on search results and min-edit distance is currently not included, but probably will be quite soon.
- nkoren 10y agoThanks, that really helps. It's getting noticeably laggy for me at 611 nodes, but below you say it shouldn't be a problem to do 5k. Have you actually tested that kind of data?
- pcbje 10y agoYes. Animating node placement has a significant performance penalty, so in larger graphs you would either hide edges or everything during the first couple of seconds.
- Bedon292 10y agoLike you said, still not big and its starting to get laggy. Do you have an example that actually is big and not laggy?
- pcbje 10y agoAre you referring to node placement or selection/merging? Node placement is done with D3 force directed layout, so I don't think I'll be able to do much there. And again, animation makes it more soggy.
- jwr 10y agoThanks, I had the same question and you answered it nicely — I will stick with Vis.js (http://visjs.org/network_examples.html http://visjs.org/network_examples.html) for now. It seems to work better for larger graphs and allows me to build a pretty good ui for exploring the graph, too.