⚡️ Speed up function retrieve_timesteps by 71%
#128
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.
📄 71% (0.71x) speedup for
retrieve_timestepsinsrc/diffusers/pipelines/ltx/pipeline_ltx.py⏱️ Runtime :
842 microseconds→493 microseconds(best of589runs)📝 Explanation and details
Key Optimizations:
inspect.signature(...).parameters.keys()for every function invocation. By caching the parameter set per scheduler class in_get_set_timesteps_param_set(cls), we reduce this to a one-time cost per scheduler class (for the process lifetime).inspectis only imported if necessary in the helper.This greatly increases speed especially for repeated calls and in hot loops.
✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-retrieve_timesteps-mbdhd3cqand push.