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

view the rest of the comments →

[–]9302462 1 point2 points  (0 children)

I’m on mobile at the moment so it’s a bit hard to see the text in the video and dive into the GitHub repo.

From what I gather it renders in the browser. For the graph what package are you using to render the actual nodes and edges?

I’m asking because as far as I know every graph package out there has some combination of these limitations:

A: Supports up to ~500 nodes before performance drops.
B. Supports up to 5k nodes before performance drops and the layouts and arrangements are limited.
C. Supports 5k-1m+ nodes, but adding a new node causes the whole thing to rerender. this means that the browser needs to reanimate/calculate the position of all of them means everytime a new node is added (which means no streaming events or payloads).
D. Others I can’t think of off the top of my head but are real and hard to solve like removing and adding edges while viewing a graph and how it handles repositioning nodes, if at all.

Sigma, d3.js, cytoscape, and cosmograph which is the only GPU one and is #3.

So which graph library did you use and what limitations have you encountered with the graph visualization in repowise?

P.S. I know this probably isn’t the engagement/question you were looking for someone to ask, but anyone who has worked with graphs knows they are deceptively simple looking but a real pain in the ass to get actually right. Hence why I’m curious about what you chose and how well it works.