โ† All posts

Model Weight Quantisation

Model Weight Quantisation

Quantisation is how you make a 109B model fit on hardware that should not be able to run it.

At a simple level, it means storing numbers with less precision so the model takes up less memory.

Instead of keeping everything in BF16, you move to formats like:

  • FP8
  • INT8
  • INT4

The trade-off is tiny precision for a huge drop in size.

That matters because model sizes are growing faster than GPU memory.

So quantisation helps you:

  • run models on fewer GPUs
  • cut latency
  • support longer conversations
  • lower cloud costs

There are two main versions:

  • ๐—ช๐—ฒ๐—ถ๐—ด๐—ต๐˜-๐—ผ๐—ป๐—น๐˜† ๐—พ๐˜‚๐—ฎ๐—ป๐˜๐—ถ๐˜€๐—ฎ๐˜๐—ถ๐—ผ๐—ป: smaller model, but compute stays mostly the same
  • ๐—ช๐—ฒ๐—ถ๐—ด๐—ต๐˜ + ๐—ฎ๐—ฐ๐˜๐—ถ๐˜ƒ๐—ฎ๐˜๐—ถ๐—ผ๐—ป ๐—พ๐˜‚๐—ฎ๐—ป๐˜๐—ถ๐˜€๐—ฎ๐˜๐—ถ๐—ผ๐—ป: smaller model and faster matrix maths

The second one is where you get the biggest speed gains, because the model can use lower-precision Tensor Cores.

And the best part?

Good quantisation usually does ๐—ป๐—ผ๐˜ destroy accuracy.

With calibrated methods like GPTQ, AWQ, and SmoothQuant, many models stay very close to their original performance even at 4-bit.

So the real lesson is this:

Quantisation is not just a compression trick.
It is a deployment strategy.

If you are running LLMs on limited hardware, it is one of the first levers worth pulling.

Originally published on LinkedIn.

Turn your expertise into LinkedIn posts like this one.

Try Postars free โ†’
Model Weight Quantisation โ€” Postars