You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drop the wash, split quant from cost, restore Context
Three fixes to the per-machine table:
No background on the cells. The Q6-or-better signal now rides on the
quant name alone, ink against muted, so the tier still reads without a
shaded ground. FITS_BG and the .swatch rule go with it, both unused after.
The quant and the memory it costs were one run of text ("Q8_0 30"), which
made them hard to tell apart. They are two spans now: the quant in mono
and bold, because it is a filename, and the cost muted, smaller and
carrying its unit beside it.
Context comes back. It was dropped to get the budget columns onto a phone
screen, which was not mine to decide. It sits after the budget columns
instead of before, so the answer still leads on a 390px screen.
The audit reads the two spans separately rather than splitting cell text
on a space, so a cell that loses its size fails instead of reparsing the
quant name as one. Both that and a doctored size were confirmed to fail.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
# every sortable table on the page, not one by id: the open-weight table
@@ -1224,10 +1232,10 @@ def h2h_stats(spec):
1224
1232
<section>
1225
1233
<h2>Which quantization for my machine</h2>
1226
1234
<p class="takeaway" style="margin:0 0 10px"><b>Pick your memory, read across.</b> Each cell is the <b>best quantization that fits</b>, named as the file you would download from the {gguf_sources} GGUF repos, and what it weighs in GB. Every figure is a real published file, not arithmetic.</p>
1227
-
<p class="takeaway" style="margin:0 0 10px">The weights do not get the whole machine, so each column reserves room for the OS, the KV cache and activations: {budget_reserve_note}. <span class="swatch" style="background:{FITS_BG}"></span> marks a pick at <b>Q6 or better</b>, where quantization is not the thing holding the model back.</p>
1235
+
<p class="takeaway" style="margin:0 0 10px">The weights do not get the whole machine, so each column reserves room for the OS, the KV cache and activations: {budget_reserve_note}. A quant in <b>full black</b> is <b>Q6 or better</b>, where quantization is not the thing holding the model back; a greyed one is a 4-to-5-bit compromise.</p>
1228
1236
<p class="takeaway" style="margin:0 0 10px">A blank means <b>nothing 4-bit or better fits</b>, which is a real answer rather than a missing one: below 4-bit degradation stops being minor and coding feels it first, so no cell recommends going lower. {too_big_note}</p>
<h2id="which-quantization-for-my-machine"><aclass="anchor" href="#which-quantization-for-my-machine">Which quantization for my machine</a></h2>
367
371
<pclass="takeaway" style="margin:0 0 10px"><b>Pick your memory, read across.</b> Each cell is the <b>best quantization that fits</b>, named as the file you would download from the <ahref="https://huggingface.co/bartowski">bartowski</a> and <ahref="https://huggingface.co/unsloth">unsloth</a> GGUF repos, and what it weighs in GB. Every figure is a real published file, not arithmetic.</p>
368
-
<pclass="takeaway" style="margin:0 0 10px">The weights do not get the whole machine, so each column reserves room for the OS, the KV cache and activations: 16 GB at 128, 8 GB at 64, 4 GB at 32, 4 GB at 24. <spanclass="swatch" style="background:#dbe7fc"></span> marks a pick at <b>Q6 or better</b>, where quantization is not the thing holding the model back.</p>
372
+
<pclass="takeaway" style="margin:0 0 10px">The weights do not get the whole machine, so each column reserves room for the OS, the KV cache and activations: 16 GB at 128, 8 GB at 64, 4 GB at 32, 4 GB at 24. A quant in <b>full black</b> is <b>Q6 or better</b>, where quantization is not the thing holding the model back; a greyed one is a 4-to-5-bit compromise.</p>
369
373
<pclass="takeaway" style="margin:0 0 10px">A blank means <b>nothing 4-bit or better fits</b>, which is a real answer rather than a missing one: below 4-bit degradation stops being minor and coding feels it first, so no cell recommends going lower. The nine open models not listed need more than 128 GB even at 4-bit: Kimi K3, MiMo-V2.5-Pro, MiniMax M3, DeepSeek V4 Flash, Qwen3.8 Max, DeepSeek V4-Pro, Hy3, Inkling and GLM 5.2.</p>
0 commit comments