Views
No views yet
tencent/Hy3,
produced with REAP (Router-weighted Expert Activation Pruning). Each MoE
layer's 192 routed experts are reduced to the 48 most salient, shrinking the
checkpoint from 557 GB to 157 GB (BF16).⚠️ Experimental research artifact. This is an aggressive prune (75% of experts removed) calibrated on a small, code-only set. It generates fluent text and is genuinely strong at code, but general/factual accuracy is degraded (see below). Not intended for production. A better-calibrated version is planned — this repo will be updated in place.
| Base | This model | |
|---|---|---|
| Routed experts / MoE layer | 192 | 48 |
| Experts per token | 8 | 8 (unchanged) |
| Size (BF16) | ~557 GB | ~157 GB |
| Architecture | hy_v3 (HYV3ForCausalLM) | same |
router_weight × activation_norm over a calibration set; the least-salient
are dropped.compression_ratio 0.75 → 192 → 48 experts kept per MoE layer.theblackcat102/evol-codealpaca-v1 (code).meta and each of the 80 layers
streamed from the on-disk safetensors shards (~7 GB resident at a time), for
both calibration and the prune. See the
How To Spark training notes for the recipe.| Prompt | Output |
|---|---|
| Write an nth-Fibonacci function | Correct, well-documented Python ✅ |
| "The sky is…" | "Blue." ✅ |
| Capital of France? | "France does not have a single capital city…" ❌ (fluent but wrong) |
vllm serve <repo> --pipeline-parallel-size 2
(vLLM supports HYV3ForCausalLM). This model was validated running
pipeline-parallel across two DGX Sparks.hy_v3
quantization is still maturing).tencent/Hy3.