⚡️ Speed up function find_last_node
by 15,978%
#44
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,978% (159.78x) speedup for
find_last_node
insrc/dsa/nodes.py
⏱️ Runtime :
37.9 milliseconds
→236 microseconds
(best of551
runs)📝 Explanation and details
Here’s a rewritten, optimized version of the given program. The original code is O(n·m), where
n
is the number of nodes andm
is the number of edges, because for each node, it checks all edges.We can make it O(n + m) by first collecting all nodes that are referenced as
"source"
in any edge. Then, the last node is any node whose"id"
is not in this set.Key improvement:
✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
To edit these changes
git checkout codeflash/optimize-find_last_node-mce6er7u
and push.