Skip to content

[executorch][muse] Serve Muse Glimmer CUDA batching on a batched-sequence cache - #24882

Open
pytorchbot wants to merge 1 commit into
gh/Gasoonjia/92/origfrom
gh/Gasoonjia/93/orig
Open

pytorchbot wants to merge 1 commit into
gh/Gasoonjia/92/origfrom
gh/Gasoonjia/93/orig

Conversation

@pytorchbot

Copy link
Copy Markdown
Collaborator

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #24075 by @Gasoonjia
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/Gasoonjia/93/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/Gasoonjia/93/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/gh/Gasoonjia/92/orig
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/Gasoonjia/93/orig
Differential Revision: D125987299
@diff-train-skip-merge

…ence cache

Pull Request resolved: #24075

Adds `--kv-layout {cell,sequence}` and `--max-kv-seqs` to the Muse Glimmer CUDA batching exports (solo and DFlash). `sequence` writes a `batched-sequence` manifest for target and draft and publishes `get_offgraph_kv_max_seqs` (and `get_draft_offgraph_kv_max_seqs` / `get_draft_offgraph_kv_seq_capacity` for the draft). `CudaExecutor` and the CUDA DFlash executor pick `kBatchedSequence` when the artifact declares a sequence count, `kBatchedCell` otherwise, so the served feature set matches MLX's batched-sequence path. Cell artifacts are unchanged. The layout is chosen at export; switching it at runtime on one .pte is out of scope.
ghstack-source-id: 469359746
@exported-using-ghexport

Differential Revision: [D125987299](https://our.internmc.facebook.com/intern/diff/D125987299/)
@pytorch-bot

pytorch-bot Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/24882

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 1 Pending, 8 Unrelated Failures

As of commit e1a4e11 with merge base 4eb094b (image):

NEW FAILURES - The following jobs have failed:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Nov 11, 2026
@pytorchbot
pytorchbot deployed to upload-benchmark-results November 11, 2026 05:35 — with GitHub Actions Active

This branch was successfully deployed

1 active and 1 inactive deployments
upload-benchmark-results — e1a4e112 Deployed Nov 11, 2026 by pytorchbot via upload-benchmark-results #22291
cadence — e1a4e112 Deployed Nov 11, 2026 by pytorchbot via hifi-op-test / hifi4 #37752
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants