Support mixed-type quantization within a single quantization backend
維護者通常 1 天內回覆
@sayakpaul 已經在處理了。
開始於 2026年11月17日。
評估
這個 Issue 還沒有評估資料。
描述
Motivation
Other tools like ComfyUI and Unsloth already support mixed-type quants: different layers or modules of a model are quantized with different schemes or precisions. Some layers stay in high precision, and others drop to lower bit-widths. This usually gets a better quality/memory trade-off than quantizing every layer the same way.
Most of the quantization backends Diffusers integrates with already support this natively. Diffusers should let users use that capability.
Proposal
- Allow mixed quantization types within a single backend (for example, different torchao or bnb configs per module/layer pattern), when the underlying backend framework supports it.
- Out of scope for now: mixing backends in one checkpoint (for example, some layers bnb and others torchao). Not all backends are feature-complete, so this would be messy. We also haven't seen such checkpoints in practice.
Open questions
- API design: how users specify per-module/per-layer quant configs (pattern-based mapping,
modules_to_not_convert-style extension, etc.). - Serialization and loading of mixed-quant checkpoints, plus compatibility with existing pre-quantized checkpoints (for example, from the ComfyUI / Unsloth ecosystems).
- Which backends support this today, and what's missing in each.
Benchmarks / guidance
As part of this work, produce:
- Benchmarks (memory, latency) comparing uniform vs. mixed quantization on representative pipelines.
- Qualitative comparisons of outputs.
- Better-grounded heuristics for choosing which layers to keep in higher precision. Existing community guides give heuristics, but they're hit and miss.
Requested by Sayak Paul - Slack thread - Agent trace
- 主要語言
- Python
- 星號
- 34.9k
- 分支
- 7.5k
- 平均合併
- 3 天 16 小時
- 30 天內合併 PR
- 65
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
huggingface/diffusers 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 84/100
huggingface/diffusers#15363 ·
維護者通常 1 天內回覆
-
`ZImageImg2ImgPipeline` / `ZImageInpaintPipeline`: explicit height/width different from the input image raises RuntimeError可能已有人在做 @chessing234 於 1 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 70/100
huggingface/diffusers#15337 · 2 則留言 ·
維護者通常 1 天內回覆
-
Multi-vector textual inversion uses only the first vector when the token has uppercase letters (transformers v5)可能已有人在做 @sunhouy 於 2 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 75/100
huggingface/diffusers#15313 ·
維護者通常 1 天內回覆
-
TCDScheduler advances the generator on the final step of a strength-truncated custom schedule可能已有人在做 @SIDDARTHAREDDY8 於 5 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 74/100
huggingface/diffusers#15288 · 2 則留言 ·
維護者通常 1 天內回覆
-
unload_textual_inversion(token) leaves the extra tokens of a multi-vector embedding behind, so it can't be loaded again可能已有人在做 @sohailshk 於 11 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
huggingface/diffusers#15211 · 3 則留言 ·
維護者通常 1 天內回覆
查看 huggingface/diffusers 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 73/100
維護者通常 1 天內回覆
-
Unused loot bag group names left in dreamcraft en_US.lang可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉Status: Triage Suggestion
難度 1/5 1 小時以內 新手友好度 90/100
GTNewHorizons/GT-New-Horizons-Modpack#27789 ·
維護者通常 1 天內回覆
-
bug frontend sev-5
難度 2/5 1-3 小時 新手友好度 83/100
-
core good first issue
難度 2/5 1-3 小時 新手友好度 65/100
-
b4b code health next
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