You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Constellation can handle a million nodes with high end graphics cards. If we want to push the limits and get to multi-million nodes with ease, can we use the depth of field to our advantage? That is, nodes that are further away into the distance should reduce the load on the graphics card.
Presently, labels render when they are closer to you and disappear when you zoom out. Could something similar be done with nodes and transactions whereby when you zoom out a lot and nodes are on top of one another, less nodes are actually rendered and therefore graph load time and interaction can improve dramatically.
Steps to Reproduce
Open a new graph
Experimental -> Build Graph -> Sphere Graph and set to 1,000 nodes and 1,000 transactions
Click OK
Save the graph
Close the graph
Open the graph and notice the time it takes to load the graph
Zoom out a lot so you see a tiny node, which is barely visible
Save the graph
Close the graph
Open the graph and notice the time it takes to load the graph
Expected behaviour:
The load time should be considerably quicker in step 10 compared to step 6
Actual behaviour:
The load times are the same regardless of how many nodes are visible.
Reproduces how often:
100%
The text was updated successfully, but these errors were encountered:
Prerequisites
Help
>Support Package
Description
Constellation can handle a million nodes with high end graphics cards. If we want to push the limits and get to multi-million nodes with ease, can we use the depth of field to our advantage? That is, nodes that are further away into the distance should reduce the load on the graphics card.
Presently, labels render when they are closer to you and disappear when you zoom out. Could something similar be done with nodes and transactions whereby when you zoom out a lot and nodes are on top of one another, less nodes are actually rendered and therefore graph load time and interaction can improve dramatically.
Steps to Reproduce
Expected behaviour:
The load time should be considerably quicker in step 10 compared to step 6
Actual behaviour:
The load times are the same regardless of how many nodes are visible.
Reproduces how often:
100%
The text was updated successfully, but these errors were encountered: