⚡️ Speed up method DDPMScheduler.get_velocity by 36%
#133
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.
📄 36% (0.36x) speedup for
DDPMScheduler.get_velocityinsrc/diffusers/schedulers/scheduling_ddpm.py⏱️ Runtime :
922 microseconds→679 microseconds(best of534runs)📝 Explanation and details
Optimization summary:
.to()conversions ofalphas_cumprodandtimestepsunless their device or dtype differs, saving copy time..flatten()and dynamic unsqueezing; use.reshape(target_shape)to broadcast in as few allocations as possible.index_selectinstead of direct indexing for efficiency and type/device consistency, astimestepsmay be on CUDA.sqrt()computation is performed directly after index selection for efficiency.✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-DDPMScheduler.get_velocity-mbdlvknjand push.