Why your local LLM feels dumber than it is(forum.level1techs.com)
364 points by felineflock 16 hours ago | 135 comments
tl;dr: Local LLM inference diverges from reference implementations because every step—attention backends (FlashAttention vs Triton), KV-cache quantization, weight quantization schemes, and the specific CUDA/GEMM kernels selected—produces subtly different logits, causing top-token flips that compound over long contexts. Benchmarks on Qwen3.6-27B show INT4 KV-cache and NVFP4 weights hitting ~50% token divergence by 88k tokens and failing tool calls, while W8A16 INT8 actually outperforms official FP8. Takeaway: your setup's "dumbness" is largely a function of stack-specific numerical drift, not just the model or quant level.
HN Discussion:
  • Only run unquantized/high-precision models to avoid the quality degradation the article describes
  • Local models work great in my experience, quantization issues seem overstated
  • Setting up local inference is painful and error-prone, reinforcing stack-specific problems
  • Curious whether the article's numerical drift analysis extends to cloud-hosted LLMs too
  • ~Local control over model quality is worth it despite any drift issues