@@nikolauswest1306 I see, so the 6k graph shown in the video is roughly the maximum graph size we can reasonably expect to perform at interactive rates?
@@ChrisOffner That's roughly the size that stays nice to use if the graph is changing dynamically and we're constantly running the simulation. If you only run the simulation once (or never) it can handle much bigger graphs but we haven't benchmarked that yet seriously since that wasn't the focus of this release
I ran this code to compute conjecture tree. pretty cool stuff!!
Looks really cool! How many nodes can a graph handle and retain interactive frame-rates on, e.g., MacBook hardware?
We've tried a 6k nodes graph on MacBook hardware that retains interactive rates including the simulation based layout
@@nikolauswest1306 I see, so the 6k graph shown in the video is roughly the maximum graph size we can reasonably expect to perform at interactive rates?
@@ChrisOffner That's roughly the size that stays nice to use if the graph is changing dynamically and we're constantly running the simulation. If you only run the simulation once (or never) it can handle much bigger graphs but we haven't benchmarked that yet seriously since that wasn't the focus of this release