It all depends on how you use it. Cytoscape.js supports lots of features, and especially some of the visual styles can be expensive. There are some notes in the documentation on this (e.g. use haystack edges):
Certainly you can visualise thousands of nodes if you use performant options and your code itself is performant. On my machine with v2.2.x I’ve tuned the options to get 8000-10,000 elements on screen, but that was the limit before performance was a problem. The upcoming v2.3.x and onward will continue to have better and better performance (and more features too).
If you were to try to visualise the graph with SVG or the DOM, you’d run into performance problems much sooner — so be careful what technology you use.
Angular 1.x tends to be able to handle on the order of 2000-4000 model elements (not necessarily graph elements) before its performance becomes an issue. Angular 2.x should have better performance, but we’ll have to wait and see.
Whether users will understand large graphs is another question. That can be addressed with use of layout, extensions/plugins (to focus on subsets of the graph at a time), and what elements your app itself puts in the graph at any one time. It’s a complicated problem.
-Max
Attachments: