⚡️ Speed up function find_last_node by 22,757%
#235
+2
−1
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.
📄 22,757% (227.57x) speedup for
find_last_nodeinsrc/algorithms/graph.py⏱️ Runtime :
78.6 milliseconds→344 microseconds(best of250runs)📝 Explanation and details
The optimized code achieves a 228x speedup (from 78.6ms to 344μs) by eliminating a quadratic nested loop pattern.
Key optimization:
Why this matters:
Python's
setlookup using hash tables is extremely fast (O(1) average case), while the originalall()with a generator expression must scan through every edge for each node. The performance gap widens dramatically as the graph grows:Test case performance patterns:
Impact considerations:
The optimization is most beneficial when:
The tradeoff is minimal: a tiny overhead for empty graphs (which complete in <1μs anyway) in exchange for massive gains on any non-trivial graph structure.
✅ Correctness verification report:
🌀 Click to see Generated Regression Tests
To edit these changes
git checkout codeflash/optimize-find_last_node-mjnk1u1rand push.