GLM-5.3-Flash REAP-50 (FP8)

50% of routed experts removed with REAP (Router-weighted Expert Activation Pruning, arXiv:2510.13999), calibrated on a permissively-licensed multi-domain corpus that includes real image-text pairs.

Base zai-org/GLM-5.3-Flash (MIT, FP8 E4M3, 128x128 block scales)
Experts 288 -> 144 per layer, top-8 routing unchanged
Size 160.6 GiB (FP8)
Healed yes
MTP block excluded (see below)

Why FP8 and not BF16

The upstream release is FP8, not BF16. Routed experts are stored per-expert with their own weight_scale_inv block scales, so pruning is deleting whole tensors - lossless on every retained weight. The 642 GB BF16 repo elsewhere on the Hub is a dequantised upcast carrying no additional information.

Calibration

Mixture weighted for a coding/agentic model that stays empirically grounded: agentic 24%, code 21%, math 15%, multimodal 15%, science+bio 10%, finance 8%, ballast 7%. Permissive licences only, so this checkpoint keeps the base model's MIT lineage.

Vision is first-class: the vision tower contains no MoE and is untouched, but image tokens route through the same expert pool as text, so text-only calibration would have deleted vision-serving experts with certainty. Real image-text pairs were asserted present.

Evaluation status: NONE

Measured against the unpruned teacher

Teacher-forced paired evaluation on 241,516 held-out tokens the calibration never saw, scored against unpruned zai-org/GLM-5.3-Flash on identical inputs.

Top-1 agreement 0.842
ΔNLL (student − teacher), mean +0.1756
ΔNLL, median +0.0012
Top-k KL (teacher ‖ student) 0.6503
Teacher NLL / student NLL 1.018 / 1.194
domain tokens top-1 agreement ΔNLL
agentic 69,202 0.873 +0.137
math 66,558 0.920 +0.022
science 45,034 0.830 +0.125
finance 22,215 0.755 +0.181
ballast 22,154 0.580 +0.989
code 15,821 0.919 +0.052
vision 532 n too small n too small

1 − flip_rate against the unpruned model is the same quantity aggressively-quantised releases quote as "retains X% of top-1 accuracy", so this number is comparable to a heavily-quantised GGUF of the same base — provided both are measured against that same unpruned reference.

Image-placeholder positions are excluded, as the training objective excludes them. After that exclusion the vision bucket is too small to support a conclusion: vision is unmeasured here, which is not the same as measured-and-fine. Its per-domain saliency retention (0.682, mid-pack of seven domains) says the mask did not strip vision-serving experts; whether the survivors suffice is untested.

This is teacher-forced agreement, not capability. It measures how far the student moved from the teacher on ground-truth prefixes. It does not measure whether the model is smart — only generative benchmarks do, and none has been run.

What this prune costs, and what it does not

REAP ranks experts on saliency pooled across the calibration mixture, so the cost is not spread evenly across capabilities. Measured on this checkpoint - the fraction of the expert output each domain actually relies on that survived the prune:

domain retained
agentic / tool use 0.747
code 0.728
science 0.720
maths 0.713
vision (image-text) 0.682
finance 0.651
general / ballast 0.487

The damage is concentrated where retrieval can repair it. Generic factual ballast is the worst-retained bucket, and it is also the single most RAG-recoverable capability: a markdown corpus and a retriever substitute for memorised trivia almost perfectly. The best-retained buckets - agentic behaviour, code, science, maths - are the ones retrieval cannot restore, because you cannot retrieve your way to reasoning, tool use, or code synthesis.

If you are deploying this, pair it with retrieval. That is not a workaround for a defect; it is the shape the trade was made in. A uniformly-quantised model of the same footprint spends its degradation budget evenly, including on the capabilities retrieval cannot give back.

Two honest caveats. Low retention can also mean a domain uses experts diffusely rather than that its capability was removed - generic web text spreads across many experts while REAP keeps concentrated ones. And the per-domain spread was a consequence of the calibration mixture, not a targeted design: this is mixture-shaped preservation, not surgery.

Method: strengths and gaps

Where this is above common practice

  • Calibration is 5.5M tokens across seven use-case-weighted domains, against the 128-512 generic samples typical of pruning and quantisation work.
  • Real image-text pairs in calibration, not text descriptions of images. Measured effect: vision retained 0.682, at the cross-domain mean. Text-only calibration deletes vision-serving experts with near-certainty.
  • Saliency capture was verified against the model source - the router gate excludes e_score_correction_bias, which is the detail most implementations get silently wrong.
  • Per-token router scores were cached, making post-prune routing exactly replayable offline.
  • The healing correction was measured, not derived. The standard first-moment estimator over-corrects by ~30% on this architecture because it ignores norm_topk_prob renormalisation; that error was found and fixed only because of the router cache.
  • The calibration budget was validated by a split-half stopping rule on retained saliency mass, rather than assumed.

Where it falls short, stated plainly

  • Healing rescales experts; it does not retrain them. The per-expert coefficients are the best a fixed rescaling can do, and that ceiling is now measured rather than assumed: 96.6% of an expert's output energy is token-dependent residual rather than its mean, so the ~0.27 residual that remains is information deleted with the pruned experts, not error a better fit could remove. Recovering it means layer-local distillation, which needs a backward pass that does not fit the hardware this was built on.
  • No expert merging (REAM/EEP), rejected on cost.
  • Evaluation is teacher-forced dNLL and top-1 agreement, not generative benchmarks. That is the largest gap: dNLL does not fully predict agentic or coding capability, which is what this model is for. Generation from the unpruned teacher costs ~110 s/token on one device and was out of reach.
  • Long context is uncalibrated. Calibration sequences were capped at 2048 tokens against a 1M-token context window.
  • The calibration mixture was specified in samples but acts in tokens; document lengths differ by more than 10x, so realised domain weights differed substantially from intended.
  • A single prune ratio was materialised. No 40/50/60 ablation with evaluation behind it.

