Improve performance of bfs functions #250
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added an optimization to these bfs functions which I benchmarked with
and then I calculated the relative speed-up for the graphs in
gsbefore and after this pr:gdistances! bfs_parents 0.99 0.99 --> path_graph(500) 0.98 0.99 --> path_graph(5000) 0.99 1.00 --> path_graph(50000) 3.18 3.14 --> erdos_renyi(50, 0.5, seed=123) 16.91 15.42 --> erdos_renyi(500, 0.5, seed=123) 126.52 120.08 --> erdos_renyi(5000, 0.5, seed=123) 5.40 5.19 --> complete_graph(50) 46.14 40.11 --> complete_graph(500) 512.26 475.42 --> complete_graph(5000)The Path Graph is kind of the worst case scenario, and the time is approximately equal to the algorithm before this pr, but, as you can see, with a well connected Erdos Renyi the speed-up becomes very good, and finally I choose to benchmark a Complete Graph since it should be the best case scenario.
I also ran the tests locally and everything should still work!