⚡️ Speed up function find_last_node by 21,185%#226
Closed
codeflash-ai[bot] wants to merge 1 commit intomainfrom
Closed
⚡️ Speed up function find_last_node by 21,185%#226codeflash-ai[bot] wants to merge 1 commit intomainfrom
find_last_node by 21,185%#226codeflash-ai[bot] wants to merge 1 commit intomainfrom
Conversation
The optimized code achieves a **21,000% speedup** by eliminating a severe O(n×m) algorithmic bottleneck through pre-computing a set of source node IDs.
**Key Optimization:**
The original implementation used a nested iteration pattern:
```python
all(e["source"] != n["id"] for e in edges)
```
For each node, it checked **all edges** to verify the node wasn't a source. With `n` nodes and `m` edges, this resulted in O(n×m) comparisons—catastrophic for larger graphs.
The optimized version pre-computes a hash set of source IDs once:
```python
sources = {e["source"] for e in edges}
return next((n for n in nodes if n["id"] not in sources), None)
```
This reduces the algorithm to O(m + n):
- **O(m)** to build the `sources` set (one pass through edges)
- **O(n)** for the lookup loop, with O(1) average-case hash set membership checks
**Why This Works:**
Python's set implementation uses hash tables, providing constant-time lookups versus the linear scan required by `all()`. The line profiler shows the dramatic impact:
- **Original:** 697ms total, all spent in the nested iteration
- **Optimized:** 707μs total (321μs building set, 386μs finding node)
**Performance Characteristics:**
The optimization excels particularly on large graphs:
- **Large linear chain (1000 nodes):** 19.5ms → 98μs (19,822% faster)
- **Large cycle graph (1000 nodes):** 19.7ms → 98.9μs (19,851% faster)
Small graphs show modest improvements (30-95% faster) since overhead is dominated by Python's interpreter rather than the algorithm. The only slight regression is empty inputs (9-23% slower) where set creation overhead isn't amortized, but this is negligible at sub-microsecond scales.
**Impact:** If `find_last_node` is called in graph processing pipelines or hot paths, this optimization will dramatically reduce execution time, especially for graphs with hundreds or thousands of nodes/edges.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📄 21,185% (211.85x) speedup for
find_last_nodeinsrc/algorithms/graph.py⏱️ Runtime :
93.7 milliseconds→440 microseconds(best of250runs)📝 Explanation and details
The optimized code achieves a 21,000% speedup by eliminating a severe O(n×m) algorithmic bottleneck through pre-computing a set of source node IDs.
Key Optimization:
The original implementation used a nested iteration pattern:
For each node, it checked all edges to verify the node wasn't a source. With
nnodes andmedges, this resulted in O(n×m) comparisons—catastrophic for larger graphs.The optimized version pre-computes a hash set of source IDs once:
This reduces the algorithm to O(m + n):
sourcesset (one pass through edges)Why This Works:
Python's set implementation uses hash tables, providing constant-time lookups versus the linear scan required by
all(). The line profiler shows the dramatic impact:Performance Characteristics:
The optimization excels particularly on large graphs:
Small graphs show modest improvements (30-95% faster) since overhead is dominated by Python's interpreter rather than the algorithm. The only slight regression is empty inputs (9-23% slower) where set creation overhead isn't amortized, but this is negligible at sub-microsecond scales.
Impact: If
find_last_nodeis called in graph processing pipelines or hot paths, this optimization will dramatically reduce execution time, especially for graphs with hundreds or thousands of nodes/edges.✅ Correctness verification report:
🌀 Click to see Generated Regression Tests
To edit these changes
git checkout codeflash/optimize-find_last_node-mjmt8n0land push.