← Latest papers
⚡ electrical engineering

Quantizing Whisper-small: How design choices affect ASR performance

This paper presents a cross-library evaluation of post-training quantization on Whisper-small, demonstrating that dynamic int8 quantization using Optimum-Quanto offers the optimal trade-off by reducing model size by 57% while improving word error rate without retraining.

Original authors: Arthur Söhler, Julian Irigoyen, Andreas Søeborg Kirkedal

Published 2026-05-22
📖 4 min read☕ Coffee break read

Original authors: Arthur Söhler, Julian Irigoyen, Andreas Søeborg Kirkedal

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you have a brilliant, world-class speech translator named Whisper. This translator is incredibly accurate, but it's also a giant. It's like a luxury limousine: it has a massive engine (high computing power) and a huge trunk (lots of memory). While it's perfect for a high-end hotel, you can't easily drive it into a narrow, bumpy alleyway (like a small phone, a smart speaker, or a low-power device) because it's too heavy and takes up too much space.

The authors of this paper asked: "How can we shrink this limousine down to fit in a compact car without losing its ability to drive safely?"

They didn't try to rebuild the engine (retraining the model). Instead, they used a technique called Quantization. Think of quantization as a "packing strategy."

The Packing Strategy (Quantization)

Normally, the model's "brain" (its weights) is written in high-definition, 32-bit floating-point numbers. This is like writing a recipe using exact measurements down to the milligram. It's precise, but it takes up a lot of paper.

Quantization is like rewriting that recipe using simpler, rounder numbers (like "a cup" instead of "237.42 grams"). This makes the recipe much shorter (smaller file size) and faster to read (faster processing), but there's a risk: if you round too aggressively, the cake might not taste right.

The researchers tested four different "packing companies" (software libraries: PyTorch, Optimum-Quanto, HQQ, and bitsandbytes) to see which one could shrink the model best without ruining the cake.

The Experiments: Clean vs. Chaotic Rooms

They tested these packed models in two different environments:

  1. The Quiet Library (test-clean): A room where the speaker is clear, and there's no background noise.
  2. The Busy Train Station (test-other): A noisy, chaotic environment with echoes and background chatter.

What They Discovered

1. The "Dynamic" vs. "Static" Packing

  • Static Packing: Imagine pre-measuring all the ingredients before you leave the house and sticking to that exact list, no matter what happens. The researchers found this didn't work well for Whisper. It was actually slower and made more mistakes. Why? Because the model has complex parts (like "LayerNorm" and "Softmax") that are like delicate glassware; trying to pre-pack them into simple boxes broke them, forcing the system to unpack and repack them constantly, wasting time.
  • Dynamic Packing: This is like having a smart assistant who measures ingredients as you go. The system adjusts on the fly. This was the winner. It kept the model fast and accurate, even in the noisy train station.

2. The "Bit-Width" Trade-off (How much to round?)

  • Int8 (8-bit): This is like rounding to the nearest whole number. It was the sweet spot. It shrunk the model by 57% (making it much smaller) but kept the accuracy almost as good as the original giant. In fact, on the GPU (a powerful computer chip), the 8-bit version was so good it actually understood the noisy train station better than the original giant!
  • Int4, Int3, nf4 (Super-aggressive packing): This is like rounding to the nearest "cup" or "handful." You get massive savings (up to 71% smaller!), but the cake starts to taste weird. In the quiet library, it was okay. But in the noisy train station, the model got confused and made many more mistakes.

3. The Hardware Difference (CPU vs. GPU)

  • On the CPU (the standard brain of a computer): The PyTorch library with 8-bit packing was the fastest. It was like a sports car: quick and efficient, though slightly less accurate in the noise.
  • On the GPU (a specialized graphics chip): The Optimum-Quanto library with 8-bit packing was the champion. It was slightly slower than PyTorch but produced the most accurate results, even beating the original giant in noisy conditions.

The Bottom Line

The paper concludes that you don't need to rebuild the model to make it fit on small devices. You just need to choose the right packing strategy:

  • If you need speed on a standard computer: Use PyTorch with 8-bit dynamic packing.
  • If you need the best accuracy (especially in noisy places) on a powerful chip: Use Optimum-Quanto with 8-bit dynamic packing.
  • If you are desperate for space and can tolerate some mistakes: You can go smaller (4-bit or 3-bit), but be warned: the model will struggle significantly if the audio is messy or noisy.

In short, 8-bit dynamic quantization is the "Goldilocks" solution: it's not too big, not too small, and just right for getting Whisper into the real world without losing its voice.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →