⚡️ Speed up function gcd_recursive
by 10%
#130
+3
−3
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.
📄 10% (0.10x) speedup for
gcd_recursive
insrc/math/computation.py
⏱️ Runtime :
69.3 microseconds
→63.1 microseconds
(best of206
runs)📝 Explanation and details
The optimization converts a recursive implementation to an iterative one by replacing the recursive call with a
while
loop. The key change is eliminating the function call overhead that occurs with each recursive step.What was changed:
if b == 0: return a
andreturn gcd_recursive(b, a % b)
withwhile b != 0: a, b = b, a % b
return a
outside the loopWhy it's faster:
Performance characteristics from tests:
The 9% overall speedup comes from eliminating Python's function call mechanism while preserving the exact same mathematical algorithm.
✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
To edit these changes
git checkout codeflash/optimize-gcd_recursive-mh1oskej
and push.