[TRTLLM-11288][fix] Adapt LTX2 pipeline to CompilationConfig warmup interface#12232
Conversation
…nterface LTX2 was merged after NVIDIA#12107 and still uses the old warmup interface (common_warmup_shapes + _run_warmup(warmup_steps)). Migrate to the new interface: default_warmup_resolutions, default_warmup_num_frames, and _run_warmup(height, width, num_frames, steps). Signed-off-by: Yiyun Lu <[email protected]>
|
/bot run --disable-fail-fast |
📝 WalkthroughWalkthroughThis change refactors the warmup mechanism in the LTX2Pipeline class from a batch approach iterating over predefined resolution shapes to an explicit per-call warmup pattern. The Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
|
PR_Github #39020 [ run ] triggered by Bot. Commit: |
…tring Signed-off-by: Yiyun Lu <[email protected]>
|
/bot run --disable-fail-fast |
|
PR_Github #39036 [ run ] triggered by Bot. Commit: |
|
PR_Github #39036 [ run ] completed with state |
…nterface (NVIDIA#12232) Signed-off-by: Yiyun Lu <[email protected]>
…nterface (NVIDIA#12232) Signed-off-by: Yiyun Lu <[email protected]>
…nterface (NVIDIA#12232) Signed-off-by: Yiyun Lu <[email protected]>
Summary by CodeRabbit
Description
Adapt LTX2 pipeline to the new
CompilationConfigwarmup interface introduced in #12107.LTX2 was merged after #12107 and still uses the old warmup interface (
common_warmup_shapes+_run_warmup(warmup_steps)). This PR migrates it to the new interface:common_warmup_shapes→default_warmup_resolutions+default_warmup_num_frames_run_warmup(warmup_steps)→_run_warmup(height, width, num_frames, steps)0→42(consistency with other pipelines)Test Coverage
test_warmup.pytests cover the base pipeline warmup logicskip_warmup=Trueand are not affectedPR Checklist
PR description clearly explains what and why.
PR Follows TRT-LLM CODING GUIDELINES.
Test cases are provided for new code paths.
Any new dependencies have been scanned for license and vulnerabilities.
CODEOWNERS updated if ownership changes.
Documentation updated as needed.
Update tava architecture diagram if significant design change.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.