⚡️ Speed up function find_last_node
by 15,745%
#45
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,745% (157.45x) speedup for
find_last_node
insrc/dsa/nodes.py
⏱️ Runtime :
37.7 milliseconds
→238 microseconds
(best of556
runs)📝 Explanation and details
Here is a faster version of your program. The main optimization is to avoid repeatedly scanning
edges
for each node. Instead, we build a set of all edge sources just once and then look for the first node whose id is not in this set.Explanation:
source
ids present inedges
in a single pass (O(N)
time whereN
is the number of edges).O(1)
lookup for each node, leading to overallO(M+N)
time, whereM
is the number of nodes.all()
call inside the generator, which could beO(N*M)
in the worst case.✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
To edit these changes
git checkout codeflash/optimize-find_last_node-mce8nlg9
and push.