Optimize and harden MiniMax Music 3 long-form generation - #309
Merged
Conversation
a-github-name
force-pushed
the
codex/minimax-music3-next-optimizations
branch
from
August 16, 2026 12:11
1dd938f to
5720cb7
Compare
a-github-name
marked this pull request as ready for review
August 16, 2026 15:38
Merged
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.
Summary
sequentialflow andlegacyseeding remain unchanged defaultsoverlap-averageand direct INT8 ConvRot only as explicit research paths because measured runs did not establish either as a production speed winMeasured results
5ec23504131e7b74cef86f368d1a9164f9ac96d071d9c0f25615c5525fc559beoverlap-averageflow measured 464.38 s versus 454.31 s sequential, so it remains opt-in and is not presented as an acceleration presetThe long-form runs used an M4 Max with 128 GB unified memory. The 23.78 GB peak makes 32 GB plausible, but this PR does not claim 32 GB support without an actual 32 GB hardware run.
Post-restack MLX refresh receipt
The exact rebased head
5720cb7c1411f179af6398d874d6d35b590cf9d9was replayed against the installed upstream checkpointMiniMaxAI/MiniMax-Music3@bd348f9c49ea3c1b39f33ace3436f8fad435f24eafter the MLX/mlx-swift refresh landed onmain.stage-separated-v1, seed202608155ec23504131e7b74cef86f368d1a9164f9ac96d071d9c0f25615c5525fc559be, byte-identical to the pre-refresh bounded-cache receipt1.0, RMS0.08406066, stereo-collapse fraction0/usr/bin/timewall time included machine-admission queueing and is not used as an inference-performance resultValidation
mainat22b35602059f2df6f5a169ad24e44d04b3e264dc./scripts/check.shswift build -c releasepnpm docs:buildgit diff --check origin/main...HEADTHIRD_PARTY_NOTICES.mdnot applicable: no vendored artifacts or package pins changed