⚡️ Speed up function find_node_with_highest_degree by 3,914%
#15
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.
📄 3,914% (39.14x) speedup for
find_node_with_highest_degreeinsrc/dsa/nodes.py⏱️ Runtime :
42.2 milliseconds→1.05 milliseconds(best of1092runs)📝 Explanation and details
Here is a rewritten version for improved speed.
Optimizations applied:
connections, avoiding checking all nodes in all targets for every node (O(N+E) instead of O(N^2) time).✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-find_node_with_highest_degree-mb8doay0and push.