GLM-4.7-Flash · file← GLM-4.7-Flash
MLX 4-bit g64
Our plain 4-bit MLX build. Lost to the mixed builds on perplexity and deleted. Made here from bf16.
- Size
- not recorded
- Status
- Deleted 8 Sep 2026
- Scored runs
- 3
| Suite | Score | 95% interval | Passed | Runtime · profile | Recorded |
|---|---|---|---|---|---|
| groundingglm-4.7-flash-mlx-q4unenforced | 53.6% | 44.9–62.1 | Passed 67/125 | mlx_lmextraction | 2026-09-08 |
| nullschemaglm-4.7-flash-mlx-q4unenforced | 40.3% | 29.7–51.8 | Passed 29/72 | mlx_lmextraction | 2026-09-08 |
| screeningglm-4.7-flash-mlx-q4 | 96.7% | 88.6–99.1 | Passed 58/60 | mlx_lmextraction | 2026-09-08 |
Runs marked unenforced were measured on a suite that requires constrained decoding, on a server shown not to apply the schema: mlx_lm accepts it and ignores it, and a few other servers and models break it. Those numbers do not measure what the suite is designed to measure. They are kept and labelled rather than deleted.
Rebuilt from the lab's records by Claude, an AI model. The results above come straight from the automated runs. How these pages are made.
| File | glm-4.7-flash-mlx-q4/ |
| Format | MLX 4-bit g64 affine, du 16 G |
| Where from | made here 2026-09-08 from the bf16 |
| Status | deleted 2026-09-08 14:29Z |
| Hugging Face | never uploaded |
How it was made
- Input:
models/glm-4.7-flash-bf16(GLM-4.7-Flash bf16 safetensors (zai-org)), so a single quantisation pass from bf16. - Command:
PY=mlx-main-venv/bin/python # mlx-lm 0.32.0, git main @ 7fb4be44d560e5b74595210f83cb6003a57e52a7; mlx core 0.32.2
$PY -m mlx_lm convert --hf-path models/glm-4.7-flash-bf16 \
--mlx-path models/glm-4.7-flash-mlx-q4 -q --q-bits 4 --q-group-size 64Same command in two one-off scripts (the second is the one whose log shows the conversion, "=== convert GLM q8 00:38 ===", "=== convert GLM q4 00:39 ===" local). The conversion's own log lines are not on record.
- Date: 2026-09-08, ~00:3x BST (23:3xZ on 2026-09-07). Who asked: Alan, "Can we quantize it?" and "First model for my hugging face profile :)".
- Size: du 16 G. Exact bytes not on record; never uploaded.
config.jsonreports4-bit g64 affine.
How it was served
| label | dates (UTC) | binary and version | ctx / -np / KV / -fa / --jinja / --reasoning-format | harness profile | why this label exists |
|---|---|---|---|---|---|
glm-4.7-flash-mlx-q4 | 2026-09-07 23:3xZ–23:5xZ | mlx-venv/bin/python -m mlx_lm server --model <dir> (bench_mlx); run log: mlx_lm 0.31.3 (see below) | mlx_lm server defaults; no flags | extraction | the first MLX build of the model, on the three extraction suites, beside the GGUF Q8_0 baseline |
No seats held.
Decisions
- Made as the 4-bit point beside q8.
- Dominated on perplexity: 14.457 against mixed_3_6's 11.677 at 2 GB more. "
q4is dominated and should not be published". - Deleted 2026-09-08 14:29Z, "reclaiming what the measurement already condemned", after Alan's "of course ;) We may need to bin a few more models though".
What went wrong
- Version stamp in doubt. The run log says
mlx_lm 0.31.3, the server venv's pinned version (mlx-venv). The card drafted the same night saysglm4_moe_liteis not in 0.31.3 and needs git main. One of the two is wrong;mlx-venvno longer exists to check.
What happened to it
Made here 2026-09-08 → benched 2026-09-08 → deleted 2026-09-08 14:29Z. No RESTORE entry; never on HF. Re-creatable with the command above, given the bf16 and mlx-lm at or after 7fb4be44. A later mlx-lm may produce different bytes.