<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Quantisation - vo.rs</title><link>https://vo.rs/tags/quantisation/</link><description>Latest from the Quantisation desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 14 Oct 2025 08:45:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/quantisation/" rel="self" type="application/rss+xml"/><item><title>Quantisation Explained: GGUF, GPTQ and Small VRAM</title><link>https://vo.rs/story/quantisation-explained-gguf-gptq-and-small-vram/</link><description>&lt;p&gt;The first time I tried to run a 13B model on a card with 12GB of VRAM, I hit an out-of-memory error before the model had finished loading. The maths is unforgiving: a 13-billion-parameter model in the FP16 precision it was likely trained and released in needs roughly 26GB just to hold the weights, before you&amp;rsquo;ve allocated a single byte for the context window. My card had less than half that. Quantisation is the technique that made it possible anyway, and understanding what it actually does — rather than treating it as a magic &amp;ldquo;make it smaller&amp;rdquo; checkbox — is the difference between picking a sensible trade-off and quietly running a model that&amp;rsquo;s dumber than it needs to be.&lt;/p&gt;</description><pubDate>Tue, 14 Oct 2025 08:45:00 +0000</pubDate></item></channel></rss>