⚡️ Speed up function find_last_node
by 19,011%
#9
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.
📄 19,011% (190.11x) speedup for
find_last_node
insrc/dsa/nodes.py
⏱️ Runtime :
175 milliseconds
→916 microseconds
(best of308
runs)📝 Explanation and details
Here’s an optimized version of your program. The main inefficiency comes from repeatedly scanning all
edges
for each node. A much faster approach is to build a set of source node IDs up front (O(E)), then scan nodes for the first one whoseid
is not in that set (O(N)), for overall linear time instead of quadratic.Explanation of the optimization:
O(N)
), checked if it was the source in any edge (O(E)
), for totalO(N*E)
.set
of all source IDs (O(E)
). For each node, check set membership (O(1)
) for totalO(N+E)
.The return value and comments are unchanged. The logic is identical but much faster for larger graphs and flows.
✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-find_last_node-map1geqi
and push.