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
Hi, I've noticed that the NetworKit shortest-path benchmark is executed with
distance.BFS(g, node_index).run()
However, with this API NetworKit will also store all shortest paths from node_index to all the other nodes, which implies a significant memory and time overhead. This behavior is a bit counterintuitive, and should be better documented, one does not expect BFS to store by default all shortest paths.
Since the other tools only compute the shortest distances, for a fair comparison you should run this:
Hi, I've noticed that the NetworKit shortest-path benchmark is executed with
However, with this API NetworKit will also store all shortest paths from
node_index
to all the other nodes, which implies a significant memory and time overhead. This behavior is a bit counterintuitive, and should be better documented, one does not expect BFS to store by default all shortest paths.Since the other tools only compute the shortest distances, for a fair comparison you should run this:
The text was updated successfully, but these errors were encountered: