Dense Qwen retains duplicate MLP intermediates across serialized graph capacities
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- python
調査の方向性
Read the offered branch linked in the issue and compare its port with upstream commit 1fd1f91; the issue identifies the dense Qwen decoder and existing prefill/decode Scratch banks as the relevant entry points. Start with tests/recipes/test_qwen38_dense_scratch.py, then qualify the exact current-main tree with GPU preparation, capture, export, numerical checks, and native replay. Done means those checks pass; the issue says they are still outstanding.
索引モデルが issue の本文から書いたものです。
説明
Code offered for maintainer discussion: https://github.com/Maxrio9/flare-local-inference/tree/dense-mlp-scratch-20261023. This is an issue rather than a PR because the standalone current-main port has not received GPU qualification.
The dense Qwen decoder allocates gate, up, down and MLP-input intermediates inside every PreparedDecoder, retaining duplicate buffers across serialized graph capacities. Sharing only the CUDA graph pool does not share those constructor allocations. This contributes to preparation OOM on a 32GB card with the official Qwen3.8-27B target plus a parallel drafter at prefill 4096.
Allocate those four disjoint BF16 fields in each existing prefill/decode Scratch bank and pass bounded row views to graph variants. They share the same serialized lifetime as the bank's existing activations and GDN scratch; persistent model state is unchanged. The memory report includes retained mlp_scratch_bytes. No projection arithmetic, precision, graph contract or runtime change.
Offered implementation and validation status
The offered branch is a focused port of 67aec46 onto upstream 1fd1f91, without the MTP, DFlash2, attention-buffer or third-party target-loading changes. CPU storage validation checks distinct live fields, common backing across capacity views, contiguous rows and untouched tails.
Exact rebased tree: pytest -q tests/recipes/test_qwen38_dense_scratch.py passed (1 test), using the current pinned FlashInfer 9c9e94ef source for CPU imports in an isolated path. The shared experiment environment was left unchanged. The test does not initialize CUDA or qualify graph execution.
The original implementation on the experimental DFlash2 stack calculated a 1,688,207,360-byte (1.572 GiB) prefill-storage saving at chunk 4096, before optional scored variants. That is an allocation delta for that catalog, not a live-memory peak or a measured saving on this rebased ordinary catalog.
On that original stack: 69 state/ring CUDA cases, 21 MTP cases, compiled multi-chunk scoring and inactive-hole C4 checks passed. An official-target C4/64K/prefill4096 package exported and passed 222 pressure/probe requests, plus 75 on the final scheduler runtime and 51K cold/warm reuse. Cold 51K TTFT remained approximately 14.5–14.8 seconds: no latency improvement is claimed.
Not ready as a recipe PR: the exact standalone current-main port still needs GPU preparation/capture/export, alternating graph/scored-prefill numerical checks and native replay. Original-stack GPU results do not qualify this tree. Existing exported packages are unchanged; reduced buffers require re-export. Only dense Qwen is modified; other recipes' workspace lifetimes are not inferred from it.
Would you like this small ordinary-dense port qualified and submitted before the larger DFlash2 integration?
Authored and lifetime-reviewed by Codex (GPT-6), AI-assisted. Claude reviews measurement and wording only for this submission; the scratch design is not attributed to Claude Opus 5.5.
- 主要言語
- Rust
- スター
- 800
- フォーク
- 106
- 平均マージ
- 1日 3時間
- マージ済み PR（30日）
- 100
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
NVIDIA/hyperflare-inference のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
NVIDIA/hyperflare-inference#268 ·
メンテナーはふだん 1 日以内に返信
-
area:caching area:engram enhancement performance triage:design-review
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
NVIDIA/hyperflare-inference#230 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 15/100
NVIDIA/hyperflare-inference#278 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
NVIDIA/hyperflare-inference#276 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
NVIDIA/hyperflare-inference#271 ·
メンテナーはふだん 1 日以内に返信
NVIDIA/hyperflare-inference の issue をすべて見る
似ている issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 62/100
-
bug UI
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
wardian-app/Wardian#1746 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
jlcodes99/cockpit-tools#3125 ·
メンテナーはふだん 2 日以内に返信