vllm-project/vllm

[Feature]: Upstream DGX spark improvements from Avarok-Cybersecurity/dgx-vllm

Open

#37,141 opened on 2026年3月16日

GitHub で見る
 (13 comments) (1 reaction) (0 assignees)Python (80,034 stars) (16,816 forks)batch import
feature requesthelp wantednvidiaquantization

説明

🚀 The feature, motivation and pitch

As shown in the readme in Avarok-Cybersecurity/dgx-vllm, there are gaps in vLLM fp4 performance for DGX. The fixes seem not too complicated, and we should try to upstream the changes from the repo into vLLM.

Avarok-Cybersecurity/dgx-vllm#7

Alternatives

No response

Additional context

No response

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

コントリビューターガイド

技術スタック
python
領域
performance
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
5
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
active
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
familiarity with vLLM codebaseunderstanding of fp4 precisionexperience with GPU kernel optimization
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
20
調査方針
Start by reviewing the referenced repository Avarok Cybersecurity/dgx vllm and its issue #7 to understand the specific improvements made for fp4 performance on DGX. Since no code diff is provided in this issue, the next step is to clone the fork, identify the relevant commits or changes, and assess how they could be integrated into the main vLLM codebase. Note that this is a complex task involving low level performance optimizations, and it lacks a clear list of deliverables. Maintainers should clarify which parts of the fork are intended to be upstreamed and the expected scope of work.