Quantization-Aware Healing: a compressed, 4-bit model that outperforms its full-precision original
Back to Articles Quantization-Aware Healing: a compressed, 4-bit model that outperforms its full-precision original Team Article Published August 25, 2026 Upvote - Antonio Tiene AntonioTN Follow MultiverseComputingCAI Iker García-Ferrero Iker Follow MultiverseComputingCAI Ali Hashemi ali-hashemi Follow MultiverseComputingCAI Bakbergen Ryskulov bryskulov-mc Follow MultiverseComputingCAI Making a large language model smaller almost always comes with a cost.
The now-standard recipe for efficient deployment is to compress the architecture first, cutting the parameter count by removing layers, heads, or neurons, and then quantize the remaining weights down to 4 bits to shrink memory and compute further.
Both steps save a lot, but together they systematically degrade the capabilities people actually care about: reasoning, mathematical problem-solving, and code generation.Because of this, serious deployment pipelines add a recovery step, usually called healing, before the model goes into production.
Recent open-weight releases such as gpt-oss, NVIDIA's Nemotron family, and our own Hypernova 60B all rely on some version of this compress-then-heal approach.
Our latest paper, Quantization-Aware Healing: A Practical Recipe for Recovering Compressed, 4-Bit LLMs, asks a question that the field has mostly left open: once a model has already been through structural compression, not just quantization, how well does that recovery step actually work, and what is the right way to do it?
We introduce Quantization-Aware Healing (QAH), and applied to a GPT-OSS 120B model compressed to 60B parameters and quantized to MXFP4, it produces a model that beats its own full-precision (bfloat16) version on 7 of 9 benchmarks.
The 4-bit model ends up smaller, cheaper to run, and more accurate than the checkpoint it was quantized from.This inverts the usual relationship between a 4-bit model and the 16-bit model it came from.
Why the usual healing methods fall short here Most efficiency pipelines follow the same three steps: compress the architecture, quantize the compressed weights, then heal the damage.The difference between methods is entirely in that last step.
The dominant healing recipe is quantization-aware training (QAT).It inserts fake-quantization operators into the forward pass and keeps fine-tuning the model on a task loss, so the weights learn to tolerate the low-precision representation.
In practice this means re-running an already expensive multi-stage post-training process, supervised fine-tuning, RLHF, agentic tuning, through a noisier, lower-precision forward pass.
It is costly, and as our results show, it can also become unstable if training continues too long past its best point.An alternative, quantization-aware distillation (QAD), avoids re-running that history.
Instead of a task loss, it distills a frozen full-precision teacher directly into the quantized student through a KL-divergence loss on the output logits.This works well when the only change is quantization, because a genuine full-precision version of the exact same model exists to act as teacher.
But once a model has gone through structural compression, fewer layers, heads, or neurons, and not just fewer bits, that assumption breaks.There is no independently trained full-precision version of the smaller architecture.
The only candidate teacher is the recovered bfloat16 checkpoint, which is itself a distilled approximation of the original model.Distilling from it anchors the quantized student to a degraded target and caps its accuracy at that recovered checkpoint's own ceiling.
So the question of how to heal a model that has been both structurally compressed and quantized was, until now, genuinely open.Our approach QAH removes that ceiling with one change: it distills directly from the original, pre-compression model rather than from the recovered one.
Teacher and student do not even share an architecture.The teacher is full-size and full-precision, the student is half the size and running in MXFP4.Because a teacher's output distribution is architecture-agnostic, nothing about the size or shape mismatch prevents the transfer.
The student never sees hard labels, only the teacher's output distribution, matched through KL divergence on the logits.This reframes what the quantization stage is doing.Under QAH it is no longer a lossy postprocessing step applied after healing is finished.
It is a second, full pass of distillation against the original teacher, supervision that the bfloat16 checkpoint never received.
The 4-bit student is not compensating for information lost to quantization; it is picking up information the earlier recovery stage did not have the time or data to transfer.There is also a stability benefit that falls out of the loss itself.
Because KL distillation ties the student to a fixed teacher distribution, once the student catches up there is no further pressure for it to drift.A cross-entropy task loss, by contrast, keeps pushing the student toward hard labels indefinitely.
That difference turns out to matter for both accuracy and training stability, as the comparison below shows.
To make QAH work at long context, where the healing corpus includes documents up to 32k tokens, we reuse the memory-efficient chunked KL-divergence loss from our companion paper on efficient distillation.
That loss computes the KL one slice of the sequence at a time and never materializes the full vocabulary-by-sequence grid, which is what makes 32k-token healing fit inside a fixed GPU memory budget.We covered the mechanics of that loss in a previous post.QAH overview.
After structural compression and quantization, capabilities drop sharply.QAH distills from the original model, a frozen teacher whose logits are precomputed offline, rather than from the recovered checkpoint.Source: paper Figure 1.
Results We applied QAH to a GPT-OSS 120B model, compressed to 60B parameters and recovered in bfloat16, then re-quantized to MXFP4 under QAH.The natural comparison is against that same 60B model's bfloat16 checkpoint, the best full-precision version of this architecture that exists.
The QAH model wins on 7 of the 9 benchmarks.Benchmark 120B teacher (MXFP4) 60B BF16 (recovered) 60B MXFP4 (QAH) QAH vs BF16 AA-LCR (long-context reasoning) 50.0 35.3 42.7 +7.4 AIME 2025 (math) 80.0 70.7 76.3 +5.6 Aider (agentic coding) 45.3 38.2 40.9 +2.7 τ²-bench (tool use) 68.4 59.4 61.7 +2.
3 GPQA Diamond (science) 69.0 65.7 67.4 +1.7 IFBench (instruction following) 63.3 58.4 59.9 +1.5 LiveCodeBench (coding) 66.0 65.5 66.5 +1.0 MMLU-Pro (knowledge) 78.0 74.0 73.8 −0.2 SciCode (science coding) 37.5 35.6 34.2 −1.
4 The two benchmarks where QAH trails, MMLU-Pro and SciCode, lose by less than a point and a half.Everywhere else the 4-bit model is ahead of its own 16-bit source, and the largest gains land on exactly the capabilities compression usually damages most: long-context reasoning (+7.
4 on AA-LCR) and math (+5.6 on AIME 2025).The comparison against the original 120B teacher is just as telling.Despite running at half the teacher's parameter count and roughly a quarter of its weight memory, the QAH model surpasses the full-size teacher on LiveCodeBench (66.5 vs.66.
0) and comes within 1.6 points on GPQA Diamond (67.4 vs.69.0).The largest remaining gap against the teacher is on AA-LCR, an extreme long-context benchmark where the capacity lost to compression is intrinsically the hardest to recover.
The 4-bit QAH model matches or beats its bfloat16 source on 7 of 9 benchmarks, and beats the full-size teacher on LiveCodeBench.Source: paper Figure 2.
QAH against QAT, head to head To isolate the effect of the loss function from everything else, we also compared QAH directly against QAT under matched conditions, quantizing a GPT-OSS 9B model to MXFP4 and tracking average performance across MMLU-Pro, LiveCodeBench, and GPQA Diamond as training progresses.
Both methods reach a similar peak, 54.9 for QAH against 54.6 for QAT, so on best-case accuracy they are effectively tied.The difference is in how they get there and what happens afterwards.
QAH reaches its peak in about 100 steps, roughly 7 times faster than QAT's 700, and then stays within about two points of that peak for the rest of training.QAT collapses sharply once past its peak, shedding nearly 19 points by step 1,200.
The practical consequence is a real deployment risk difference.A QAT checkpoint needs careful early stopping against a held-out signal to avoid shipping a model that has already started to degrade, whereas a sufficiently trained QAH checkpoint can be served safely because it simply does not drift.
This is consistent with the mechanism: KL distillation against a frozen teacher gives the student no incentive to move once it matches the teacher, while a cross-entropy objective keeps pushing on hard labels and eventually erodes capabilities the model inherited from the original.QAH peaks at 54.
9 in roughly 100 steps and holds; QAT reaches 54.6 only around step 700, then loses nearly 19 points by step 1,200.Source: paper Figure 3.What this changes in practice The accuracy story comes paired with the efficiency story that motivated compression in the first place.
At 4-bit precision the QAH model uses roughly 4 times less weight memory than the bfloat16 student, and at half the parameter count of the 120B teacher it roughly halves compute per token, which is what lets it run on substantially smaller hardware.
For model families that ship in bfloat16 rather than 4-bit, the combined parameter and precision reduction would be closer to 8 times less compute per token.The takeaway is that a compressed, 4-bit model does not have to be a lower-accuracy version of its full-precision counterpart.
With this healing recipe it can be smaller, cheaper to serve, and more accurate at the same time, and it reaches that point in a fraction of the training a QAT recipe would need.Quantization stops being a tax you pay for efficiency and becomes an extra opportunity to teach the model.
This work is part of Multiverse Computing's ongoing research into making large models smaller and cheaper to run without giving up the capabilities that make them useful.It sits alongside our companion work on efficient distillation, which supplies the long-context training machinery QAH depends on.
Want the full technical details, including the healing pipeline, the chunked KL implementation for long-context healing, and the distributed-training findings?Read the full paper, or get in touch with our team to talk about applying compression and healing to your own models.
Models mentioned in this article 2 Papers mentioned in this article 1 More from this author Making Knowledge Distillation Cheap Enough to Run at Scale 37 August 10, 2026 Community EditPreview Upload images, audio, and videos by dragging in the text input, pasting, or clicking here.
Tap or paste here to upload images Comment · Sign up or log in to comment Upvote - Models mentioned in this article 2 Papers mentioned in this article 1
Related
相關文章
Google 開源 Harness²:遞迴代理程式框架,無需新模型也能提升效能
Google Cloud AI Research 開源了 Harness²,這是一個遞迴代理程式框架,透過改良凍結模型周圍的程式碼與檔案來增強效能。對開發者而言,重點很簡單:你的代理程式無需更強大的模型也能進步。重點摘要:規模為框架而非模型,訓練參數為0,包含8個可編輯的框架元件,版本0.1.0。執行環境為Linux、Python 3.12或3.13搭配uv,模型呼叫則透過Vertex AI。GPU需求未公開。效能方面:一次改良步驟即可在3個基準測試中,提升所有4個模型與框架組合的表現。最佳成果:GLM-5搭配OpenCode在WorkBuddy-Bench上從64.2提升至75.7(+11.5點);最差表現:GLM-5搭配Codex在JobBench上僅提升1.2點(23.6至24.8)。什麼是Harness²?它是Google研究推出的即插即用框架。
如何利用NVIDIA結構化資料模型進行零訓練表格預測
In this tutorial, we implement Structured Data Models, NVIDIA’s new library that puts several pretrained foundation models for tables behind one PyTorch interface, and use it to make predictions without training.
認識 Kyutai REKI:2.4B VLA 模型為機器人操控帶來高效記憶
Kyutai 與 Inria 及 École des Ponts 合作,推出了 REKI——一個用於機器人操控的 2.4B 參數視覺-語言-動作模型(VLA)。該模型僅使用公開數據進行預訓練,並配備了輕量級的近期記憶功能。在三個分佈外基準測試中,僅有規模約為其兩倍的模型能超越它。所有模型權重已於今日在 Hugging Face 上公開。核心資訊:規模:2.4B 參數(2.2B Qwen3.5-2B VLM + 0.2B 流匹配動作專家)。記憶涵蓋最近 3 幀,間隔 1 秒。運行環境:在 1 張 NVIDIA H100 上進行基準測試。從兩個 256×256 攝像頭輸入,編譯後每個動作區塊耗時 21.8 毫秒。權重以 BF16 格式提供,暫無量化版本。性能:在 LIBERO-Plus 和 RoboTwin Clean2Rand 基準測試中,為公開數據預訓練的 VLA 模型中最優;在 LIBERO-Plus 上達到 90.4% 的最高分。
DeepSeek 發布 V4.1-Flash-1017,DeepSWE 得分 77.0,並開放搜尋 API
DeepSeek 剛發布 DeepSeek-V4.1-Flash-1017,這是其 V4.1-Flash 模型的新檢查點,現已在 DeepSeek 網站、應用程式及 API 上線。DeepSeek 宣稱該版本在性能、任務完成速度與輸出簡潔度上均優於 9 月發布的 V4.1-Flash,並稱之為性能與成本的帕累託改進。同時,DeepSeek 也向所有開發者開放了搜尋與擷取 API。對代理建構者而言,這意味著更便宜的編碼模型加上單一 API 金鑰即可使用的第一方網路層。重點摘要:骨架參數 552B,另加 196B 的 Engram 參數;預填充階段每 token 啟用 8B 參數,解碼階段啟用 16B 參數;上下文長度達 1M tokens,最大輸出 384K tokens。運行於 DeepSeek API 的 deepseek-flash 模型。9 月版的 V4.1-Flash 權重(763B 參數,FP8)採 MIT 授權。
2026年20款Jev替代方案:挑戰TypeSafe的決策模型
TypeSafe於2026年9月15日推出Jev,這是一款決策模型而非聊天機器人。使用者可定義允許的答案,Jev將回傳標籤、分數或是否的機率。約4週內,至少20款Jev替代方案相繼問世,來自Cloudflare、OpenAI、Perplexity、Liquid AI、AWS的Strands Labs及獨立開發者。本指南比較各方案在規模、授權、硬體、價格、Jev API相容性及已發布基準測試的表現。重點摘要:規模範圍從287M(GLiNER2.5-multi-Decide)到35B-A3B(Mapika Decider),Jev規模未公開。執行環境:Von和Laya等編碼器可在CPU上運行,4B適配器適用24 GB GPU或32 GB Mac。效能:多數開源模型在困難推理上落後Jev,但在狹窄分類任務上數款與之匹敵或超越。最佳表現:Cloudflare Clef在BANKING7取得94.20分。
長鑫科技市值兩月內跌去1萬億;阿里加碼AI硬件品牌,天貓、速賣通聯動;國行版蘋果AI有望12月上線,百度、阿里參與合作丨雷峰早報
要聞提示1.長鑫科技市值兩月內跌去1萬億2.年內已至少18次故障!DeepSeek發放宕機補償,有人拿到3000元3.阿里加碼AI硬件品牌,天貓、速賣通聯動4.國行版蘋果AI有望12月上線,百度、阿里參與合作5.可靈AI新一代模型Kling 4.