⚡️ Speed up function find_last_node
by 15,521%
#39
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,521% (155.21x) speedup for
find_last_node
insrc/dsa/nodes.py
⏱️ Runtime :
115 milliseconds
→735 microseconds
(best of591
runs)📝 Explanation and details
Here's an optimized version of your code.
Your profiling result shows the code is dominated by the repeated check of whether any edge references a node’s id as "source".
This is O(N*M) where N = nodes, M = edges.
We can precompute the set of all edge "source" ids so the inner check is O(1) instead of O(M).
Here’s the faster rewrite (comments preserved).
Summary of speedup.
Behavior and return values are unchanged.
✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
To edit these changes
git checkout codeflash/optimize-find_last_node-mce2fvtu
and push.