Known-issues sheets for local language models Rev 0.1.0 · reviewed every 7 days

Model datasheet · GLM

GLM-4.7

The full-size GLM behind the 30B Flash already listed here, and the strongest open coding scores on this site — SWE-bench Verified 73.8. It is also the most expensive model here to hold in memory: all 92 layers use full attention, so the KV cache costs 368KB per token, more than any other model in the catalogue.

Vendor
Z.ai
Architecture
MoE · 358B total / ~32B active
Context
202,752 tokens
License
MIT
Released
2025-12-22
Vision
No

→ GGUF (llama.cpp / LM Studio / Ollama)

§1 Characteristics by quantization band

Q2–Q3 — 2–3 bit

171GB weights · e.g. Q3_K_M + KV: 2.9GB at 8K · 11.5GB at 32K · 46GB at 128K
Coding 6/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q3_K_M · aggregated · 2026-08-31

    Editorial derivation: two points down. At 3-bit a MoE this large loses expert-routing precision first, which surfaces as dropped tool arguments and broken multi-file edits before prose visibly suffers.

Tool calling / agentic 6/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q3_K_M · aggregated · 2026-08-31

    Editorial derivation: two points down. At 3-bit a MoE this large loses expert-routing precision first, which surfaces as dropped tool arguments and broken multi-file edits before prose visibly suffers.

Q4–Q5 — 4–5 bit

205GB weights · e.g. Q4_K_M + KV: 2.9GB at 8K · 11.5GB at 32K · 46GB at 128K
Coding 8/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q4_K_M · aggregated · 2026-08-31

    Editorial derivation: one point down from the measured bf16 figure. 4-bit is the band a model this size is actually run at, and the loss is real but modest.

Math & reasoning 8/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q4_K_M · aggregated · 2026-08-31

    Editorial derivation: one point down from the measured bf16 figure. 4-bit is the band a model this size is actually run at, and the loss is real but modest.

Tool calling / agentic 8/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q4_K_M · aggregated · 2026-08-31

    Editorial derivation: one point down from the measured bf16 figure. 4-bit is the band a model this size is actually run at, and the loss is real but modest.

Q6–Q8 — 6–8 bit

294GB weights · e.g. Q6_K + KV: 2.9GB at 8K · 11.5GB at 32K · 46GB at 128K
Coding 9/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q6_K · aggregated · 2026-08-31

    Editorial derivation: no drop from the measured bf16 figure. 6-8 bit is effectively lossless on a model this size — the differences that show up at 4-bit and below are not measurable here. Recorded explicitly rather than left to band fallback, which would otherwise borrow the 4-bit number and subtract a point.

Factuality 8/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q6_K · aggregated · 2026-08-31

    Editorial derivation: no drop from the measured bf16 figure. 6-8 bit is effectively lossless on a model this size — the differences that show up at 4-bit and below are not measurable here. Recorded explicitly rather than left to band fallback, which would otherwise borrow the 4-bit number and subtract a point.

Math & reasoning 9/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q6_K · aggregated · 2026-08-31

    Editorial derivation: no drop from the measured bf16 figure. 6-8 bit is effectively lossless on a model this size — the differences that show up at 4-bit and below are not measurable here. Recorded explicitly rather than left to band fallback, which would otherwise borrow the 4-bit number and subtract a point.

Tool calling / agentic 9/10
data checked Aug 2026
  • quant-degradation-community — editorial band derivation @ Q6_K · aggregated · 2026-08-31

    Editorial derivation: no drop from the measured bf16 figure. 6-8 bit is effectively lossless on a model this size — the differences that show up at 4-bit and below are not measurable here. Recorded explicitly rather than left to band fallback, which would otherwise borrow the 4-bit number and subtract a point.

FP16 — full precision (fp16/bf16)

717GB weights · e.g. bf16 + KV: 2.9GB at 8K · 11.5GB at 32K · 46GB at 128K
Coding 9/10
data checked Aug 2026
  • vendor-model-cardSWE-bench Verified = 73.8 @ bf16 · vendor-reported · 2026-08-31

    LiveCodeBench-v6 84.9. The highest SWE-bench figure in this catalogue; Z.ai position 4.7 explicitly as a coding model.

Factuality 8/10
data checked Aug 2026
  • vendor-model-cardMMLU-Pro = 84.3 @ bf16 · vendor-reported · 2026-08-31

    No hallucination-rate benchmark published, so this rests on a knowledge benchmark alone.

Math & reasoning 9/10
data checked Aug 2026
  • vendor-model-cardAIME 2025 = 95.7 @ bf16 · vendor-reported · 2026-08-31

    GPQA-Diamond 85.7, MMLU-Pro 84.3, HLE with tools 42.8.

Tool calling / agentic 9/10
data checked Aug 2026
  • vendor-model-cardTau2-Bench = 87.4 @ bf16 · vendor-reported · 2026-08-31

    Terminal Bench 2.0 41.0, BrowseComp with context management 67.5. The Tau2 figure is the best agentic number on the site.

§2 Known issues & what fixes them

ISSUE-01 severe Q2–Q3 / Q4–Q5 / Q6–Q8 / FP16 · long-context

The most expensive KV cache in this catalogue by a wide margin. All 92 layers use full attention with no sliding window and no linear-attention layers, giving 368KB per token — so a 32K context costs 12GB of cache before a single weight is loaded, and filling the 198K window would cost about 71GB. On a machine sized to just hold the weights, context is what you run out of first.

No fix
No known fix — choose a different model

Architectural. Budget the cache explicitly: the RUNS AT line on this site prices it at the context you pick.

Evidence · 2 sources · community-consensus
ISSUE-02 moderate Q2–Q3 · coding, tool-calling

For almost everyone this model is only reachable at 2-3 bit — the 4-bit build is 205GB and the bf16 weights are 717GB. Unsloth's dynamic 2-bit lands around 135GB, which is the first size that fits a single large machine. That is a real option, but it is the bottom of the quant ladder, and expert routing in a 358B MoE is exactly what degrades there.

Fix
Move up a quant band [strong]

Move up to the 205GB 4-bit build if you have the memory; the gap between 2-bit and 4-bit is larger here than on a small dense model.

Evidence · 2 sources · community-consensus