Is your engine lobotomizing your model? Kinda, and I measured it
retained text
I've been reading a lot about "engines lobotomizing the models they run", either because they quantize already quantized weights, or because they automatically turn on "hacky" flags to gain decode/prefill performance by default. I wanted to test this out by myself, not only with KLD but with real tasks, so I set up an experiment using **Qwen 3.8 Flash Next** with [Basalt](https://github.com/jesdga95/basalt) (disclaimer: I'm the developer) and two of the most popular "speed" flags: * **Routing bias:** the engine pushes the model toward experts that are already on the GPU, so it sometimes gets a convenient expert instead of the one it actually wanted. * **Tail skip:** when one of the model's lower expert picks isn't on the GPU, the engine just skips it instead of fetching it. Both are faster because fewer experts come from RAM, but they change the output. I added them to the engine as opt in flags so I could measure the real cost with everything else fixed. >**DISCLAIMER:** This post and the experiment were run by me, but it has been polished by AI. Rig: RTX 5090 + RTX 5060 Ti and 128 GB of DDR5. Settings tested: * **Shipped:** bias 1.5, skip rank ≥ 7. Values other engines ship (or have shipped) as defaults on smaller cards. * **Worst:** bias 16, skip rank ≥ 1, plus relaxed draft acceptance. Worst case scenario, not something anyone ships or would make sense to use. # 1. KLD 100 chunks of wikitext, decode path, against a llama.cpp Q8 reference. Exact IQ3\_XXS and Q2\_0 are in there for scale. |Pack + setting|File|PPL|KLD mean|Same top-1| |:-|:-|:-|:-|:-| |Q8\_0 exact|178 GiB|3.276|0.031|94.1%| |NVFP4 exact|122 GiB|3.304|0.068|91.4%| |IQ3\_S exact|81 GiB|3.385|0.155|87.3%| |IQ3\_XXS exact|74 GiB|3.470|0.243|84.0%| |IQ3\_S + shipped|81 GiB|3.583|0.244|84.3%| |NVFP4 + shipped|122 GiB|3.931|0.348|81.8%| |Q8\_0 + shipped|178 GiB|4.221|0.401|79.4%| |Q2\_0 exact|65 GiB|3.949|0.436|78.2%| |NVFP4 + worst|122 GiB|5.917|0.823|71.3%| |Q8\_0 + worst|178 GiB|12.858|1.616|56.8%| **Note:** even exact Q8\_0 is 0.031 away from the reference. That's mostly the reference's own noise, not damage: llama.cpp's Q8\_0 rounds a few spots of this model more than Basalt does, which adds about 0.01-0.02 to every row equally, so the rows still compare fairly. # 2. Does it really matter? KLD by itself is just a number, so I also ran a task eval: thinking off, temp 1.0, top\_p 0.95, top\_k 20, two different sets of questions: * **Ladders:** 300 chained steps, scored by step. * **Facts:** 1200 questions with 5 popularity bands (rare to famous), 3 seeds. |Config|Ladders|Facts|Ladders Δ|Facts Δ|Prose tok/s| |:-|:-|:-|:-|:-|:-| |Q8\_0 exact|45.4|38.1|||117| |NVFP4 exact|45.6|38.0|||272| |Q8\_0 + shipped|43.8|36.6|\-1.6 \[-3.4, +0.2\]|\-1.5 \[-2.5, -0.5\]|202| |NVFP4 + shipped|44.1|36.8|\-1.5 \[-3.2, +0.2\]|\-1.2 \[-2.2, -0.4\]|271| |IQ3\_S exact, small card\*|44.1|36.7|||192| |IQ3\_S + shipped, small card\*|38.9|34.3|\-5.2 \[-7.1, -3.2\]|\-2.3 \[-3.4, -1.3\]|299| |Q8\_0 + worst|26.6|2.7|\-18.8|\-35.3|379| \* Small card: the 5090 alone capped to 16gb, the experiment was run this way because it was still much faster than the 5060 Ti. On a big card the shipped flags barely matter (NVFP4: 272 -> 271 tok/s) and cost about 1.5 points, 4% of the facts the model knew. On a small card you get +56% speed but a much bigger hit. At the worst setting facts fall from 38% to 3%, and the model says things like "The Great Composer" with total confidence. Easy tests barely notice. The damage is mostly in chained reasoning and recalled facts. # 3. Bonus: a loop in the model weights Not every bad output is the engine's fault. One prompt made Qwen 3.8 Flash Next get stuck into an endless run of 0 in its reasoning: |Setup, same request, seeds 1-4|Stuck in zeros| |:-|:-| |Basalt, NVFP4|4 of 4| |Basalt, IQ3\_S|4 of 4| |Basalt, Q8\_0|3 of 4| |llama.cpp, same IQ3\_S GGUF|3 of 4| |API (OpenRouter - Alibaba)|6 of 6| The odds of another 0 are the same on every quant and both engines: 0.99 after 10 zeros, 95%+ past 100 or so. top\_p 0.95 leaves 0 as the only choice, and temp 1.0 doesn't fix it. The API fixes it by cutting the run at \~500 zeros. Basalt patched the issue as well, after 256 identical reasoning tokens it closes the thinking block and keeps going. # TLDR: there's no free lunch. * Engines can buy speed on MoE models by turning on speed "hacks". * With values some engines ship, every pack drops to somewhere between IQ3\_XXS and Q2 on KLD. A Q8 ends up next to Q2. This is as bad as it gets. * In practice the model forgets things it knew and loses the thread on multi step problems. Small cards get the biggest speedup and pay the most for it. * If your engine is faster than it should be on a model that doesn't fit, check whether it's still running the model you downloaded.
document fetched 2026-11-01 00:38 · canonical https://reddit.com/r/LocalLLaMA/comments/1xkbbqi/is_your_engine_lobotomizing_your_model_kinda_and