⚡️ Speed up function find_last_node by 15,068%
#248
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.
📄 15,068% (150.68x) speedup for
find_last_nodeinsrc/algorithms/graph.py⏱️ Runtime :
39.6 milliseconds→261 microseconds(best of250runs)📝 Explanation and details
The optimized code achieves a 150x speedup by eliminating redundant computation through two key optimizations:
Primary Optimization: Set-based Lookup
The original code uses a nested loop structure: for each node, it checks
all(e["source"] != n["id"] for e in edges), resulting in O(n × m) comparisons where n is the number of nodes and m is the number of edges. This means for a graph with 500 nodes and 499 edges, the original code performs up to 249,500 comparisons.The optimized version pre-computes a set of all source IDs (
source_ids = {e["source"] for e in edges}), reducing the complexity to O(m + n). Set membership testing (n["id"] not in source_ids) is O(1) average case, dramatically faster than iterating through all edges for each node.Secondary Optimization: Early Return for Empty Edges
When there are no edges, the optimized code short-circuits with
if not edges: return next((n for n in nodes), None), avoiding unnecessary set construction and dictionary access operations. This provides modest gains in edge cases (75-94% faster in single-node scenarios).Impact Analysis
The performance gains scale with graph size:
The optimization is particularly effective for:
The behavior remains identical for all valid inputs, preserving the "first match" semantics when multiple sink nodes exist and correctly handling edge cases like mixed ID types, disconnected components, and missing node references in edges.
✅ Correctness verification report:
🌀 Click to see Generated Regression Tests
To edit these changes
git checkout codeflash/optimize-find_last_node-mk3lyl05and push.