⚡️ Speed up function find_last_node by 18,963%
#220
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.
📄 18,963% (189.63x) speedup for
find_last_nodeinsrc/algorithms/graph.py⏱️ Runtime :
56.8 milliseconds→298 microseconds(best of250runs)📝 Explanation and details
The optimized code achieves a 190x speedup by eliminating a nested loop that caused O(N*M) time complexity, where N is the number of nodes and M is the number of edges.
Key optimization:
The original code used a nested iteration pattern:
For each node, it checked against every edge to see if that node was a source. This means for 1000 nodes and 999 edges, it performed ~1 million comparisons.
The optimized code preprocesses edges into a set:
Then performs a simple O(1) hash lookup:
Why this is faster:
Performance characteristics by test case:
The optimization is universally beneficial and particularly impactful when the function is called repeatedly on graphs with many nodes or edges, making it ideal for production workflows involving graph analysis or flow processing.
✅ Correctness verification report:
🌀 Click to see Generated Regression Tests
To edit these changes
git checkout codeflash/optimize-find_last_node-mjj0thsvand push.