Known limitations

  • The MTP (multi-token-prediction) block at layer 45 is excluded. transformers' Glm5NextForConditionalGeneration does not instantiate it, so the pruning path cannot see it. Dropping it forecloses speculative decoding from this artifact.
  • REAP has no published data above 50% compression; this checkpoint sits at the validated ceiling, not beyond it.
  • Expect factual-recall regression before reasoning or coding regression. That is the measured failure mode of expert pruning on this architecture family: the closest published analogue (cerebras/Kimi-Linear-REAP-35B-A3B, same KDA + full-attention stack) loses 3.4 points on FRAMES at only 30% pruning while code and maths hold flat.
  • Healing is an output-scale correction applied exactly to the F32 block scales, median gain 0.9096. It was measured, not derived: post-prune routing is replayed from a cached router-score trace, because the first-moment estimator that pass 1 used ignores that norm_topk_prob renormalises the surviving top-8 and over-corrects by ~30%. It is not distillation and does not recover lost knowledge.
  • A per-expert least-squares refinement of this correction was built, shipped, and then reverted. It reduced held-out reconstruction residual in 41 of 42 layers and was still 11.8σ worse end-to-end (top-1 agreement 0.83693 vs the scalar's 0.84249, worse on every metric and in every sufficiently-sampled domain). Under the measured near-orthogonality the coefficient reduces to c_j = (gate mass before pruning) / (gate mass after), so it suppresses exactly the experts the pruned router leans on hardest - 62% of coefficients landed below their layer scalar, the worst by 3.3×. Lower reconstruction error, worse model. Recorded here because the technique is more attractive on paper than in measurement; see the repository's research/HEALING_ABLATION.md.
  • A per-expert least-squares refinement of this correction was built, shipped, and then reverted. It reduced held-out reconstruction residual in 41 of 42 layers and was still 11.8σ worse end-to-end (top-1 agreement 0.83693 vs the scalar's 0.84249, worse on every metric and in every sufficiently-sampled domain). Under the measured near-orthogonality the coefficient reduces to c_j = (gate mass before pruning) / (gate mass after), so it suppresses exactly the experts the pruned router leans on hardest - 62% of coefficients landed below their layer scalar, the worst by 3.3×. Lower reconstruction error, worse model. Recorded here because the technique is more attractive on paper than in measurement; see the repository's research/HEALING_ABLATION.md.
  • Routing is disrupted more than expert count suggests: the retained experts carry ~0.99x the routing mass an average expert would, because REAP preserves rare-but-strong experts over common-but-weak ones.

Serving on Jetson Thor

Use the cutlass fused-MoE backend (the Marlin FP4 MoE kernel faults at >=256 experts) and TRITON_MLA for the 11 MLA+DSA layers (FLASHINFER is invalid for MLA).

Corrections to this repository

2026-08-29 — the healing correction was replaced, and the weights changed. If you downloaded this checkpoint before this date you have the superseded version; re-pull to get the current one.

This checkpoint originally shipped a per-expert least-squares healing correction: one coefficient per retained expert, fitted in closed form to reproduce the unpruned layer's output under post-prune routing. It reduced held-out reconstruction residual in 41 of 42 layers, which is why it shipped.

An end-to-end ablation then measured it against the per-layer scalar it had replaced — same checkpoint, same 241,516 held-out tokens, same cached teacher, one variable moved:

metric per-expert (was shipped) per-layer scalar (ships now) Δ
top-1 agreement 0.83693 0.84249 +0.00556
ΔNLL vs teacher 0.19396 0.17563 −0.01833
top-k KL 0.69388 0.65030 −0.04358

Better in every sufficiently-sampled domain. Both arms score the identical token set, so the correct test is paired: McNemar over the 13,020 discordant tokens (5,839 the per-expert arm gets right and the scalar does not, 7,181 the other way) gives χ² = 138.1, z = 11.8. Healing is a multiply on the F32 block scales and is exactly invertible, so the fix was a rescale, not a re-prune — no expert was re-selected and the mask is unchanged.

Why it lost. Under the measured near-orthogonality of expert outputs (off-diagonal mass 1.9%) the coefficient reduces to c_j = (gate mass expert j received before pruning) / (gate mass it receives after). The intended reading was that an expert promoted into the top-8 by pruning is doing work it never did before and should be shrunk. But it is doing that work because the expert that used to do it was deleted — damping the substitute does not bring the original back, it leaves a hole. 62% of the 5,760 coefficients landed below their layer's scalar; 45 experts were suppressed more than 2×, the worst by 3.3×, and by construction those are exactly the experts the pruned router depends on most.

A second correction follows from the same measurement. Pass 1 shipped scalar healing and pass 2 shipped per-expert, so the two were never comparable. Holding healing fixed, the pass-2 mask is worth +0.00545 over pass 1 (McNemar z = 9.3) — not the ≈0 previously reported here. The two changes were real effects of opposite sign that had cancelled into a null.

Full analysis, including why a held-out reconstruction proxy improved while the model got worse: research/HEALING_ABLATION.md in the pipeline repository.

Downloads last month
-
Safetensors
Model size
165B params
Tensor type
BF16
·
F8_E4M3
·
F32
·
Inference Providers NEW
This model isn't deployed by any Inference Provider. 🙋 Ask for provider support

Model tree for patrickbdevaney/GLM-5.3-Flash-REAP50-FP8-v2

Quantized
(52)
this model

Paper for patrickbdevaney/GLM-5.3-Flash-REAP50-FP8-v2