perf(minimax-h3): add conservative DiT velocity reuse - #38
Closed
L17807593 wants to merge 4 commits into
Closed
Conversation
L17807593
force-pushed
the
perf/minimax-h3-conservative-cache
branch
from
August 26, 2026 05:04
f898472 to
4622b9d
Compare
Collaborator
|
MiniMax h3已经支持了AdaTaylorCache的feature cache策略,应该包括了这种特殊情况 |
Author
|
感觉优化方向很类似但实现上没有完全包含,PR #38 中的 Conservative cache 位于 denoising loop 层,使用上一次 DiT 预测的完整 velocity 来跳过当前 DiT 调用;AdaTaylorCache 是在 block/feature 层进行缓存和近似。 |
Collaborator
|
@L17807593 AdaTaylorCache也是用来跳步加速的 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the Conservative DiT velocity cache, disabled by default, and depends on the lossless optimizations in PR #37.
TeleFuser MiniMax-H3: Conservative DiT Velocity Cache
1. Summary
This implementation adds a Conservative DiT velocity cache on top of the five lossless optimizations from PR #37. The cache is disabled by default. Under a four-GPU setup with five prompt/seed pairs, the final results are:
2. Lossless optimizations from PR #37
PR #37 provides the following five lossless optimizations:
These changes are described and validated in detail in PR #37.
3. Conservative DiT velocity cache
Added
MiniMaxH3DiTCacheConfig:conservativeis accepted as an alias forvelocity. In the default validation schedule, caching is active only between 20% and 80% of the denoising process. A DiT refresh is forced every other step, and at most one consecutive step reuses the previous video/audio velocity.When the cache is hit, the previous DiT-predicted video and audio velocities are reused and the current DiT invocation is skipped.
4. Per-case performance
5. Quality verification
All quality comparisons use the baseline generated with the same prompt and seed, comparing the final video and audio MP4 outputs.
Additional hash checks:
baseline == lossless: 5/5.lossy_only == all: 5/5.The lossless optimizations are bit-exact with the baseline at the final video and audio file level. The Conservative cache changes the denoising trajectory and final outputs, so it is a lossy optimization. The average PSNR, SSIM, and audio metrics show that the quality difference is limited under the tested settings.