⚡️ Speed up function retrieve_timesteps by 96%
#135
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.
📄 96% (0.96x) speedup for
retrieve_timestepsinsrc/diffusers/pipelines/deprecated/alt_diffusion/pipeline_alt_diffusion.py⏱️ Runtime :
642 microseconds→328 microseconds(best of703runs)📝 Explanation and details
Here is an optimized version of your program that reduces runtime by avoiding repetitive heavy calls to
inspect.signatureandset()in each invocation.Instead, it uses per-class caching for parameter accept checks. The function logic, signature, comments, and exception messages are unchanged. This optimization is fully compatible with all types for
scheduler.Optimization summary:
"timesteps" in set(inspect.signature(...).parameters.keys())and"sigmas" in set(...)checks, as shown in your line profile.✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-retrieve_timesteps-mbdmw0d7and push.