<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Quantization & Formats]]></title><description><![CDATA[GGUF, EXL, AWQ, GPTQ, FP8, bitsandbytes.]]></description><link>https://airigs.net/category/17</link><generator>RSS for Node</generator><lastBuildDate>Mon, 02 Nov 2026 05:49:07 GMT</lastBuildDate><atom:link href="https://airigs.net/category/17.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 31 Oct 2026 23:48:20 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[8-bit KV Cache on Ampere]]></title><description><![CDATA[When using vLLM on Ampere GPUs, you may see that when selecting 8bit quantization formats for kv cache (fp8, int8) it falls back to other inference engines (Flashinfer, Triton Attention).
In my experience, Triton Attention performs very poorly on Ampere, especially on higher contexts, and Flashinfer doesn't work with DFlash2, which is most likely why these alternatives were made: (both available in the HyperQwen repository).

For FP8 KV Cache -&gt; There's a fork of Flash Attention 2 with fp8 kv cache.
For Int8 KV Cache -&gt; Use the 'PTH' option in HyperQwen.

In my experience, FP8 performed better at prefill and Int8 performed better at decode, both work with DFlash2 with solid results.
]]></description><link>https://airigs.net/topic/39/8-bit-kv-cache-on-ampere</link><guid isPermaLink="true">https://airigs.net/topic/39/8-bit-kv-cache-on-ampere</guid><dc:creator><![CDATA[fedes1to]]></dc:creator><pubDate>Sat, 31 Oct 2026 23:48:20 GMT</pubDate></item><item><title><![CDATA[EXL3]]></title><description><![CDATA[Seems to be objectively one of the BEST quantization formats as of now, with the added benefit that the inference engines run much better than llama.cpp (GGUF) for CPU offload.
For example, numbers on Qwen3.8-Flash-Next-exl3:
[image: image.jpeg]
[image: image.jpeg]
[image: image.jpeg]
]]></description><link>https://airigs.net/topic/8/exl3</link><guid isPermaLink="true">https://airigs.net/topic/8/exl3</guid><dc:creator><![CDATA[fedes1to]]></dc:creator><pubDate>Mon, 28 Sep 2026 16:42:34 GMT</pubDate></item><item><title><![CDATA[VLLM with mixed quantization]]></title><description><![CDATA[Findings from Minachist's huggingface profile.
Before anything, there's a really good blog post detailing the internals in Minachist's blog, found here.
Turns out these quantizations are the best I've found (compared to their size, for vLLM) by a HUGE margin, (photos from the blog linked above):
[image: image.jpeg]
[image: image.jpeg]
Sources (and good quantizations/resources):
https://minamism.com/posts/vllm-int5-7-quantization/
https://huggingface.co/Minachist/Qwen3.8-27B-INT6-Mixed-AutoRound
https://huggingface.co/Minachist/Qwen3.8-Flash-Next-INT4-Mixed-AutoRound
]]></description><link>https://airigs.net/topic/6/vllm-with-mixed-quantization</link><guid isPermaLink="true">https://airigs.net/topic/6/vllm-with-mixed-quantization</guid><dc:creator><![CDATA[fedes1to]]></dc:creator><pubDate>Mon, 28 Sep 2026 16:30:26 GMT</pubDate></item></channel></rss>