⚡️ Speed up function find_last_node
by 23,284%
#10
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.
📄 23,284% (232.84x) speedup for
find_last_node
insrc/dsa/nodes.py
⏱️ Runtime :
210 milliseconds
→899 microseconds
(best of125
runs)📝 Explanation and details
Here’s a much faster version. The original code checks each node against every edge in a nested loop (O(N*M)), which is expensive.
The optimization is to first build a set of all sources in
edges
, then simply find the first node whose ID is not in this set (O(N+M)).This reduces the complexity from O(N*M) to O(N+M) and yields the exact same results. All comments are preserved as requested.
✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-find_last_node-map1nt8f
and push.