Skip to content

[executorch][muse] Add run_solo_batching - #23374

Open
Gasoonjia wants to merge 1 commit into
gh/Gasoonjia/41/basefrom
gh/Gasoonjia/41/head
Open

Gasoonjia wants to merge 1 commit into
gh/Gasoonjia/41/basefrom
gh/Gasoonjia/41/head

Conversation

@Gasoonjia

@Gasoonjia Gasoonjia commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Stack from ghstack (oldest at bottom):

The runtime half of batched Muse Glimmer on CUDA: runs what
export_solo_batching.py writes, on the batching extension only. It is
separate from solo.cpp and MuseGlimmerEngine, which it leaves untouched. The
structure follows the MLX batched example (mlx_run_llm_batched), with
CudaExecutor in place of ModuleExecutor.

  • One session per prompt. The batching Runner carries every generation, and
    DecodeFirstScheduler packs decodes and prefill chunks into shared forwards
    of up to W tokens (--max_decode_sequences decode slots, default one per
    session).
  • Prompts come from --prompt_file (one verbatim, already formatted),
    --prompts_file (one per line), or --prompt_tokens_file (token ids, no
    tokenizer needed). Stop tokens are the model's EOS plus <|eot|> and
    <|end_of_text|>, as MuseGlimmerEngine uses.
  • --cuda_graph and --weight_sharing (both default on) map to
    CudaExecutorOptions.
  • Prints each prompt's text, engine counters, KV pool usage, and GPU memory
    before load, after load and after generation. --report_json writes all of
    it, with each generation's tokens and finish reason, for CI to check.

Builds as the run_solo_batching target of the MG CMake project and the
muse-glimmer-cuda preset/make target (CUDA only). It links cuda_batching and
exports dynamic symbols for the AOTI blobs, as solo_runner does.

The tiny-model e2e test joins the OSS unittest-cuda job, after
make muse-glimmer-cuda.

Differential Revision: D123051485

[ghstack-poisoned]
@pytorch-bot

pytorch-bot Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 6 New Failures, 1 Pending, 2 Unclassified Failures

As of commit 4677ca5 with merge base c16dd0a (image):

NEW FAILURES - The following jobs have failed:

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

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

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@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 Oct 2, 2026

This branch was successfully deployed

1 active deployment
cadence — 4677ca5a Deployed Oct 2, 2026 by Gasoonjia via hifi-op-test / hifi4 #31153
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. meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant