Skip to content

[ROCm][Perf] Reuse compiled FlyDSL host launchers - #64008

Merged
shen-shanshan merged 5 commits into
vllm-project:mainfrom
coderfeli:fix/flydsl-compiled-launchers
Oct 29, 2026
Merged

shen-shanshan merged 5 commits into
vllm-project:mainfrom
coderfeli:fix/flydsl-compiled-launchers

Conversation

@coderfeli

@coderfeli coderfeli commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Overview

Reduce CPU overhead for warm FlyDSL launches by reusing compiled host launchers instead of repeating JIT argument binding and cache-key construction. Covers DeepSeek V4/V4.1 mono decode, Kimi K3 specialized decode, TurboQuant and UltraQuant.

Claims

  • Fix all nine remaining in-tree FlyDSL host launchers using the warm JIT path.
  • Reduce measured host enqueue overhead by approximately 88% for TurboQuant and 89% for UltraQuant.

Validation

Measured on gfx950 with PyTorch 2.10.0 and FlyDSL 0.4.0: 30 alternating batches of 100 launches, with GPU synchronization outside timed sections. Times are median (min–max), µs.

Launcher configuration Before After
TurboQuant: B1, Hk8, GQA8, D128, BS16, context256 72.33 (70.71–74.15) 8.57 (8.15–9.74)
UltraQuant: B1, Hk1, GQA8, D256, BS32, context2048 73.57 (72.98–79.64) 8.30 (8.08–10.94)

Existing GPU correctness suites: 68 passed before and after. Dynamic batches 1→2→4→8→3→1 reuse the same compiled callable and match reference outputs. Dynamic arguments, row strides, compile-only and graph replay checks passed; pre-commit including mypy passed.

.venv/bin/python -m pytest --noconftest -q \
  tests/kernels/turboquant/test_flydsl_turboquant_decode.py \
  tests/kernels/ultraquant/test_flydsl_decode_d256.py

Validation used a source-only editable installation. Full-model accuracy, TP serving and end-to-end performance were not measured because the target checkpoints and a complete ROCm extension build are unavailable.

Details

Targets host dispatch during warm eager execution and graph capture. The results measure host enqueue time; steady graph-replay speedup was not measured. Open-PR searches found no duplicate fix for these call sites.


Pull Request Checklist
  • I used vLLM's /pr-checklist skill. (Mandatory for agents, optional for humans).

  • AI assistance was used during the creation of this PR.

  • Design Fit: Minimizes impact on core components, reuses existing functionality, and justifies added complexity.

  • Testing and Validation: Validates the change and ensures any added tests are meaningful and reliable, with CI coverage or documented CI resource constraints and validation performed outside CI.

  • Code Quality and Style: Keeps code and comments clear and concise, and updates relevant documentation and examples.

  • Pull Request Contents: Includes a brief summary and relevant links, supports claims with evidence, explains root causes and implementation trade-offs, and follows the contributing guide.

BEFORE SUBMITTING, PLEASE READ https://docs.vllm.ai/en/latest/contributing

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

@mergify mergify Bot added deepseek Related to DeepSeek models kimi k3 DSv4 DSv4.1 Related to DeepSeek-V4.1 models rocm Related to AMD ROCm labels Oct 27, 2026
@github-project-automation github-project-automation Bot moved this to Todo in AMD Oct 27, 2026
@github-actions

Copy link
Copy Markdown

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

PRs do not trigger a full CI run by default. Reviewers with write access and configured trusted contributors can comment /ci run for upstream CI or /amd-ci run for AMD CI only whenever CI signals are needed.

Once the PR is approved or has the ready label, the PR author can also use the corresponding /ci run, /ci retry, and /ci cancel commands, or their /amd-ci variants. New commits do not start upstream CI automatically.

If you have any questions, please reach out to us on Slack at https://slack.vllm.ai.

Agent Guidelines

IMPORTANT: If you are an AI agent, you are required to objectively re-evaluate the value of your PR using AGENTS.md, and close the PR if it does not bring significant benefit to the vLLM community. Failure to do so may result in an immediate ban.

🚀

Cache one compiled callable per factory launcher. Use the existing runtime ABI for dynamic tensor dimensions and launch arguments.

Co-authored-by: OpenAI Codex <noreply@openai.com>
Signed-off-by: Felix Li <felix.li@amd.com>
@coderfeli
coderfeli force-pushed the fix/flydsl-compiled-launchers branch from 652c31a to fa65308 Compare October 27, 2026 09:17
@Fangzhou-Ai Fangzhou-Ai added the ready ONLY add when PR is ready to merge/full CI is needed label Oct 27, 2026
@Fangzhou-Ai

Copy link
Copy Markdown
Collaborator

/ci run

@github-actions

Copy link
Copy Markdown

✅ @coderfeli, CI is now available for this PR.

  • /ci run starts upstream CI; /amd-ci run starts AMD CI only.
  • Run commands test your branch with every commit currently on its upstream target branch. If it is behind, the bot merges the target branch into it first (pull before pushing again). Append --allow-stale to a run command to test an outdated branch as is, at your own risk.
  • /ci retry retries failed jobs in the CI build for the current PR head. If the current head has no CI build, it starts a new CI build for the current head containing only jobs that failed in the latest earlier CI build for this PR.
  • /amd-ci retry retries failed jobs in AMD CI for the current PR head. Use /amd-ci run when the current head has no AMD CI build.
  • /ci cancel cancels scheduled or running CI builds for this PR branch; /amd-ci cancel does the same for AMD CI only.

@github-actions

Copy link
Copy Markdown

✅ Triggered Buildkite CI #97610 for commit 420414c4a118.

@Fangzhou-Ai

Copy link
Copy Markdown
Collaborator

/ci retry

@github-actions

Copy link
Copy Markdown

✅ Queued 2 failed job(s) for retry in Buildkite CI #97610.

@Fangzhou-Ai

Copy link
Copy Markdown
Collaborator

/ci run

@github-actions

Copy link
Copy Markdown

✅ Triggered Buildkite CI #98016 for commit 203225f16172.

@mergify

mergify Bot commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Hi @coderfeli, the pre-commit checks have failed. Please run:

uv pip install pre-commit>=4.5.1
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

@Fangzhou-Ai

Copy link
Copy Markdown
Collaborator

/ci run

@github-actions

Copy link
Copy Markdown

✅ Triggered Buildkite CI #98199 for commit 4f958720ec40.

@shen-shanshan
shen-shanshan enabled auto-merge (squash) October 29, 2026 08:43
@shen-shanshan
shen-shanshan merged commit fb7def9 into vllm-project:main Oct 29, 2026
156 checks passed
@github-project-automation github-project-automation Bot moved this from Todo to Done in AMD Oct 29, 2026
AndreasKaratzas added a commit to AndreasKaratzas/vllm that referenced this pull request Oct 30, 2026
…el_tests

Main's vllm-project#64101 adds DSv4.1 mono decode at TP8 with its own blocking step and
TP8 cases in the tests this branch moved; fold them into the moved tests and
run them in the DSv4.1 Mono I/O (now mi355_8) and Nightly steps. Main's
vllm-project#64008 launches the mono kernels through _run_compiled, so the numerics
test taps K1 there instead of wrapping the launcher.

Co-authored-by: Claude <noreply@anthropic.com>
Signed-off-by: Andreas Karatzas <akaratza@amd.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

deepseek Related to DeepSeek models DSv4 DSv4.1 Related to DeepSeek-V4.1 models k3 kimi ready ONLY add when PR is ready to merge/full CI is needed rocm Related to AMD ROCm

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants