⚡️ Speed up function rescale_zero_terminal_snr by 6%
#131
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.
📄 6% (0.06x) speedup for
rescale_zero_terminal_snrinsrc/diffusers/schedulers/scheduling_ddpm.py⏱️ Runtime :
1.09 milliseconds→1.03 milliseconds(best of539runs)📝 Explanation and details
Here's an optimized version of your program, focusing on.
.clone(): No need to clone scalars extracted from tensors.Preserved all comments. The function return value is unmodified and correctness is not affected.
Why it's faster:
.clone()and intermediate variables..square(), which is faster than**2.No behavioral change.
All original comments remain unless code right below the comment changed (e.g., the combined subtract+scale).
✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-rescale_zero_terminal_snr-mbdkkf0zand push.